Development record
docs fidelity --apply writes each drafted replacement into .abcd/work/brief-review-flags.json, but the sentence a person then tidies by hand before committing (grammar, a half-replaced wrapped line, a flag name the chapter prose may not carry) is not what the flags file records: in the v0.13.0 cut, five chapters (10-docs, 15-prepare-this-repo, 22-site, 23-reading, 27-implement) landed wording that differs from the flagged replacement, so the record of what the product thinker must read names text that is not in the brief.
issueresolvedminoriss-2610050259233425
docs fidelity --apply writes each drafted replacement into .abcd/work/brief-review-flags.json, but the sentence a person then tidies by hand before committing (grammar, a half-replaced wrapped line, a flag name the chapter prose may not carry) is not what the flags file records: in the v0.13.0 cut, five chapters (10-docs, 15-prepare-this-repo, 22-site, 23-reading, 27-implement) landed wording that differs from the flagged replacement, so the record of what the product thinker must read names text that is not in the brief.
Grounds
- pursued: record-lint over the tree reports no brief_flag_landed finding and a hand-tidied replacement is reported on its flag's line; shown wrong by a flag whose replacement its chapter lacks passing record-lint, or a current flag being reported
Frontmatter
| id | iss-2610050259233425 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610050259233425-docs-fidelity-apply-writes-each-drafted.md
open on GitHub ↗ · commit history ↗