state-mcp rejects the documented decisions/decisions.md key

Open
#2,378 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
cli, devtools

Research direction

Start by searching the codebase for the rejection text "State mutations are limited to mutable runtime state" to find the allowlist check that squad_state_create_if_absent and squad_state_write hit under the two-layer backend. Reproduce with an absent decisions/decisions.md and confirm the check rejects it while decisions/inbox and log pass. Done means the canonical ledger key can be created and then updated with read-back, unrelated static paths and arbitrary keys are still rejected, and regression tests cover both initial creation and later updates. Check #1876 and #2084 for how the related allowlist was extended.

Written by the indexing model from the issue text.

Description

wave:1-next wave1:P1

Summary

With the current @bradygaster/[email protected] state-MCP server and a two-layer backend, the documented canonical decision ledger key decisions/decisions.md cannot be initialized even when squad_state_read explicitly reports that the key is absent. This blocks the coordinator's required state handshake and stops all work.

Reproduction

  1. Configure stateBackend: "two-layer".
  2. Start the configured state-MCP server (@bradygaster/[email protected]).
  3. Confirm squad_state_health succeeds.
  4. Read decisions/decisions.md; observe State key not found: decisions/decisions.md.
  5. Attempt to initialize the absent key with squad_state_create_if_absent or squad_state_write, using the canonical empty-ledger seed documented by Squad's init procedure.

Actual behavior

Both mutation tools fail with:

State mutations are limited to mutable runtime state (decisions, inbox, casting policy, logs, sessions, scratch files, agent history, and identity). The casting registry/history pair must only be changed through the atomic casting protocol. Static config such as config.json, team.md, routing.md, charters, templates, and skills must not be changed with state tools.

The bridge is not wholly unavailable: health succeeds, squad_state_list(dir: "log") returns existing logs, and squad_state_list(dir: "decisions/inbox") returns existing inbox entries. The logical ledger key remains not found after the failed writes.

Expected behavior

Allow the exact documented mutable key decisions/decisions.md to be initialized and written through the state-MCP API, with successful read-back. Continue rejecting unrelated static paths and arbitrary keys. Add regression coverage for initial creation and normal subsequent decision-ledger updates under a two-layer backend.

This appears related to the state-MCP mutable-key allowlist issues #1876 and #2084, but those cover casting keys and built-in audit-trail keys rather than the canonical decision ledger.

Impact

A healthy state bridge that rejects initialization of a required mutable key leaves an established Squad unable to pass its startup/round-start gate. In this repository the overdue retro gate prevents Ralph's requested dependency-update work from beginning.

Dominant language
TypeScript
Stars
3.4k
Forks
516
Avg merge
1d 15h
Merged PRs (30d)
116

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/squad

All issues in github/squad

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.