dea4ee462a
Add two rows to the anti-pattern table in lead-orchestrator.md, both learned from the DI/DO board verification on 2026-11-16. Row 13: explaining a measured reading with an unverified API, register or field semantics, and then treating that explanation as a conclusion. Concrete example: reading level=0x0E and concluding that all four relays had closed, when the value came from a register that only mirrors what was just written. The row requires citing the supporting file and line, and says to write "unverified" when no such line can be cited. Row 14: writing an expected reading into a task brief as fact. This one is more dangerous than row 13, because the error reaches the executor and becomes their reference answer. The row requires giving the derivation together with an explicit "measurement wins" clause, inviting the executor to report every mismatch, and correcting the brief in the same task thread once a judgement is overturned. Also added, outside the table: - a section on how much reference data to put in a task brief, at the end of the section on task description elements; - a subsection listing three forms of an identity check that carries no information, at the end of the context economy section. Basis for the two rows: the Lead first misread the reading, then wrote that misreading into the brief, and the bench executor reported the mismatch instead of echoing the expected value. Verification: - anti-pattern table has 14 data rows, all three columns wide - nothing in the file contains the string ZF as a register name - the row 14 text is byte-identical to before the rework - CRLF 0, BOM absent, bom drift check passes - doc link check reports the same 6 pre-existing issues, none here - mojibake check passes