You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem — SEAM 1's extension half landed (the MockSoc rehearsal, the outcome-gated stage, the device-session record with sim pinned true); its UI half — the sim pill + verdict rendering in the panel — cannot land the same way: the overlay is GENERATED from the harmoniqs/opencode fork at the pinned tag, so even the amicode/ UI files are fork files, and hand-edits are drift by construction (the drift gate caught SEAM 1's UI edits exactly as designed). Approach — the fork-first flow: branch the fork, carry the UI edit (device-view + problem.ts verdict propagation, the tests), re-extract the overlay with the extractor against the fork ref (NOTE: the extractor's default tag constant is stale at .14 while the manifest pins .18 — pass --tag explicitly or fix the default), land the overlay+manifest in amicode, with the pin hygiene the fork cadence owner prefers (branch-pin interim + a release tag, per the #634 precedent). Scope — in: the fork branch, the UI edit, the extraction, the amicode overlay+manifest commit · out: any extension-side change (landed).
Acceptance Criteria
The overlay renders the sim rehearsal verdict with the sim pill, failures distinct, and the honest-stub note — sourced from the fork extraction, drift gate green
The manifest pins a resolvable fork ref with its exact sha; the drift gate passes all three checks
Notes
Filed as the SEAM 1 UI half. The fork cadence is shared with the parallel campaign — coordinate the branch/tag etiquette before landing. Director lesson from SEAM 1: never hand-edit overlay/; the extractor is the only door.
Important
Problem — SEAM 1's extension half landed (the MockSoc rehearsal, the outcome-gated stage, the device-session record with sim pinned true); its UI half — the sim pill + verdict rendering in the panel — cannot land the same way: the overlay is GENERATED from the harmoniqs/opencode fork at the pinned tag, so even the amicode/ UI files are fork files, and hand-edits are drift by construction (the drift gate caught SEAM 1's UI edits exactly as designed).
Approach — the fork-first flow: branch the fork, carry the UI edit (device-view + problem.ts verdict propagation, the tests), re-extract the overlay with the extractor against the fork ref (NOTE: the extractor's default tag constant is stale at .14 while the manifest pins .18 — pass --tag explicitly or fix the default), land the overlay+manifest in amicode, with the pin hygiene the fork cadence owner prefers (branch-pin interim + a release tag, per the #634 precedent).
Scope — in: the fork branch, the UI edit, the extraction, the amicode overlay+manifest commit · out: any extension-side change (landed).
Acceptance Criteria
Notes
Filed as the SEAM 1 UI half. The fork cadence is shared with the parallel campaign — coordinate the branch/tag etiquette before landing. Director lesson from SEAM 1: never hand-edit overlay/; the extractor is the only door.