Complete — APG17 public-release identity evidence corrected
The maintainer accepted APG17 in substance and authorized a record-only correction before the separately authorized APG18 phase. ADR 0013, the provisional synthesis skill, sixteen frozen scenario families, zero candidate corrections, the reviewed 34-unit dogfood ledger, native authoring and APG lifecycle boundary, no-rewrite and no-cutover contract, router integration, six stable process skills, provisional workflow router, six-skill public-v0.2 distribution boundary, and APG17 reviews remain accepted.
APG17 recorded two public v0.2.0 object identities that conflicted with the accepted APG14 release record. Fresh live-remote, fresh-checkout, active-source, tag-type, tag-target, tree, parent, subject, lineage, and skill-library evidence all match APG14. The former values are not Git objects in any inspected repository and entered repository history only as APG17 prose.
The demonstrated cause is an unverified manual transcription into one publication-excluded APG17 record. This was not live public divergence, a stale tag, a temporary candidate, a wrong checkout, or an incorrect peeling mode.
The two exact publication-excluded fields are corrected. Bounded subsequent notes identify the record correction and smoke disposition without publishing private object identities. The public release itself did not change.
All eight skill files, the seven-entry capability map, catalog, eight checked projection targets, project/user/release helpers and policy, schema versions, maturity rows, managed defaults, and six-skill v0.2 distribution contract remain byte-identical to the APG17 baseline. No skill, architecture, scenario, dogfood disposition, maturity, schema, command, dependency, external repository, or integration changed.
A fresh read-only non-author reviewer returned accept with no finding after
inspecting the complete tracked diff and all untracked APG17A artifacts. The
reviewer independently verified the live and APG14 identity, original mismatch,
demonstrated transcription-error class, corrected fields, unchanged protected
surfaces, public privacy, external-state preservation, smoke disposition,
APG18 gate, and this exit’s truthfulness.
The maintainer intentionally deferred APG17 and APG18 application discovery and explicit-use smoke to APG23 aggregate readiness and APG24 release preparation. The deferral does not reverse APG17 repository acceptance.
APG18 is authorized by the same assignment but may begin only after this phase is independently accepted, validated, committed, pushed, remote-equal, and represented by complete schema-valid managed reports.
Resulting-state validation passed:
Source suites were not run because the phase changes records only.
No immediate application smoke or additional human confirmation is requested. The next authorized action is APG18 after every APG17A gate above passes.