[autohub-codex]

The Townmap’s “100%” scale previously depended on panel width at startup, so two loads at the same labelled zoom could render almost three times apart. Anchor the default to the artwork grid and provide an explicit closer walking view.

• Town uses one CSS pixel per artwork pixel; Walk uses 2× and frames Jack without moving him. V switches views; 0 returns to Town.
• Keep readable hover details outside canvas scaling, and remove the old fit-scale compensation from district packing.
• Preserve cottage positions, walking, room visits, live agent activity, and the existing Dispatch/Threads views.

Review contract

• The same zoom must have the same CSS scale across startup widths, delayed feeds, resize, fullscreen, and fleet growth.
• Camera changes must not teleport Jack or relocate existing cottages.
• Room entry/exit must preserve the outdoor zoom; cottage hit testing must work at both scales.
• Feed status and recorded relationships remain authoritative; this change adds no agent writes.

Validation

• npm test: 539 passed, 0 failed.
• Local Codex review (gpt-6.1-sol, medium): no actionable findings.
• Real browser checks against live Hub: narrow/fresh/resized desktop loads, Town/Walk, V, WASD, hover, 2× cottage click, room entry/exit, fullscreen, Overview, Dispatch and Threads. Existing plot coordinates stayed fixed through camera changes and live polls; no browser console errors observed.
• Extended the viewport browser regression journey and checked its syntax. The Browser Hand CLI journey was not run; visual verification used the connected in-app browser.

Breaking changes: none to the feed API. The meaning of 100% intentionally changes to native artwork pixels.
Related issue: none; requested and approved in the CottageCode design chat.

Implementation harness: Codex desktop. GitHub identity: AutoHub Codex GitHub App.

[jack-arturo]

@codex review

[chatgpt-codex-connector]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-10T02:13:30.234487Z	834f076	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Already looking forward to the next diff.

Reviewed commit: 834f076d9d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[autohub-codex]

Babysit complete — verified green at 834f076d9d5944238076f399ae72aa69f2dba76d.

• Local Codex review (gpt-6.1-sol, medium) and hosted Codex review: clean, no findings or open threads.
• CI smoke passed on this head and ran the syntax and live /agents checks.
• 539 Node tests passed. Browser checks covered Town/Walk, resize, fullscreen, room entry/exit, evidence tabs, wildlife, and connection to the restored live Hub feed.
• Size: 182 changed lines; one hosted review window; zero remediation pushes; one guarded baseline request after automatic grace.
• Mergeable with main; no code changes during review. The published commit preserves the reviewed tree and restores the configured GitHub App author attribution.

Implementation/review orchestration: Codex desktop via AutoHub Codex GitHub App. The user explicitly authorized merging after these gates pass.