Phase ID: APG22
Complete — cross-repository dogfood and v0.3 guidance-migration proposal recorded
APG22 applies the provisional router, guidance-synthesis leaf, and all nine retained profiles to a frozen read-only matrix spanning APG, RepoMap, classified private guidance, and public-safe synthetic boundaries. All 10 router, 9 profile, and 16 synthesis cases match their expected dispositions. The evidence includes process/domain pairing, no-skill and non-trigger results, overlap resolution, project override, classified artifacts, semantic-over-structural control, Red stops, privacy treatment, and no authority expansion. No behavior-bearing APG defect or correction is found. One review-driven evidence-record correction enumerates eight initially asserted synthesis classes and normalizes all per-application measurement fields before final acceptance.
Application discovery is not measured. Explicit skill reading and application do not establish fresh-session selector discovery.
APG’s concise root remains unchanged. The public proposal keeps exact target commands, thresholds, schemas, compatibility, runtime, and destructive-action policy with target repositories and keeps personal, machine, host, private runtime, and integration guidance private. Any later shadow or cutover requires current-source refresh, public distribution, managed projection, discovery, non-trigger, overlap, project-override, target-acceptance, and byte-restorable rollback evidence.
Native skill writing requires no separate public APG leaf. A distinct manager- assignment capability remains a separately authorized evaluation and optional implementation candidate. ZUnit supports only a legacy-only, version-bounded future evaluation under an explicit maintainer decision; current stable-Zsh compatibility is not established.
Before APG23, the manager-assignment candidate must reach a terminal result and the maintainer must authorize legacy-only ZUnit work or explicitly exclude it from v0.3. If retained, ZUnit requires its own compatibility, implementation, review, and retention phase. APG22 finds no current correction-phase input.
Private development remains 17 canonical leaves, 17 relative projections, 6 stable rows, 11 provisional rows, and 16 routable non-router capability-map entries. The six v0.2 managed defaults and project, user, public-release, and map schema-version-1 contracts remain unchanged. Public v0.2.0 and active public-backed integration remain six stable skills.
The complete documented unit and integration suites, development and public checker shapes, report identity, Python and shell syntax, executable help, Markdown links, privacy, durable-reference, mode, schema, whitespace, staged- diff, and ten fresh non-author review lanes accept the resulting tree.
APG22 performs no skill correction, maturity change, root rewrite, private- skill mutation or decommission, target edit or execution, database or graph operation, Nix operation, dependency or schema change, public release, active- integration mutation, application smoke, APG23 work, or later phase. No tracked record uses an internal commit hash as phase or state identity.
APG22A retains the approved-roadmap manager-assignment owner provisionally and preserves every APG22 migration, privacy, distribution, and smoke boundary. The remaining pre-APG23 objective is the separately authorized version-bounded ZUnit evaluation.
APG22B makes that objective terminal by retaining a provisional ZUnit profile only for exact ZUnit v0.8.2 with Zsh 5.9.2 in the tested environment. The exact Zsh 5.3.1 pair is unsupported. APG23 remains separately authorized and has not begun.