Phase ID: APG24
Published — v0.3.0 released; fresh-session public shadow smoke pending
2026-07-22
APG23 is accepted as complete with nineteen release-included skills, fourteen stable rows, five provisional rows, and no unresolved material skill defect. ADR 0019 expands the public and local distribution contracts to the exact nineteen-skill set while retaining state schema version 1. User lifecycle is source-release-specific; project lifecycle defaults new installations to the current release but preserves explicit and existing subsets.
Release inclusion remains independent of maturity. The exact ZUnit boundary is v0.8.2 with Zsh 5.9.2 in the tested environment and recorded startup boundary; Zsh 5.3.1 is unsupported and every other pair is unverified. Nix and database profile publication grants no live operational authority.
The public-safe source contains nineteen skills, nineteen catalog rows,
nineteen projections, fourteen stable rows, five provisional rows, and eighteen
non-router routes. Every public artifact is independent of private/.
Two builds from the same reviewed source, exact public v0.2.0 base, version, timestamp, and publisher identity produce identical manifests, trees, commits, and annotated tag objects. Candidate and isolated user/project lifecycle validation cover the exact 6 to 19 to 6 transition, existing six-skill project state, unrelated content, conservative recovery, and the complete configured regression surface.
Public v0.3.0 appends exactly one squashed commit over unchanged v0.2.0 and one
annotated v0.3.0 tag. Publication is limited to one atomic fast-forward of
public main and creation of that tag. Public v0.1.0 and v0.2.0 remain present
and unchanged. Exact object and remote evidence belongs to the postcommit
operational record rather than this semantic exit.
After fresh public-checkout verification, the active public-backed source fast-forwards from v0.2.0 to exact v0.3.0. Its existing aggregate-link owner, inode, and raw target remain unchanged. No direct-link conversion, user-state migration, Codex configuration change, target-repository mutation, or unrelated user-skill mutation occurs.
The personal workflow router remains installed alongside the public v0.3.0 router. No precedence is inferred from their shared name. Reference, RepoMap, Codex configuration, databases, Nix state, graphs, and deployments remain unchanged. Root and publication-excluded guidance are not removed or cut over; their only APG24 change is the bounded exact-Git-evidence clarification. Superpowers remains retired.
Shell validation cannot prove that a new Codex session has refreshed the public source or can source-qualify both router entries. The remaining action is a full application quit and relaunch, followed by a new task outside the APG repository that explicitly selects the public v0.3.0 router and exercises process, no-skill, process/domain pairing, and stale-metadata cases.
Terminal outcome:
published-pending-fresh-session-shadow-smoke
That observation does not authorize personal-router decommission. APG24 removes no root or private guidance and begins no successor phase.
APG24A records the maintainer’s later report that the fresh-session public shadow smoke passed and that the personal same-name router was subsequently decommissioned under separate human authority. Focused resulting-state verification confirms unchanged public and active v0.3.0 state and an exact private restoration source. APG24’s original disposition remains the truthful outcome at this exit; APG24A closes the later external condition forward.