The agent's own pages carry no developer details: the commit badge, the API/MCP line and the notes link move to a "For developers" page #131

Intent: on the agent's pages, the shared header shows the commit (src/pages/layout.ts:81) and the footer reads "Also at /api/listings (described) and POST /mcp … Team notes" (src/pages/layout.ts:93). That is developer chrome on a product a realtor sees in a sales meeting.

Done looks like:

• [ ] On /, /listings/:id, /week and the other agent pages, the shared layout's header and footer show no commit hash, no /api, openapi.json or /mcp line, and no notes link. The env pill (production or preview) may stay.
• [ ] A server-rendered /developers page, linked once from the footer in small type as "For developers", holds what was removed: the build/commit, /api/listings, /openapi.json, POST /mcp and the notes link. It also has a terminal line that prints FORGE_APP_SSH verbatim, or says the terminal is off when that is unset.
• [ ] The buyer-facing face on the property page stays exactly as it is.
• [ ] Every route, permission and contract.json cell is unchanged. Only where the links live changes.
• [ ] Tests: / contains no commit hash and no /mcp. /developers answers 200 with the commit, /mcp, /openapi.json and the terminal line, both with FORGE_APP_SSH set and unset. Existing tests that asserted these on / move to /developers, and the pull says which.
• [ ] bun test and bun scripts/design-lint.ts pass. The README names the page in one sentence.

Files likely: src/pages/layout.ts, new src/pages/developers.ts, src/routes.ts, the footer tests, README.md.

Risks: forge checks may look for the build marker or terminal line. Keep both reachable at /developers.

Suggested crew: builder.