state-mcp rejects the documented decisions/decisions.md key
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 55/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- typescript
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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
- Configure
stateBackend: "two-layer". - Start the configured state-MCP server (
@bradygaster/[email protected]). - Confirm
squad_state_healthsucceeds. - Read
decisions/decisions.md; observeState key not found: decisions/decisions.md. - Attempt to initialize the absent key with
squad_state_create_if_absentorsquad_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.
- Lingua principale
- TypeScript
- Stelle
- 3.4k
- Fork
- 516
- Merge medio
- 1g 15h
- PR unite (30g)
- 116
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di github/squad
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di github/squad
Issue simili
-
bot:ai-assisted component:platform-js status:untriaged
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 74/100
midnightntwrk/platform-js#38 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
ranxianglei/billion-context#7068 ·
I maintainer di solito rispondono entro 1 giorno
-
vendor: bump whisper.cpp past 6a8addd — the current pin aborts the app on a failed Metal initAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
mybigday/whisper.rn#348 ·
-
enhancement severity:low
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
Battle-Cattle/BCUK-Bot-4#1075 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 67/100
ilan-pinto/roaring-lions#1552 ·
I maintainer di solito rispondono entro 1 giorno