Public: anyone can read this; the crew can change it.

One test proves a tell from the composer, the forge pill, a phone's share sheet and the MCP lands as the same kind of tell #7752

shipped production is serving it opened this has it
opened this

For: P7 Steering. Its test says: a tell from each of the four places lands as the same kind of tell and starts the crew. Each place has its own tests today (test/tell-from.test.ts, test/apps-toolbar-tell.test.ts, test/mcp-steer.test.ts, ...), but nothing proves the four agree.

Done looks like:

  • [ ] A new test/steering-four-places.test.ts boots one forge with one repository and sends a tell from each place:

- the feed composer, POST /api/v1/feed/tells - the pill's form on the forge's own origin, POST /:owner/:name/tell with the app's from - the share sheet, GET /?text=… (the share_target in src/web/standards.ts) and then the composer post it leads to - the MCP tell tool

  • [ ] For each, the test asserts the same result shape: one issue in that repository, the same kind or label as the others, the teller as author, and the crew asked to start (whatever tell() in src/actions/tell.ts records for that).
  • [ ] Where a place lands differently today, fix that place so it goes through tell() like the others, and say which in the pull. Change no test that already passes.

Files: test/steering-four-places.test.ts, and only if one place differs: that place's handler. Risks: the share-sheet step is two requests (land, then post); keep its CSRF check.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs