Correct the board-automation sentence in the erecto workflow block

[edgariscoding]

Summary

The shared workflow block that erecto writes into every repo's CLAUDE.md says "the board never moves cards automatically". That is wrong for any GitHub Project with the built-in "Item closed" workflow turned on, because closing an issue moves its card to Done. A repo that also turns on "Auto-add sub-issues to project" adds sub-issues without a manual step. A session that trusts the sentence tries to move a card that already moved, or trusts a board that has drifted.

Technical detail

The sentence is in plugins/erecto/skills/erecto/assets/invariants-block.md, in the "Work is tracked in GitHub issues" bullet:

Where the project uses a board, move the issue's card as work progresses — the board never moves cards automatically.

protego-app has already changed its copy to this text, in commit 7f7c9f55:

Where the project uses a board, move the issue's card as work progresses. Only the automations the project names (Project constants) move a card for you, so check the card after each step.

protego-app lists its two automations in release/project.md ("Board"). Its Project constants "Work tracking" bullet points there.

Decisions

• Chose to point to the project's own list of automations instead of naming "Item closed" in the shared block. Which workflows a board has turned on differs per project, so the shared block cannot state it.

Done when

• invariants-block.md holds the new sentence. Evidence: the file diff.
• erecto's interview, or its generated Project constants, has a place to record which board automations the project has turned on. Evidence: a scaffold run on a scratch repo shows the field.
• protego-app's CLAUDE.md block matches the template byte for byte again. Evidence: diff of the two blocks.

Out of scope

• Changing any project's board workflows.

Notes / links

• Found during a protego-app docs audit on 2026-09-23. The board's workflows were read with a GraphQL query of projectV2.workflows.