trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- docs/MCP.md describes the boards tools: `boards`, `board_write`, `board_delete`, `board_pins`
- docs/MCP.md describes the forge family and following tools: `contribute`, `family`, `follow_mode`, `forges`, `forge_proposals`, `propose_to_parent_forge`, `sever`
- docs/MCP.md describes the inbox decision tools: `asks_decide`, `asks_proposal`, `asks_undecide`
- docs/MCP.md describes the accounts and access tools: `access`, `account_role`, `mint_invite`, `signup`, `whoami_can`
- A test fails when an MCP tool has no row in docs/MCP.md
- require_checks, red half: a failing head refuses the merge and its preview still answers, every time
- The OpenAPI document describes browsing an origin's code: branches, tags, labels, paths, tree, blob and commits
- `.map-tool` leaves the map's stylesheet: no control renders it
- `.number` leaves the stylesheet: an issue's number in a heading draws from base utilities
- `.hex` leaves the stylesheet: the settings colour value draws from base utilities
- The OpenAPI document describes browsing an origin's conversations: its issues and pulls, the lists and one of each
- `.tok-plain` leaves the stylesheet: the highlighter never writes it
- The `.bt-*` rules leave the stylesheet: no page renders them
- `.front-featured` and its parts leave the stylesheet: no page renders them
- The OpenAPI document describes an issue's dependencies, a crew seat, a secret and the front page
- A test fails when a new GET /api/v1 route names no Server-Timing phase
- Browsing an origin names its Server-Timing phases: session, origin, render
- The telemetry reads name their Server-Timing phases: session, read, render
- The OpenAPI document describes itself, a migration job and its stream, and opening an app
- The OpenAPI document describes editing a pull, its reviews, approving it here and assigning an issue or pull
- The OpenAPI document describes a repository itself: create, read, edit, delete and its upstream
- "origin sync: incremental, event-shaped, and polite > a conditional request is answered from the cache, not refetched" passes every time on a loaded check machine
new above
offline