@geraldmaron/construct 1.2.3 → 1.3.1

package/rules/common/beads-hygiene.md

@@ -67,3 +67,55 @@ There is no authorized bypass. Beads hygiene is a release gate. If the tooling i
 ## Automation
 
 Project-level automation is tracked in the beads queue: auto-close on merge, pre-push `bd preflight` gate, weekly drift report, memory-contradiction detection. Until that ships, hygiene is a per-session discipline.
+
+## Execution protocol (construct-m7k2 / feature/team-redesign)
+
+Every child bead under epic `construct-m7k2` uses **double validation** before close. Definitions are normative for agents on any model tier (including smaller models).
+
+### Pass A — implementer
+
+The agent that claimed the bead and wrote the code:
+
+1. Run scoped tests cited in the bead acceptance criteria (`npm test` or `node --test tests/...`).
+2. Run bead-specific grep or CLI assertions listed in the bead body.
+3. Record command output in `bd note <id>` or the close reason (exit codes, failure counts).
+
+Pass A is not done if tests were not executed in this environment.
+
+### Pass B — reviewer (different model or fresh session)
+
+A different agent, or the same agent in a new session with no assumed memory of Pass A:
+
+1. Re-run every Pass A command independently (do not trust prior transcripts).
+2. Run `npm run release:check`.
+3. Run `construct doctor` — no new team/auth/MCP warnings attributable to the change.
+4. Confirm no `CONSTRUCT_SKIP_*` / `CONSTRUCT_ALLOW_*` env vars were introduced.
+
+Pass B is not done if `release:check` was not run.
+
+### Parallel runs — verify the committed branch, never a stray worktree
+
+When beads are implemented by parallel subagents in isolated git worktrees, the verify loop must check the **implementer's committed work**, not a fresh tree branched from the base:
+
+1. **Implementers commit to a named branch before review.** No uncommitted worktree state may gate a close — uncommitted work is invisible to a fresh reviewer and is lost when the worktree is pruned.
+2. **Reviewers check out and verify that exact branch** (or the integration branch after merge). A reviewer that branches from the base commit is verifying the *wrong tree*.
+3. **Integration merges the reviewed branch**, then re-runs the close evidence on the merged result.
+4. **Close evidence is reproduced on the merged branch** — e.g. grep the new symbol on the branch, not in a worktree. A symbol that exists only in a worktree is not landed.
+
+Failure mode this prevents (observed 2026-06-25): a bead was closed with a reason naming files that were never committed — the work was stranded uncommitted in a worktree, the reviewer branched from base and "passed" the pre-existing tests, and pruning the worktree discarded the work. A close reason must name only what is reproducible on the branch.
+
+### Baseline-diff close gate
+
+When the suite is not green (pre-existing unrelated failures), "all tests pass" is unsatisfiable and invites premature closes. Use a baseline-diff instead:
+
+1. Capture the failing-test set once at the start (e.g. `.cx/artifacts/baseline-fails.json`).
+2. A bead may close only if its scoped tests pass **and** the full suite introduces **zero new failures** vs the baseline. Newly-passing tests are a bonus, not a requirement.
+3. A test that fails on genuinely out-of-scope incomplete logic is marked `node:test` `todo` with a tracking bead id — flagged, not hidden — never silently skipped.
+
+### Bead body template
+
+Child beads must include sections: Goal, Read first, Out of scope, Steps, Acceptance criteria, Pass A checklist, Pass B checklist, Do not touch. See `construct-m7k2.9` for the gate bead that introduced this contract.
+
+### Gate bead
+
+Claim `construct-m7k2.9` first on the epic branch to land this section, then proceed to `construct-m7k2-fix-tests` and downstream work per the dependency graph.

package/rules/common/neurodivergent-output.md

@@ -1,11 +1,11 @@
 ---
 description: every human-facing Construct output is formatted for neurodivergent readers — without reshaping machine-readable output.
-enforced_by: (persona prompt), tests/term-format.test.mjs, construct dashboard:sync --check
+enforced_by: (persona prompt), tests/term-format.test.mjs
 precedence_tier: style
 ---
 # Neurodivergent-Friendly Output
 
-Construct's output is read under load — in a terminal, mid-task, often by people who process text differently. Dense walls of prose, buried conclusions, inconsistent structure, and meaning carried only by color cost every reader attention, and cost neurodivergent readers more. This rule applies to **every human-facing output** Construct produces: terminal output, agent prose to the user, reports, error messages, and the dashboard.
+Construct's output is read under load — in a terminal, mid-task, often by people who process text differently. Dense walls of prose, buried conclusions, inconsistent structure, and meaning carried only by color cost every reader attention, and cost neurodivergent readers more. This rule applies to **every human-facing output** Construct produces: terminal output, agent prose to the user, reports, and error messages.
 
 It is a `style` rule by design. The precedence resolver (`rules/common/precedence.md`) guarantees a style rule never overrides a higher tier — so when accessible formatting would conflict with correct machine output, correctness wins automatically. Section 0 states that boundary explicitly.
 
@@ -13,8 +13,8 @@ It is a `style` rule by design. The precedence resolver (`rules/common/precedenc
 
 Two layers, treated differently:
 
-- **Presentation layer (human-facing)** — section titles, prose, help text, report narratives, guidance notes, error wording, dashboard markup and CSS. This is what the rest of this rule shapes.
-- **Data layer (machine-readable)** — never reshape it for readability. Off-limits: any `--json` / `--plain` output; `specialists/registry.json`, `contracts.json`, `role-manifests.json`; the parsed tokens hooks emit (for example the session-start `## Working branch: **<name>**` line, the efficiency status enum `degraded` / `configured` / `healthy`, commit hashes, counts); auxiliary state JSON; any text one component parses out of another.
+- **Presentation layer (human-facing)** — section titles, prose, help text, report narratives, guidance notes, error wording. This is what the rest of this rule shapes.
+- **Data layer (machine-readable)** — never reshape it for readability. Off-limits: any `--json` / `--plain` output; `specialists/org`, `contracts.json`, `role-manifests.json`; the parsed tokens hooks emit (for example the session-start `## Working branch: **<name>**` line, the efficiency status enum `degraded` / `configured` / `healthy`, commit hashes, counts); auxiliary state JSON; any text one component parses out of another.
 
 When a format choice would change a value, key, ordering, or token that something downstream parses, do not make it. Accessibility is presentation; it never edits the contract.
 
@@ -47,19 +47,16 @@ End human-facing output with the current state and the next action in plain word
 - Meaning carried by color must also be carried by text, shape, or label. A red number is also labelled `error`; a green check is also the word `passed`.
 - Honor `NO_COLOR`, non-TTY, and `TERM=dumb`: degrade to plain text, never to nothing.
 - Respect terminal width — wrap rather than overflow.
-- On the dashboard, honor `prefers-reduced-motion` and `prefers-color-scheme`; motion is never required to understand state, and animation can be fully disabled.
 
 ## Applies to
 
 - **Terminal / CLI** — help text, status, reports, hook display. Routed through the shared formatter (`lib/term-format.mjs`); color and width handled there, never per-call.
 - **Agent prose** — every response Construct and its specialists return to the user.
-- **Dashboard** — `apps/dashboard/` source (semantic landmarks, labels, focus, contrast, reduced-motion), rebuilt into `lib/server/static/`.
 
 ## Enforcement
 
 - Persona prompt: `personas/construct.md` carries the output-style directive; specialists inherit the standard through the front-door agent.
 - `tests/term-format.test.mjs` asserts the terminal formatter honors `NO_COLOR` / non-TTY and that machine-readable `--json` output is unchanged by presentation changes.
-- `construct dashboard:sync --check` keeps the built dashboard in step with the accessible source.
 
 ## Bypass
 

package/rules/common/research.md

@@ -58,6 +58,8 @@ Start with the narrowest authoritative source that can answer the question:
 4. **Tertiary sources last**
    - blogs, forums, Q&A, analyst summaries, AI-generated summaries
 
+When the research is specifically about a library/framework/API/cloud-docs surface, a docs MCP such as Context7 is an acceptable way to reach the official documentation. It is a retrieval path, not the evidence standard. If that MCP is unavailable or incomplete, fall back to direct web search and fetch against the official docs, changelog, and release notes. Do not block research on the presence of a single docs integration.
+
 ## 4. Required metadata for every source
 
 Record: