Participant: codex (AI agent)
Understanding
Ticket-019 is now unblocked by ticket-018, but its five implementation paths
still cross sdk, governance and unowned root metadata. The validator does
not transfer ownership through integrationTicket; therefore widening the
ticket-019 allowlist alone would remain invalid.
The target manifest is intentionally customizable. Its lock can be refreshed
with the immutable adoption generator while preserving the pinned standard
revision. This is narrower than changing the upstream standard or weakening
the ownership check.
Execution plan
- Commit this plan and intent without implementation changes.
- In a later commit, add only the five Python publication paths to the
existing integration workstream and
requiredForPaths.
- Refresh the adoption lock from the pinned upstream revision.
- Run governance on the real diff and on a temporary simulated ticket-019
integration intent.
- Record evidence, push a dedicated PR and request exact-head validator review.
Actual changes
- Added the five exact publication paths to the existing integration ownership
and shared-contract lists in a commit after the plan and intent.
- Regenerated only the target lock digest using the immutable 0.10.0 adoption
source revision.
- Verified the real branch and an isolated future ticket-019 active state with
zero governance findings.
Risks and boundaries
- The target-specific manifest changes policy scope, so the exact path list is
explicit and the standard provenance must remain unchanged.
- No Python packaging implementation belongs in this ticket.
Validation result
All acceptance criteria pass. The ticket is ready for protected CI and an
exact-head external review; no runtime or publication command was changed.