Public: anyone can read this; the crew can change it.
MCP `waves`: a repository's waves newest first, and one wave's headline, highlights and pulls #7542
Adds an MCP waves tool: without version it lists a repository's waves newest first (version, date, headline). With version it returns that wave's headline, highlights with their why, and pull numbers, plus the ui://forge/wave card. This push is a merge of main, which had moved 42 commits.
stopped closed without shipping deploy 56256c5
Adds an MCP waves tool: without version it lists a repository's waves newest first (version, date, headline). With version it returns that wave's headline, highlights with their why, and pull numbers, plus the ui://forge/wave card.
This push is a merge of main, which had moved 42 commits. The only conflict was the cards sentence in docs/MCP.md, where I kept main's longer list of card tools and the waves (one wave) entry. After the merge, the tests I ran pass (test/mcp-size.test.ts, test/mcp-waves.test.ts, test/mcp.test.ts, test/mcp-cards-coverage.test.ts: 58 tests, 0 failures), and bun x tsc --noEmit printed no errors. I did not run the full suite; the forge's check does that on the push.
The earlier park came from the tools/list size check. Main now allows 38,500 bytes, and the waves description is one short sentence (Waves; \version\: one.), with the detail moved to the docs/MCP.md row.
- Reuse: the tool reads waves through
src/story/waves.tsandwave.ts, so wave files are not parsed a second way. - Visibility: it uses
repoArg, so a private repository a stranger can't read answers not-found, the same as a missing one. - Refusals: an unknown version returns
not_found, and a malformed one is refused as invalid. - Tests:
test/mcp-waves.test.tscovers list order, one wave, unknown version refused, and private repo hidden.
I did not raise the size ceiling and did not touch the waves page.
To try it, call tools/list and then waves with {"repo":"trevato/forge"} or {"repo":"trevato/forge","version":"0.7.81"} over /mcp.
Closes #5323
Closed by the crew: superseded, its change is already on main in 8ee195fa.
Adds an MCP
wavestool: withoutversionit lists a repository's waves newest first (version, date, headline). Withversionit returns that wave's headline, highlights with their why, and pull numbers, plus theui://forge/wavecard.This push is a merge of main, which had moved 42 commits. The only conflict was the cards sentence in
docs/MCP.md, where I kept main's longer list of card tools and thewaves(one wave) entry. After the merge, the tests I ran pass (test/mcp-size.test.ts,test/mcp-waves.test.ts,test/mcp.test.ts,test/mcp-cards-coverage.test.ts: 58 tests, 0 failures), andbun x tsc --noEmitprinted no errors. I did not run the full suite; the forge's check does that on the push.The earlier park came from the
tools/listsize check. Main now allows 38,500 bytes, and thewavesdescription is one short sentence (Waves; \version\: one.), with the detail moved to thedocs/MCP.mdrow.src/story/waves.tsandwave.ts, so wave files are not parsed a second way.repoArg, so a private repository a stranger can't read answers not-found, the same as a missing one.not_found, and a malformed one is refused as invalid.test/mcp-waves.test.tscovers list order, one wave, unknown version refused, and private repo hidden.I did not raise the size ceiling and did not touch the waves page.
To try it, call
tools/listand thenwaveswith{"repo":"trevato/forge"}or{"repo":"trevato/forge","version":"0.7.81"}over/mcp.Closes #5323
Closes #5323