Breaking Changes

Breaking changes lists every change that removes or reverses something you may rely on, newest first, with what to do instead. New features and wording changes aren't listed here.

A change we can plan is announced under Upcoming before it takes effect, and moves under its date when it lands. Each page a change affects carries a stamp that links to the entry here: Changing before the date, Changed after it.

30 September 2026

Remove work items no longer complete themselves

A sync completes an Open or Assigned structural work item when its changes already exist in code. A work item with a Remove answer is the exception. A sync can't tell a removed element from a renamed one, so a rename completed the work item although nothing was removed.

A Remove work item now stays open and shows ≠ Drifted once its element is gone. Check the code, then complete it yourself, or leave it to the developer who holds it. Other structural answers still complete themselves, and a sync still confirms a completed Remove with ✓ Confirmed.

Affects Work Items.

Agents no longer publish boards

The publish_board tool is gone from MCP access. Publish from Publish: publishing makes a board readable outside the workspace, so you choose who can see it. A playbook's publish step is now yours: the agent asks you to publish, and the step ticks when you do.

An agent that calls publish_board gets an error that the tool doesn't exist. Update the architect plugin to its latest version so it stops asking for it.

Affects MCP Access, MCP Tools and Playbooks.

24 September 2026

The connect plugin is retired

Grounding a board in a document repo moved from the connect plugin (pmap-connect) into the code plugin, as its /ground command. /ground mirrors an architect-authored board into a document repo, links the board's nodes to the PRDs, RFCs and ADRs that back them, and reports drift.

If you have pmap-connect installed:

1. Install pmap-code from the same marketplace (/plugin install pmap-code@provenmap on Claude Code; pick it from /plugins on Codex) and restart your host.
2. Run /ground in the document repo. It reads the .provenmap/ state the connect plugin wrote (the binding, the mirrored board and the evidence links) as is, so nothing needs migrating.
3. Uninstall pmap-connect. Its last release ships three commands (/start, /help, /update) that print this notice, and it gets no further updates.

The binding credential is unchanged.

Affects The Connect Plugin and The Code Plugin.