Objective: prepare the synthetic prototype in PR #71 for Morgen’s review, while Industrial Atlas validates Hamilton independently. Tools may be Codex, Claude Code or Cursor according to the assigned task. Existing references: NA-32 epic; NA-305 browser notice; NA-308 run records; NA-309 addresses without parcels; NA-310 experience profiles. Linked Linear issues own task status.
This documentation PR is based on PR #81 at 6ff9756, branch hm-front/handoff-2026-10-18. Until these changes reach main, use the documentation PR’s head ref for instructions and the assigned implementation branch for code. A checkout of main alone may lack both these instructions and web/. Refresh PR heads, base revisions and conflicts at pickup.
Agents never merge. Before merging, verify whether the changed paths trigger publication and whether jurisdiction approval applies. The earlier review’s Pages/Railway observations are historical evidence, not a current verification for every change. No public publish/deploy without Morgen’s jurisdiction gate sign-off; building/testing deploy tooling is allowed.
PR #80 records the merged split plan; split execution and identifier migration require a separate assignment from Morgen. Preparing or merging #71 does not resume the split, move files or authorize wire/package renaming. Keep heavymap_id and current schema names until a separately accepted contract migration.
Work against invented synthetic contract fixtures. Real-data integration uses a pinned screened Atlas artifact when eligible. Do not change the Atlas pipeline, scripts or dataset truth under a frontend assignment. The explicitly assigned #71 conflict repair may preserve/append existing documentation and sheet rows as its review describes. Do not commit production tiles/shards, dist/, local-data/ or identifying values. Existing approved small synthetic test fixtures are distinct from production outputs. Do not access heavymap-restricted.
Assign one implementation owner on codex/heavymap-v0-frontend. The branch name does not require Codex to remain its owner; record any transfer before another agent writes it.
Done means the bounded repairs are reviewable, conflicts addressed, npm tests/build and applicable Playwright checks run against that branch, and skipped/unrun checks explained. Return PR/head SHA, B/S checklist, test evidence and synthetic screenshots where useful. No merge. A full adapter, all gap/sliver states and responsive enhancements are follow-on tasks, not implicit #71 repairs.
Use NA-318 for the schema-v1 adapter, NA-319 for gap/sliver fixtures and NA-320 for desktop/mobile interaction/accessibility. Their acceptance stays separate from NA-312. NA-316 owns the pinned-artifact integration.
A separate owner may draft HM-15 CI, HM-04 screening design or HM-13 build-only deployment design. No overlapping edits to the prototype owner’s worktree.
CI validation must name a branch containing web/. Either wait for #71 to land, or explicitly stack on its current head and record that dependency; do not claim a successful web check against main without the files. Record any later Firefox coverage as a separate acceptance result.
HM-03 adapter, HM-05 gaps, HM-07 slivers and HM-08 browser notice may use explicitly based follow-on branches and agreed fixtures. Real-data integration waits for an eligible artifact, not for the entire Atlas backlog. HM-02 depends on D1; HM-06 on D3/D4; HM-11/HM-12 on D2.
D1 (Pages strategy), D2 (startup budget meaning), D3 (held-info presentation), D4 (withheld_disclosure) and D6 (Railway) remain open unless separately recorded as decided. D7 is complete: Morgen authorized the Linear project updates and both descriptions, resources, outcome milestones and dated updates were applied. This supersedes #81’s STOP on editing the project description for that authorized work. D4’s manifest_entry is interim. No settings/Linear changes are authorized by a recommendation in the backlog.
D5 has one destination: heavymap-planning/frontend/19-process-insights.csv with HM-PI IDs. The earlier alternate paths are superseded. Until that file exists, put reusable frontend findings in the PR’s Process insights section using the shared columns; never put HM-PI rows in Atlas sheet 19. Existing pending HM-PI-0001 through 0008 remain in backlog section 4; reverify historical observations before using them as current evidence.
Recorded state, 2026-10-18: PR #81 head 6ff9756, PR #71 head 1d74db5 (draft, conflicting), PR #80 merged as plan-only at 6333e55; migration execution remains separately assigned. These are snapshots, not permanent instructions. The old review reports npm checks/build passed but Playwright unrun; this documentation change makes no new runtime claim.
BE-1 through BE-16 are drafted asks, not delivered capabilities. Use current dossier schema v1, suffix-based shards and 0-1 share fractions. The register in backlog section 3 holds interface details and exact blocking scope; task status belongs to linked Linear issues. Each shared change has one preparing owner and a named Atlas reviewer.
Next action: use NA-312 under frontend epic NA-32 for the bounded #71 repair packet, refresh branch state and collect review evidence. Already-authorized Atlas operational validation proceeds concurrently. Follow-on tasks and first artifact integration receive their own acceptance claims.