Phase ID: APG23
Complete — v0.3 development catalog readiness and fresh-session smoke accepted
APG22C is accepted as complete with no unresolved material defect. APG23 began after the required full application restart in a new session rooted in the private APG development repository.
The client displayed all 19 repository development skill names and separate repository and personal same-name workflow-router entries. The repository router was selected using client-supplied APG path evidence. Outside-repository global-only visibility was not observed and is not claimed.
| Skill | Maturity | Inclusion |
|---|---|---|
agentic-praxis-grimoire-workflow |
stable |
include-v0.3 |
synthesizing-repository-guidance |
stable |
include-v0.3 |
composing-approved-roadmap-assignments |
provisional |
include-v0.3 |
python-language-profile |
stable |
include-v0.3 |
bash-language-profile |
stable |
include-v0.3 |
bats-test-profile |
stable |
include-v0.3 |
go-language-profile |
provisional |
include-v0.3 |
ruby-language-profile |
provisional |
include-v0.3 |
zsh-language-profile |
stable |
include-v0.3 |
zunit-test-profile |
stable |
include-v0.3 |
nix-language-profile |
stable |
include-v0.3 |
postgresql-database-profile |
provisional |
include-v0.3 |
sqlite-database-profile |
provisional |
include-v0.3 |
Eight rows are promoted; five remain provisional; no skill requires correction or exclusion. The resulting catalog/map/projection state is 19/19/19, with 14 stable rows, 5 provisional rows, and 18 non-router routes.
All router, synthesis, approved-roadmap, language, test, database, and five required process/domain pairing cases pass. Exact ZUnit support remains limited to v0.8.2 with Zsh 5.9.2 under the APG22C corrected selected-user-startup boundary. Exact Zsh 5.3.1 is unsupported and every other pair is unverified.
Thirteen fresh non-author per-skill reviews find no material skill defect. A fresh aggregate review accepted seven integrated categories and found one record-contract defect: ADR 0018 initially omitted its decision date. The date and standard status section were added before finalization and the affected gates were rerun.
The configured repository suites pass 250 tests with two expected fixture skips. Development projection checks pass 19/19/19 and the unchanged active public-backed projection checks pass 6/6/6 in text and JSON. Compilation, shell syntax, command help, changed-link, privacy, mode, schema, durable-reference, record-identity, and staged-whitespace checks pass. A fresh complete-diff reviewer accepts the corrected resulting state. Commit/push parity and managed reports remain required before this exit is externally accepted.
Every original v0.3 objective is terminal. APG24 is the only remaining v0.3 phase and may enter only after APG23 is committed, pushed, remote-equal, fully reported, and externally accepted.
Public v0.2, public/reference/RepoMap and target repositories, project/user/ release schema version 1, managed defaults, personal workflow, and active public-backed integration are preserved. APG23 creates no candidate, publishes nothing, performs no root/private cutover, and does not begin APG24.
Accept APG23 as complete and authorize APG24 only through a separate explicit maintainer instruction.