Files
STM32F4-Base/.dsh
wandering1 ab20302999 refactor(agents): split entry file from role knowledge, add orchestration role
The entry file had grown to 194 lines, of which a large part duplicated
knowledge that already lived in skills, docs or role files. Worse, three
pieces of project knowledge existed only there, and ten roles were all
module implementers or reviewers: no role carried the Lead side
collaboration protocol, so "Lead only orchestrates, never implements" and
"the reviewer must not be the implementer" had no home anywhere.

AGENTS.md 194 lines / 13908 B -> 121 lines / 12283 B, 13 sections -> 9.
- Dropped four sections whole, each with an existing landing point:
  build and verify (keil-build / serial-boot-test skills), Python env
  (new-machine-setup skill), hardware pins (hardware spec doc section 2),
  docs and diagrams (writing standard plus draw-diagram skill).
- Compressed project overview, iron rules, pre-commit, platform
  constraints and module conventions into pointers plus the few facts that
  must be seen every turn.
- The directory map changes from "directory | responsibility | can I
  modify it" to "directory | can I modify it" and hands the detail to the
  architecture overview section 7. The value of this table on the entry
  file is the permission semantics, not a second copy of the tree.
- Delegation policy is the one section that grows in substance: four
  always-present rules, reviewer is not implementer, rework needs fresh
  evidence, the gate flow, three measured limits of the ledger plugin and
  member revive/rebind.

Three machine anchors are untouched: the TASK_TABLE comment pair and its
body, the BOM list line (one line, four paths, the bom-drift checker
concatenates every line containing BOM), and the hook count sentence.
Line endings stay CRLF.

New roles:
- .dsh/roles/lead-orchestrator.md: the Lead collaboration protocol in two
  parts, generic methodology and this project's specifics. Twelve
  anti-patterns with the case behind each, an eleven-role split table
  (what it owns, what it must not touch, when to call it), and ten
  documented gaps between what the entry file claimed and what
  dsh-plugin-team-ledger v0.2.0 actually does.
- .dsh/roles/bench-runner.md: bench execution and evidence collection, an
  execution layer and explicitly not a decision layer. It has no write
  tools and no gate submit/accept, because the person who reads the log
  must not also judge the run.

Existing roles:
- mcu-specialist gains the kernel-before-start rule, including the legal
  counterexample vTaskDelete(testTaskHandle) in Src/freertos.c. The
  criterion is not "create or delete" but whether the call waits for the
  scheduler or for time.
- algo-specialist gains the RS-485 wiring gate with the two contract
  defects it stands on: a weak rx hook with a single 256 byte buffer, and
  a direction switch back to RX that does not wait for TC.
- storage-specialist's owner statement is rewritten rather than appended:
  defaultTask owns the config engine because its static state is unlocked,
  and reading still advances the poll baseline and the debounce counters.
- README: eleven roles, order unified across the overview table, the
  detailed sections and the selection guide.

Verified: gen_task_table --check, bom drift, mojibake, generated fresh and
doc links all clean, and doc links report the same six pre-existing
findings as before this change. Role files are CRLF free, no BOM.
2026-11-16 19:37:15 +08:00
..