fix(maps): seal Incuna void boundaries

[zoeyrose]

Summary

• seal the six exposed Forgotten Tunnels seam cells with authored blockers
• fill the missing Under the Barn floor cell
• seal the Water Well seam corner, channel outlets, and secondary aperture without changing the puzzle machinery or intended passages
• refresh only the semantic light-review hashes shifted by these authored map edits

Closes #197.

Release line

This targets main only. The issue explicitly designates 1.x as immutable rollback and migration evidence and does not authorize a backport.

Coordinates

• Base branch/SHA: main at 65a88167d3a2bedcc2dc21508d94d7ca009a76d2
• Head branch/SHA: fix/197-incuna-boundaries at c5b0a693fd9ef8c81534c549e30452cefdce6589
• Worktree: /workspaces/atrinik/workspace/worktrees/content/issue-197-incuna-boundaries-main
• Commit: c5b0a693f fix(maps): seal Incuna void boundaries

Validation

• python3 tools/validate.py
• python3 tools/world_content_audit.py lights --check
• python3 tools/build_runtime.py --target classic --source-commit c5b0a693fd9ef8c81534c549e30452cefdce6589 --output build/issue-197-classic-runtime
• python3 /workspaces/atrinik/build/reviews/atrinik-content-197-scan.py /workspaces/atrinik/workspace/worktrees/content/issue-197-incuna-boundaries-main (90 maps, all 34 listed transitions, preserved seams, and scoped static exits)
• git diff --check

The issue's abbreviated build_runtime.py --target classic command omits the current CLI's required --output; the validation above uses the repository-documented isolated-output form.

Runtime capability and verification

The supported main-line profile is pinned to the final content worktree:

./atrinik profile show issue-197-incuna-main --json
./atrinik topology show issue-197-incuna-main --state default --json
./atrinik build content --profile issue-197-incuna-main --test

The first two commands resolve atrinik/content@main at c5b0a693fd9ef8c81534c549e30452cefdce6589. The build command currently reports that content has no wrapper build/runtime contract for the default stack. Replacement build, topology, and scenario integration remain tracked by atrinik/atrinik#266, atrinik/atrinik#269, and atrinik/atrinik#270.

No topology or scenario was created: routing this main-line worktree through the Classic content-1x@1.x provider would mix providers and violate the issue's explicit frozen-1.x rule. Until the tracked adapters land, repeat verification with the owner-native validation commands above and the ignored 90-map acceptance scan. The original real-entrance and controlled water-walking/flying playtest remains capability-blocked rather than being substituted with unrelated Classic content.

Two independent whole-diff reviews and a fresh final pass found zero known actionable findings. Final local validation and all latest-head required checks pass at c5b0a693fd9ef8c81534c549e30452cefdce6589.

[zoeyrose]

Delivery review complete at c5b0a693fd9ef8c81534c549e30452cefdce6589.

• Two independent whole-diff reviews plus a fresh final pass found zero known actionable findings.
• Final owner validation, the zero-unreviewed lighting audit, the 90-map/34-transition acceptance scan, the clean Classic target package, and git diff --check pass.
• All latest-head required checks pass; the PR is mergeable and has no review threads or comments.
• Main-line integrated runtime remains unavailable under Workspace: add Go, Cargo, Protobuf, renderer, toolkit, and website build contracts atrinik#266, Workspace: supervise canonical and classic topologies with isolated state atrinik#269, and Workspace: provision deterministic replacement account and character scenarios atrinik#270. No Classic content-1x substitution, topology, scenario, or shared-state mutation was used.

The issue remains open and this PR will not be merged here. Required human approval remains the only merge gate.