trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- The .bt-* rules (bar, grid, group, hist, name, procs, row, val) leave the stylesheet
- MCP `forks`: a repository's forks the caller may see, each with how far ahead and behind it is, as /forks shows
- MCP `forks`: a repository's forks the caller may see, each with how far ahead and behind it is, as /forks shows
- The OpenAPI document describes the caller's origin apps: list, add and remove
- A component gallery at /design/components, where the parts the cold-read audit blames are judged
- The OpenAPI document describes the caller's origin apps: list, add and remove
- .repo-lineage leaves the stylesheet
- A crew pull that has stayed conflicted for 3 days with no push is closed with one line, and its issue goes back to ready for a fresh run from main
- The OpenAPI document describes the caller's origin apps: list, add and remove
- MCP `tell` takes `from` (a page URL on this forge or one of its apps) and the tell records it as where it was said, as a tell from the toolbar does
- releases.json's test reads past 200 releases a hundred at a time, as a child does
- /llms.txt lists every MCP tool with its one-line purpose, generated from the tool registry, and a test fails when one is missing
- /llms.txt lists every MCP tool with its one-line purpose, generated from the tool registry, and a test fails when one is missing
new above
offline