This is a human-owned operational runbook. The maintainer completed the controlled decommission operation and bounded post-decommission smoke before APG9. The sequence remains historical operational and rollback guidance; it does not authorize restoration or another plugin mutation.
Superpowers is retired from the maintainer’s workflow. Preserved source remains
reference evidence. The apg-project-skills command manages only opted-in
repository projections and must never install, disable, remove, restore, or
configure a global plugin.
The human maintainer owns readiness acceptance, the decommission decision, global plugin controls, rollback authority, and final disposition. Stop if the current Codex product does not expose a supported control for the intended global action.
The maintainer’s explicit decision, completed decommission, and accepted fresh RepoMap smoke supply the authorized v0.1 closeout facts. The smoke discovered all six APG skills, explicitly applied the review skill, passed default and explicit managed checks, preserved the tracked repository, and did not use Superpowers as workflow authority.
Before the operation, APG8 supported these components:
APG9 reconciles the later outcome rather than rewriting APG8’s contemporaneous record. No rollback was required, and successful restoration remains untested. The operation does not establish an exhaustive active-project inventory, automatic skill selection, comparative superiority, or stable maturity.
Record the date, decision owner, Codex application version, APG revision, relevant repositories, current evidence, unresolved risks, and rollback owner. Confirm that every materially used Superpowers workflow has an accepted APG, native Codex, repository-policy, deferral, or rejection disposition.
Stop if any authority, privacy, destructive-action, completion-evidence, or representative-workflow regression remains unresolved.
For each repository selected for the smoke, run the APG check command from the current APG checkout:
<apg-root>/bin/apg-project-skills check --repo <target-path>
Confirm exact managed names, readable canonical leaves, clean normal Git status, and no tracked target changes. Do not automatically enroll additional projects.
Confirm that the existing publication-excluded source and provenance record is readable, immutable for the operation, and sufficient to identify the installed source and applicable license. Do not place local plugin paths, private payloads, or credentials in public artifacts.
Using current supported Codex inspection controls, record whether Superpowers is installed and enabled, its observable version or identity, and the control used to restore it. Store exact local evidence only in an authorized private operational record. Do not infer configured state from APG skill discovery.
The maintainer must explicitly approve the named global action, affected Codex profile, smoke scope, failure criteria, rollback operator, and time boundary. An APG report, ADR, tool result, or agent recommendation is not approval.
The human operator uses only the currently supported Codex plugin controls for
the approved profile. Do not edit internal plugin files, user configuration,
desktop metadata, or caches directly, and do not ask apg-project-skills to
perform the action.
Stop if the supported control is absent, ambiguous, affects a broader profile, or reports a different plugin state than the readiness record.
Close and restart the complete Codex application using its supported lifecycle. Opening a new task without restarting the application is insufficient when the environment still presents cached discovery state.
In each approved target, verify:
apg-project-skills check still passes.Record actual invocation only when observable. Do not treat filesystem projection or skill listing alone as invocation evidence.
Rollback is required when any approved smoke target shows:
Do not broaden the phase into plugin debugging, unsupported configuration editing, APG skill promotion, or emergency framework development.
The human operator reverses the exact approved global action using the supported Codex control recorded before decommissioning. Restore the prior observable plugin identity and enabled state. Do not reconstruct plugin files or internal configuration manually.
If supported restoration is unavailable or ambiguous, stop and escalate to the human maintainer. APG project projections may remain installed; they do not replace a failed global restoration operation.
If rollback policy also requires removing local APG discovery, run:
<apg-root>/bin/apg-project-skills uninstall --repo <target-path>
Use check first when state is uncertain. The command removes only valid
state-owned links and its Git-local exclusion block. It does not remove
canonical APG skills or restore Superpowers.
Restart the full Codex application again. Verify the restored Superpowers state, the intended APG projection state, representative workflow availability, material non-trigger behavior, repository authority and privacy boundaries, and clean target tracked state.
Record whether rollback fully restored the pre-decommission condition, what remains unresolved, and the human maintainer’s terminal disposition. A failed or partial rollback stops further decommission attempts.
Keep a bounded private operational record containing the decision, supported control categories, before-and-after state, smoke results, failure or rollback trigger, and terminal human disposition. Do not retain credentials, raw private payloads, private source content, or local paths in public records.
This runbook originally satisfied the rollback-plan documentation component of the gate. APG9 accepts the subsequent human action and bounded smoke as the v0.1 decommission closeout while retaining the unverified inventory, universal- coverage, and restoration dimensions as limitations. The preserved rollback sequence remains available only under a new explicit human authorization; APG9 does not restore or test restoration.