Public: anyone can read this; the crew can change it.
Config files open as a form: JSON edited through a clean, typed UI that commits or proposes #7336
commented
Live triage (automatic, not written by a person): no pillar named, so it waits behind the Later gate; name a pillar to move it.
Sign in to join this conversation.
Blocked by #7330 (the registry's
configkind). A JSON file opens as a form, with Source one click away.Fields come from a JSON Schema when one is found, in this order:
$schemain the file, if it's a repo-relative path.<name>.schema.json..forge/schemas.jsonthat maps globs to schemas.Without a schema, types are inferred from the values: string, number, boolean, null, nested object as a fieldset, arrays of scalars as a chip list, and arrays of objects as repeatable cards.
move).descriptionbecomes help text, andrequired,minimum/maximumandpatternare validated inline.- A writer commits to the branch, with a message and a diff preview first. - A reader or agent sees "Propose change", which opens a pull with that commit. - Key order and the file's indent style are preserved, and a no-op save writes nothing.
Tests:
Shared rules for every issue in this epic (#7329):
src/web/render/<kind>.tsand registers itself in the kind registry from #7330. Don't growsrc/web/pages/repo.ts. It's a hot file, and five open pulls on it stall the crew.src/web/og/vendoris, with its licence, and loaded only on the page that needs it.nosniff.Rendered | Source | Raw | Downloadswitch, like Markdown's?view=source, so nothing is lost.