# IPZ Delivery and Site Content Continuation

Audience: AI coding agents first.

- **ID:** IPZ-DELIVERY-SITE-CONTENT-CONTINUATION-2026-08-14
- **Status:** IDLE
- **Task IDs:** DC-01, SC-REPO-01, SC-ADAPTER-01, SC-HANDLER-01, REL-ENTRY-01, REL-OVERVIEW-01, REL-GENERATE-ALL-01, REL-INTEGRATION-01
- **Source request:** Follow plugins/international-press-zone/.claude/agents/expert.md
/caveman ultra
In the current isolated worktree, create or update the durable continuation plan for the owner’s remaining session scope. Record, without duplicating existing detailed plans: (1) diagnose repeated delivery-controller missing-reference errors first; (2) continue dormant Site Content in strict order—repository, translation adapter, resource-handler integration; (3) keep those inactive until later runtime/API/UI work; (4) preserve remaining release tasks: site entry/layout, site overview, Generate All, broader integration; (5) request-context contracts and dormant catalog are already published to origin/master. Plan must include outcome, status, task IDs, exact source request, acceptance criteria, preserved WIP/refs/paths, constraints, execution order, current receipt, and next executable action. Add/update the plugin plan index. Edit plan files only; do not commit.

## Outcome

Continue remaining scope safely. Delivery-controller repair is a separate shared-infrastructure lane and must not distract the main thread. Begin dormant Site Content repository work now, then continue in dependency order with the translation adapter and resource-handler integration. Keep all three unreachable until separately requested runtime, API, and UI work. Do not publish Site Content through the controller until the separate shared repair is installed and verified. Preserve later release tasks without starting them.

## Acceptance criteria

- DC-01 remains a separate shared-infrastructure repair lane; it must not block starting or verifying SC-REPO-01 locally.
- SC-REPO-01 completes only dormant repository dependencies required by later Site Content slices and remains unpublished until DC-01's shared repair is installed and verified.
- SC-ADAPTER-01 follows repository completion and integrates the existing dormant block-template translation adapter without runtime registration.
- SC-HANDLER-01 follows adapter completion and integrates `SiteContentTranslationResourceHandler` with published request-context contracts and catalog.
- No Site Content route, hook, scheduled job, write path, API surface, UI, feature flag, or visible behavior activates before later runtime/API/UI scope.
- Preserve, do not start: site entry/layout, site overview, Generate All, broader integration.
- Every future slice has isolated acceptance, affected paths, activation state, rollback, blocker limit, deterministic gates, independent review, and delivery receipt.
- Do not duplicate detailed plans. Update their receipts/statuses when their owned work changes.

## Preserved WIP, refs, paths

- Read-only preserved source: `/home/user/Projects/Press.zone/wordpress/wp-content/.worktrees/remaining-release-orchestration`.
- Current isolated worktree: `/home/user/Projects/Press.zone/wordpress/wp-content/.claude/worktrees/ipz-delivery-controller-diagnosis`.
- Published baseline: `origin/master` at `acc6a4d07` when this continuation plan was recorded.
- Published dormant catalog: `555047b35` (`Add dormant site content catalog`) with receipt `61fc6b12b`.
- Published request-context contracts: owner-confirmed on `origin/master`; use published definitions, never preserved-WIP copies.
- Related detailed plans: `docs/plans/2026-08-13-site-content-schema.md`, `docs/plans/2026-08-14-site-content-domain-core.md`, and `docs/plans/2026-08-14-translation-resource-contracts.md`.

## Constraints

- Follow `plugins/international-press-zone/.claude/agents/expert.md` for every implementation slice.
- Preserve dirty WIP. NEVER reset, stash, clean, overwrite, or modify non-plan files during DC-01.
- Use fresh isolated worktrees from current `origin/master` for implementation. Preserved WIP is read-only.
- Treat missing references as delivery-controller defects until DC-01 proves otherwise. Do not retry, force, bypass, or substitute refs.
- Dormant compatible library/schema preparation needs no feature flag. Runtime behavior must remain unreachable.
- Do not contact remote WordPress. Runtime/browser work, when later requested, uses only local `devzone-wordpress` and `e2e-remote`.

## Execution order

1. **SC-REPO-01 — dormant repository.** DONE and published on `origin/master`; remains unregistered and unreachable.
2. **DC-01 — delivery-controller repair.** Installed shared repair and regressions are green. The separate Overdeck source-review blocker remains visible but does not block Site Content delivery.
3. **SC-ADAPTER-01 — dormant translation adapter.** ACTIVE under `plugins/international-press-zone/docs/plans/2026-08-14-block-template-translation-adapter.md`. Integrate only the preserved-compatible library and focused tests against published contracts. Keep unregistered.
4. **SC-HANDLER-01 — dormant resource-handler integration.** Integrate `SiteContentTranslationResourceHandler` only after adapter completion. No controller routing, dispatch, finalization registration, job execution, API, or UI.
5. **Later, inactive release scope.** Site entry/layout, site overview, Generate All, then broader integration. Start only after explicit runtime/API/UI scope and its own detailed plan.

## Current receipt

DC-01 root cause was the shared delivery library treating remote-tracking names as local branch names and constructing nonexistent `refs/heads/origin/master` references during post-land reporting and retirement. The correction is installed in `/home/user/.claude/workflows/lib`, and the focused shared regression passed `118` checks with `0` failures. The installed non-publishing drift check returned `status: ok`. Shared source commit `d2cb36f0e` remains outside this repository; its independent source review is blocked before model execution by a missing generated reviewer extension artifact at `/home/user/.pi/agent/extensions/gpt-sol.ts`. This separate source-landing blocker does not affect the installed controller proof or the Site Content main thread.

Task #80 / SC-REPO-01 passed focused PHPUnit (`12 tests, 63 assertions`), uncached and candidate-aware PHPCS, PHPStan, syntax, diff validation, dormancy search, and independent review. The delivery controller returned `stage: landed`, `status: done`, published the repository to `origin/master`, removed its source worktree, and deleted its branch. The repository remains dormant with no route, hook, scheduled work, API, UI, feature activation, or visible behavior.

Task #81 / SC-ADAPTER-01 is ACTIVE in a fresh canonical worktree under `plugins/international-press-zone/docs/plans/2026-08-14-block-template-translation-adapter.md`. Its frozen scope covers only the adapter library, focused fixtures/tests, and receipts. Read-only exploration confirmed the preserved adapter requires snake_case compatibility updates and that no published runtime registration or consumer exists.

## Next executable action

Implement, verify, independently review, and publish Task #81. Then begin SC-HANDLER-01 without activating runtime behavior. Keep the separate Overdeck source-review blocker visible without diverting the Site Content lane.