FE-1265: Carry approved contracts into worker execution

.agents/skills/linear-pr-cleanup/SKILL.md

@@ -69,8 +69,10 @@ Explain the concrete change in clear domain terms.
 
 ## How to test
 
-- `npm run verify`
-- Add any manual checks or focused test commands used.
+1. Open a workspace with a committed scope.
+2. Start a build from that scope.
+3. Confirm the proposed slices retain its design and verification context.
+4. Edit the draft scope without committing it, then confirm another build still uses the committed version.
 ```
 
 Rules:
@@ -79,8 +81,11 @@ Rules:
 - Keep each section short.
 - Use accepted domain terminology consistently.
 - Do not paste the whole Linear description into the PR.
-- Include actual verification commands if known.
-- If testing was not run, say so directly.
+- Write `How to test` as two to four numbered user steps with a recognizable starting state, clear actions, and observable outcomes.
+- Prefer one complete happy path and one meaningful edge case over setup detail or implementation terminology.
+- Do not repeat repository-wide commands already enforced by CI, such as `npm run verify`.
+- If the change has no user-facing path, name the focused automated test and the behavior it proves instead.
+- Do not invent testing. If user testing was not performed or the result is unknown, say so directly.
 - If the change involves architecture or a complex flow, add a small ASCII diagram under `What` when it improves clarity.
 - Prefer ASCII diagrams over Mermaid, images, or long prose.
 - Skip the diagram for straightforward changes.

.changeset/steady-workers-carry.md

@@ -0,0 +1,5 @@
+---
+"@hashintel/brunch": patch
+---
+
+Carry exact approved requirements and pinned public packets into scoped execution workers.

memory/PLAN.md

@@ -117,7 +117,7 @@ Everything executor/orchestrator-shaped or Execute-mode-owned belongs to Kostand
 - `execution-comparison-tracer` ([FE-1230](https://linear.app/hash/issue/FE-1230/greenfield-execution-comparison-tracer)) — **active on `ka/fe-1230-independent-oracle-journeys`:** the frozen case, immutable-attempt contract, retained Brunch/Claude v1 pair, and versioned independent browser-oracle journeys are built. Next: restore the exact retained output paths, replay `petri-editor-browser-v2` unchanged against both, then review and promote the bounded evidence; no mutants, judging campaign, or repetitions in this frontier.
 - `end-to-end-comparison-tracer` ([FE-1239](https://linear.app/hash/issue/FE-1239/trace-elicitation-through-execution)) — **complete on `ka/fe-1239-end-to-end-comparison-tracer`, stacked on FE-1230:** two rigorous Petri-editor elicitation outputs crossed exact immutable handoffs into the staged 2×2 Brunch/Claude matrix; all four valid failed cells, unchanged-oracle evidence, and the validity-first requirement ledger are promoted. Definition and retained witness below.
 - `executor-slice-admission-parity` ([FE-1240](https://linear.app/hash/issue/FE-1240/prevent-invalid-scoped-slices-from-reaching-execution)) — **complete on `ka/fe-1240-slice-admission-parity`, restacked on `next` after FE-1239 landed:** incomplete scoped-slice worker context is rejected during deterministic plan admission, exact findings enter bounded repair before `slice_execute`, and the execution boundary remains fail-closed. Definition below.
-- `executor-plan-coherence` ([FE-1250](https://linear.app/hash/issue/FE-1250/build-coherent-execution-plans)) — **implementation complete on `ka/fe-1250-coherent-execution-plans`, based on FE-1240 via `next`:** frontier-verified multi-slice epics now require one ordinary terminal member over every sibling, planner conduct establishes shared foundations, and workers preserve cumulative public contracts for the canonical harness. Fast verification passes; next is the separately authorized unchanged Petri comparison rerun. No new browser gate, durable plan kind, or executor lifecycle phase. Definition below.
+- `executor-plan-coherence` ([FE-1250](https://linear.app/hash/issue/FE-1250/build-coherent-execution-plans)) — **I69-L worker-contract carry implementation complete on `ka/fe-1250-coherent-execution-plans`, based on FE-1240 via `next`:** workers now receive exact cumulative requirement bodies and a hash-verified target-visible packet while controller-only neighbors remain excluded. Deterministic tests and build pass; next is the explicitly authorized unchanged Petri outer witness. No new browser gate, durable plan kind, or executor lifecycle phase. Definition below.
 - `executor-slice-verification-repair` ([FE-1254](https://linear.app/hash/issue/FE-1254/repair-failed-slice-verification-before-halting)) — **implementation complete on `ka/fe-1254-slice-verification-repair`:** terminal failed slice verdicts now enter a finite cycle-qualified Petri repair ladder with crash-durable canonical repair context, grouped validated history, and serial/parallel authority-preserving recovery. The full suite, repository checks, and build pass; next is the owned unchanged Petri comparison rerun. Definition below.
 - `comparison-publication-workflow` ([FE-1251](https://linear.app/hash/issue/FE-1251/publish-traceable-comparison-reports)) — **active on `ka/fe-1251-comparison-publication`, stacked on FE-1250:** capture immutable controller and release provenance before comparison lanes start, then explicitly publish retained validity-first reports into the canonical Notion database through a guarded idempotent skill. Definition below.
 - `prospect-research-workspace-regression` ([FE-1253](https://linear.app/hash/issue/FE-1253/thin-prospect-research-into-a-regression-case)) — **active on `ka/fe-1253-prospect-research-e2e`, stacked on FE-1241:** retain the exploratory mission and calibrated browser/HTTP/SQLite/export oracle while deleting the unexecuted prospect study profile, requirement-ledger expansion, and scored-provider completion gate.
@@ -448,15 +448,15 @@ Instrumentation experiments and far-horizon items. Each re-enters only via re-qu
 - **Branch:** `ka/fe-1250-coherent-execution-plans`, based on `next`.
 - **Kind:** bounded proving frontier — planner conduct and deterministic plan-shape admission over settled D126-L/D130-L and FE-1195 executor seams.
 - **Certainty:** proving.
-- **Status:** implementation complete 2026-07-22; `npm run verify` passes (2531 tests, 2 skipped, build green). Outer evidence remains the unchanged frozen Petri comparison rerun.
+- **Status:** implementation complete 2026-07-24, including I69-L worker-contract carry; the explicitly authorized unchanged frozen Petri rerun remains outer evidence and is not a merge gate.
 - **Objective:** make integration-sensitive multi-slice plans converge on one working result without adding a browser-specific executor gate or a new durable planning concept.
 - **Lights up:** committed scope context → dependency-aware candidate plan → ordinary terminal reconciliation slice → canonical slice verification → existing fan-in and epic verification.
 - **Stabilizes:** the model-planner/admission seam between FE-1240's complete worker context and FE-1195's integrated executor worktree.
 - **Depends on:** FE-1240 candidate-admission parity and the landed FE-1195 slice integration/epic verification topology; FE-1230/FE-1239 provide evaluation evidence only, not target-visible oracle material.
-- **Acceptance:** an integration-sensitive multi-slice fixture produces an explicit shared foundation, dependency ordering, and one ordinary terminal slice that transitively depends on its sibling implementation work and carries the relevant requirement, criterion, design, and verification anchors; workers are told to preserve prior public-contract behavior and use the canonical authored harness cumulatively; the admitted plan lowers unchanged through preview and worker-request parsing; existing slice integration and epic verification execute the shape without a new transition or lifecycle phase; non-integrating plans are not forced to acquire ceremonial closure work.
-- **Verification:** inner — planner prompt/candidate-validation regressions with a contrastive non-integrating plan; middle — synthesis → preview → request → existing integrated epic harness; outer — rerun the frozen Petri comparison unchanged after the product change, retaining its controller-owned browser oracle outside execution.
+- **Acceptance:** an integration-sensitive multi-slice fixture produces an explicit shared foundation, dependency ordering, and one ordinary terminal slice that transitively depends on its sibling implementation work and carries exact cumulative approved requirement content plus the relevant criterion, design, verification, and target-visible packet anchors; workers are told to preserve prior public-contract behavior and use the canonical authored harness cumulatively; the admitted plan lowers unchanged through preview and worker-request parsing; existing slice integration and epic verification execute the shape without a new transition or lifecycle phase; non-integrating plans are not forced to acquire ceremonial closure work.
+- **Verification:** inner — planner prompt/candidate-validation plus I69-L exact requirement-carry differentials that reject ids-only, paraphrase-loss, wrong-link, malformed/duplicate context, hash-divergent packet, symlink destination, and hidden-oracle rivals; middle — synthesis → preview → request → rendered sealed-worker brief plus cumulative terminal-slice integration and serial/parallel artifact parity through the existing epic harness; outer — one explicitly authorized rerun of the frozen Petri comparison unchanged, retaining its controller-owned browser oracle outside execution and outside the merge gate. See SPEC §Verification Design “I69-L worker-contract-carry”.
 - **Boundary:** no hidden-oracle exposure, inferred browser command, new plan-plane node, candidate command surface, execution-time plan repair, or FE-1241 comparison-framework change.
-- **Current execution pointer:** none; the two-card scope is consumed. Re-enter only for the unchanged frozen Petri comparison rerun.
+- **Current execution pointer:** none; the worker-contract-carry card is implemented. Re-enter only for an explicitly authorized unchanged frozen Petri comparison rerun.
 
 ### prospect-research-workspace-regression