# Subnautica2Maps Clean Rerun — Repair Acceptance Gate

- task_id: `t_c1d92155`
- tenant: `site-rerun-subnautica2maps-20260520-clean`
- checked_at_utc: `2026-05-20T11:52:21Z`
- owner: 墨策 / 墨测 gate
- verdict: `REPAIR_GATE_BLOCKED`

## 0. Gate decision

07C Product Acceptance, 08 QA, 09 Launch, and 10 Data Review must stay blocked until the three P0 repair tracks pass:

1. Design/media atmosphere repair: real Stitch evidence, or explicit `fallback_visual_review` if Stitch fails again.
2. Asset/media inventory: game/media/YouTube inventory with source, risk, use decision, and fallback per asset.
3. Executable map UX repair: real pan/zoom/layers/controls/semantic map base verified by browser and code inspection.

The previous readiness cannot be treated as launch-ready because the site currently passes many checklist fields while still failing the actual product expectation for a competitive game map.

## 1. Regression evidence read

Primary regression report:

`/root/.hermes/reports/site-pipeline/site-rerun-subnautica2maps-20260520-clean/subnautica2maps/design-map-regression-review-20260520.md`

Key findings:

- Design package was `local-html-fallback`, not true Stitch output.
- Existing visual direction lacks game/site media anchors: no real screenshots, YouTube guide cards, biome visual cards, resource icons, or game-like map preview.
- `/map/` is closer to coordinate scatterplot + list/detail than competitive interactive map.
- Browser/code inspection found `.map-canvas` is CSS grid background only, with no image tiles, canvas/WebGL, semantic SVG base layer, or real wheel/pointer handlers.
- Current map lacks zoom controls, reset/fullscreen, layer panel, scale/cursor/share/copy controls, semantic biome/depth/landmark layers, marker icon legend, and visual route line.
- Mobile map is readable but not map-first; it behaves like a stacked content page rather than a map app with drawer/bottom sheet.

Secondary historical regression evidence:

`/root/.hermes/kanban/boards/site-factory/workspaces/t_b43b2eac/qa-regression-report.md`

Relevant recurring pattern:

- Prior QA already failed mobile overflow, detail/map handoff, schema, and source metadata. The new regression is not only a bug list; it exposes the gate allowing checklist compliance without competitive product quality.

## 2. Blocking status applied / confirmed

Current required downstream gates:

| Stage | Task | Required status | Reason |
|---|---|---|---|
| 07C Product Acceptance | `t_116369fe` | `blocked` | PM must not pass scatterplot-grid map without semantic map layer, even if search/filter/detail exist. |
| 08 QA | `t_453bf37a` | `blocked` | QA must not start final pass until design/media/map repair evidence exists. |
| 09 Launch | `t_52055258` | `blocked` | No GSC/Bing/external distribution before PM+QA repair gates pass. |
| 10 Data Review | `t_6bea352e` | `blocked` | Review metrics are not meaningful until launchable UX exists. |

Repair owner tasks:

| Track | Task | Current gate requirement |
|---|---|---|
| Design repair | `t_82afb4b1` | Must produce true Stitch evidence or explicit fallback visual review; currently blocked after worker crash, so this remains the first operational blocker. |
| Media/legal inventory | `t_bc0c998c` | Must produce asset inventory + compliance strategy before design/frontend claims game media coverage. |
| Map UX repair | `t_883d0c5a` | Must implement and verify real interactive map behavior; cannot deploy as label-only pan/zoom. |

## 3. Hard acceptance checklist for repaired handoff

### 3.1 Stitch / visual design gate

Required evidence, one of:

- `stitch_project_id` plus exported Stitch screens/code references; or
- explicit `fallback_visual_review=true` with reason, screenshots, competitor comparison, and PM/user approval note.

Required pages/states:

- Home desktop and mobile.
- `/map/` desktop map-first workspace.
- `/map/` mobile map-first layout with filter drawer and marker bottom sheet.
- Resource/detail page.
- Guide/media page or section.
- Empty/search/no-results/error states.

Must fail if:

- Handoff says `local-html-fallback` but no explicit fallback review exists.
- The design claims Stitch-native without real Stitch evidence.
- The visual system remains generic sci-fi console with no game-map/media cues.

### 3.2 Game/media asset inventory gate

Required artifact fields per asset:

```json
{
  "asset_id": "string",
  "asset_type": "youtube_video|thumbnail|screenshot_policy|generated_visual|icon|biome_layer|resource_icon",
  "source_name": "string",
  "source_url": "string|null",
  "license_or_risk": "low|medium|high + reason",
  "usage_decision": "embed|link|store_if_allowed|generate_substitute|do_not_use",
  "fallback": "string",
  "attribution_text": "string|null",
  "related_page_or_marker": "string"
}
```

Required coverage:

- YouTube guide/video cards with title, channel/source, embed URL, thumbnail policy, timestamps/chapters where available.
- Safe screenshot policy: official copied assets are not assumed safe; if unsafe, use self-made/generated underwater/biome substitutes.
- Resource/databox/biome icon set with provenance or self-made status.
- Self-made biome/depth/landmark map visual layers.
- Compliance notes: no official/endorsed language, no copied map tiles/icons/text, no hotlinking unknown assets, clear fan-made/no-affiliation disclaimer.

Must fail if:

- Asset list has URLs but no license/risk/use decision.
- Frontend uses thumbnails/assets without source and policy.
- Media repair is reduced to decorative generic images unrelated to Subnautica 2 map/guide intent.

### 3.3 Competitor delta gate

Required competitors:

- IGN Subnautica 2 Interactive Map.
- Game8 Subnautica 2 Interactive Map.
- MapGenie Subnautica 2 map.
- SubnauticaMap / legacy map baseline.

Required dimensions:

- Map layout: map-first vs page-first.
- Filters/layers.
- Marker categories and icons.
- Detail panel richness.
- Progress/notes or save equivalents.
- Mobile interaction model.
- Source/provenance and confidence.
- Our explicit delta: what we match, where we intentionally differ, what remains not-do.

Must fail if:

- Matrix only lists feature names without interaction implications.
- It ignores map-first mobile and executable controls.

### 3.4 Executable map gate

Browser/code verification must prove:

- Real drag/pan changes map transform/state.
- Zoom in/out changes scale/state via buttons and wheel/pinch where feasible.
- Reset restores default view.
- Layer panel toggles visible semantic layers and marker categories.
- Semantic base exists: at minimum self-made SVG/canvas/HTML layer for biome/depth/region/landmark zones, not plain CSS grid only.
- Legend exists and matches marker/icon categories.
- Current-position route helper shows current marker, target marker, line/path, distance/depth delta.
- Coordinate cursor or copied coordinate/share view exists.
- Mobile 390/360/320: map is first-screen primary object; filter drawer opens/closes; selected marker bottom sheet is readable; no horizontal overflow.

Suggested evidence files:

- `browser-map-interaction-evidence.json`
- `map-code-inspection.md`
- desktop screenshot for `/map/`
- 390px mobile screenshot for `/map/`
- `npm run build` output
- production/preview smoke URLs

Must fail if:

- `/map/` is only a scatterplot grid with markers and text details.
- Pan/zoom appears only as copy/label.
- Search/filter/detail fields work but no semantic layer exists.
- Route helper remains text-only without visual line/current/target state.

## 4. PM/QA launch rule patch

PM and QA must use this override before normal checklist scoring:

> If `/map/` lacks a semantic map layer and executable pan/zoom/layer controls, verdict is `NO_GO/P0`, even when search, filters, marker list, detail panel, source fields, or route text exist.

This prevents checklist-pass / product-fail outcomes.

## 5. Re-entry sequence

1. `t_82afb4b1` design repair is unblocked/re-run and completes with Stitch evidence or explicit fallback visual review.
2. `t_bc0c998c` media/legal inventory completes and provides machine-readable inventory + compliance notes.
3. `t_883d0c5a` frontend map repair consumes the design/media contract, commits, pushes, deploys, and provides browser/code evidence.
4. Only then unblock/re-run:
   - `t_116369fe` Product Acceptance.
   - `t_453bf37a` QA.
   - `t_52055258` Launch.
   - `t_6bea352e` Data Review.

## 6. Final gate verdict

`REPAIR_GATE_BLOCKED`.

Do not proceed to PM_GO, QA_GO, launch, GSC/Bing submission, or cold-start distribution until the above evidence is present and the repaired `/map/` passes the hard map gate.