Files render in the browser — images, PDF, audio/video, CSV, 3D — and config files open as forms (owner, this week) #7329

The owner, 2026-10-27: "we should render filetypes properly. stls, images, csvs, pdfs, mp3s, mp4s, etc. should all be able to be rendered right there in the browser when you click on the file. lastly, config files should load in a form. so like a json, yaml, etc should have a clean ui to update. a great example is the forge/boards repo. think deeply and nail this. … i want it this week"

Today: only Markdown renders. Every other binary file shows "Binary file — Download", and /raw serves text/plain or an opaque stream.

The goal: click any common file and see it, right there.

• Images, SVG, PDF, audio, video, CSV/TSV and 3D models (STL first) render inline.
• JSON, YAML and TOML config files open as a clean form you can edit and save. Saving commits for a writer and proposes a pull otherwise.
• forge/boards is the acceptance repo: one JSON file per board, so editing a board's panels in the file form must feel as good as the boards editor.

The order:

1. #7330 comes first: the safe media route and the kind registry. Everything else is blocked by it.
2. In parallel after #F1: images (#7331), PDF (#7332), audio/video (#7333), CSV (#7334), 3D (#7335) and the JSON form (#7336).
3. After #JSON: YAML/TOML (#7337), then the boards schema and acceptance (#7338).

Done when every child has landed and the steward has kicked the tires on forge/boards, an STL, a PDF, a CSV and an mp4 at phone and desktop width.

Live triage (automatic, not written by a person): no pillar named, so it waits behind the Later gate; name a pillar to move it.

Owner's direction, 2026-10-27 ~20:00Z: "it could actually be a huge add to the forge. eventually we could build in CAD features, excel features, etc. right now i could also see the dynamic config feature being super cool. the crew could build config as simple files that they edit with text but as a human i could have an interface to adjust things that work directly with the git flow"

What this means for #7336, #7337 and #7338:

• Config is plain files in git. The crew reads and writes them as text, and a person gets a form over the same file. There is no second store and no database copy.
• Every form save is a commit or a pull, so it gets the same review, checks, history and revert as any code change. A person's edit and an agent's edit are both just commits.
• When the crew adds a setting, it ships a schema next to it (a sibling *.schema.json or a .forge/schemas.json entry), so the person's form gets real selects, ranges and help text with no UI work.

Later, not this week: the same pattern for spreadsheets (CSV/XLSX edited as a grid, committed as a file) and CAD (STL/3MF/STEP viewed, then parametric edits). Each is a rich editor over a plain file in git.