Complete — shared language-profile contract accepted and one provisional Python language profile implemented
APG17A completed its independent review, validation, commit, push, remote-equality, and schema-valid managed reports before APG18 began. Its public-identity record correction and smoke-deferral disposition remain accepted.
APG18 accepts ADR 0012 and the shared language-profile contract, implements one provisional Python profile, and integrates that profile with the existing workflow router, capability map, private-development catalog, and checked-in skill projections. The profile supplies calibrated language judgment while the existing APG process skills continue to own procedure.
No root guidance was migrated or removed. No private skill was decommissioned. No dependency, plugin, state schema, framework selection, public v0.2 release, active integration, or other language profile was added.
The accepted levels are Green routine, Yellow caution, Orange warning, and Red crisis or stop. Levels classify one coherent current decision, do not grant authority, and cannot relax superior safety, privacy, compatibility, destructive-action, or task-authority rules. Orange requires an explicit local decision, rationale, rollback, and focused validation. Red stops unsafe action or new crisis-level growth until the governing condition is resolved.
Python defaults cover module lines, callable statements, cyclomatic complexity, branches, nesting depth, explicit arguments, local bindings, and independent responsibility families. They distinguish maintained hand-written code from generated, vendored, protocol, migration, snapshot, machine-produced, test, and legacy artifacts. Repository analyzers and stricter project policy remain controlling.
Current Python, packaging, compatibility, typing, lint, and complexity sources were inspected with their reuse terms. Numeric tool defaults and read-only repository distributions informed the calibration; APG independently authored the profile and added no tool dependency.
Twenty-four scenario families were frozen before candidate wording. The first complete application passed all families, after which semantic review found two material completeness gaps. One bounded correction added public-source maintenance boundaries and explicit proportional treatment for several Python semantic cases. The corrected candidate then passed 24/24 in a fresh complete application. No second candidate correction was needed.
Seven read-only real-code cases produced one Green, one Yellow, four Orange, and one Red disposition. The sample exercised structural measures, combined signals, compatibility, concurrency, legacy minimal fixes, test coherence, and migration ownership without changing the sampled files or requiring a threshold correction.
Four independent resulting-state reviews cover semantic completeness, threshold calibration and false escalation, router/catalog compatibility, and the complete diff. Material findings were corrected and re-reviewed before retention.
Private development contains nine canonical skills, nine relative projections, six stable process rows, three provisional rows, and eight routable non-router capability-map entries. Project installation continues to manage only the six stable v0.2 skills. Public v0.2 remains 6/6/6, all three lifecycle state schemas remain version 1, and all eight preexisting skill files remain byte-identical to the APG17A baseline.
Resulting-state validation passed:
Fresh-session application discovery and explicit-use smoke were intentionally not run. APG23 owns aggregate v0.3 readiness smoke; APG24 owns public-candidate and active-integration release-preparation smoke. APG18 supplies no selector or invocation observation and no maturity promotion.
APG19 has not started and is not authorized by this phase. The next action requires a separate maintainer authorization.
No immediate application smoke, publication, successor phase, or additional human confirmation is requested. Preserve the APG23/APG24 smoke deferral and await separate maintainer authorization for any further phase.
APG18A corrected publishable current owners that still described the APG17 eight-skill state, ADR 0012 as proposed, or only two provisional development additions. README and the project-projection, user-integration, public-release, and roadmap documents now state the accepted APG18 9/9/9 development shape, six-stable/three-provisional maturity, eight-entry router map, and unchanged six-skill public-v0.2 lifecycle.
The correction changes no APG18 decision, skill, threshold, map, projection, maturity, test, schema, managed default, public release, integration, or external state. APG19 is conditionally authorized only by the maintainer’s APG18A-then-APG19 assignment and may begin only after APG18A closes through its review, commit, push, remote-equality, and managed-report gates. Smoke remains deferred to APG23/APG24.