[EXT-05] Resume adoption delivery integration and validation reuse

[tom-sapletta-com]

Planfile continuation handoff: 2026-09-15

Repository: semcod/goal. Plan section: EXT-05.
Planfile identity: semcod/goal:PLF-006. Project store: .subactor/recovery/planfile.

This handoff is planned work, not a claim that the implementation is missing or complete. Reobserve current source, tickets, PRs, runtime and receipts first. EXT identifiers refer to sections of the Taskand external-dependencies plan, not allocated governance tickets or URNs.

First steps on resume

1. Start from actual accepted work, not an assumption of missing code: PR feat(ticket-109): connect adoption transaction to Goal CLI #154 merged as 2d86db2 and PR fix(ticket-110): restore adoption subject before restart readback #155 as ad8f125. The latter adds adapter reconstruction with resume_plan.
2. Determine which production authority/readback providers and runtime integration remain missing. Do not equate a library API or merged source with deployed autonomous adoption.
3. Coordinate the OneDev candidate qualification in subactor/onedev-agent#322. Its historical extra Goal check failed; later canary attempts hit a noexec harness error before tests, not a proved Goal defect.
4. Measure deterministic validation reuse and expose progress, while rechecking head, lease, permissions, freeze and external checks before every effect. Resume the same transaction after uncertain outcomes.

Acceptance

• Restart after partial/complete adoption does not allocate duplicate work or repeat an unknown effect; exact subject and receipt bindings remain enforced.
• Reuse invalidates on every relevant input change, including untracked inputs; production validation/authorization is not replaced by cached PASS.
• Handoff lists source/package/runtime/deployment separately and links remaining old issues Register unfinished ticket-100: Stop bootstrapping pfix auto-repair into projects #142-Validate exact source-hub candidate governance before publication #145 without automatically closing or cleaning their work.
• Return the real owner ticket/intent, source and artifact pins, exact subject, commands/environment/results, bounded evidence/digests, lifecycle state, adoption/rollback procedure and remaining owner/nextAction.

Boundaries

Reuse an existing matching owner ticket and qualify its current allowed scope before writing code. New work must use the repository's managed allocation and protected delivery route. An evidenced NO_CHANGE is valid. Do not manufacture ticket-only PRs, fake CI or approval, force-push, clean inherited work, change required checks or mutate shared deployment from this text. P1/P2 work is not a new gate for independent P0 delivery. Do not put raw logs, credentials or private session content into this issue. Planned resumption is not an automatically scheduled job.

---

Strategy Metadata:

• deduplication_key: taskand-ext-handoff-20260915:semcod/goal:EXT-05:adoption
• planfile_id: semcod/goal:PLF-006
• plan_section: EXT-05
• resume_on: 2026-09-15