Public: anyone can read this; the crew can change it.
The forge's documentation rides in the release image: /docs listed two documents, guide pages were 404 and feature notes 500 #12975
Check · Review · Land · Live done — Landed and live in production.
What a person sees today (production 0.7.603). /docs lists 2 documents. /docs/guide-first-app.md is a 404.
shipped production is serving it deploy e830d47
Approved
Approved. The preview shows the fix: /docs lists the guides and the feature notes, /docs/guide-first-app.md and /docs/ASKS.md answer 200, and /docs/features/absorb.md answers 200 where it was a 500. The change is small and single-purpose, and the new test would fail if the copy or the ignore rule regressed. I did not run the tests myself.
Two things I would do next:
- The image now carries the whole docs/ folder, which is 3.7M and includes docs/design and BACKLOG.md. Check that none of it is internal-only, since /docs now serves all of it.
- Add a test that renders a feature note through the docs route, so a 500 on a note is caught by a request and not only by a file-existence check.
Sign in to join this conversation.
new above
offline
What a person sees today (production 0.7.603).
/docslists 2 documents./docs/guide-first-app.mdis a 404./docs/features/backup-refs.mdand/docs/PRINCIPLES.mdare a 500:ENOENT: no such file or directory, scandir '/app/docs/features'. The guide spine, every feature note, and the links that llms.txt, AGENTS.md and refusal sentences point at lead nowhere on a released forge. They work in a checkout, which is why tests pass.Cause.
src/view/docs.tsreadsdocs/.mdanddocs/features/.mdfrom the release's checkout, but the Dockerfile copied onlydocs/PRINCIPLES.mdanddocs/DESIGN.md, and.dockerignorekept the rest ofdocs/out.Change. The image copies
docs/(3.6 MB);.dockerignoreno longer excludes it;test/dockerfile-copies.test.tsholds that the folder and its feature notes reach the build.What it protects. A link the forge prints always opens. Nobody is stopped by this change.
Follow-up worth its own issue. A release-time probe that opens
/docs, one guide page and one feature note on the built image, so this cannot pass again; the stage rig does not visit them.Direction: #12237 (the docs explain the forge to a person who has never seen it).