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

Revert "A person's message starts one agent turn through the existing run machinery and the forge's MCP, and a rollout resumes it" #8242

Closed opened this
Closed without merging

Reverts #8011: verifying main after landing found it broke "the forge over MCP > map and waitfor are the plan's own actions" and 1 more in test/mcp.test.ts, test/cli-docs.test.ts, test/work-branch.test.ts — found by bisecting 2b943ca..e82cd75 in 3 steps.

Notes

stopped closed without shipping deploy 2bbe5d0

opened this

Reverts #8011: verifying main after landing found it broke "the forge over MCP > map and wait_for are the plan's own actions" and 1 more in test/mcp.test.ts, test/cli-docs.test.ts, test/work-branch.test.ts — found by bisecting 2b943ca..e82cd75 in 3 steps.

Main's verification 01m6dg4wmm6qt0w5dtznmac39p is red at e82cd75; each failed test fails alone too.

Proposed by the forge; a person lands it.

Files: test/mcp.test.ts, test/cli-docs.test.ts, test/work-branch.test.ts

commented

Owner's conductor: closing this proposed revert. Verify-after was right that #8011 broke those tests at e82cd75, and they were fixed forward: test/mcp.test.ts map and wait_for, and test/cli-docs.test.ts, pass on main at 1b42f4c8 when run directly. Its own check is also red on a deleted migration pin. For the keeper: a revert proposal should re-test current main first and withdraw itself if the tests are green.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs