feat(action-items): clean generated titles; machine refs → Refs block; carry-forward normalizes - #191
Open
jordanrburger wants to merge 1 commit into
Open
feat(action-items): clean generated titles; machine refs → Refs block; carry-forward normalizes#191jordanrburger wants to merge 1 commit into
jordanrburger wants to merge 1 commit into
Conversation
…k; carry-forward normalizes Rewrite the task-line authoring rules so the bold title is a short natural imperative (no tag/Linear/GitHub ids/hashtags/status/dates/quotes/emoji/ internal em-dash), narrative goes in the body, and all machine refs land in one Refs sub-bullet. Priority is section placement only. Carry-forward now re-authors items into this shape (the sole corpus migration). Main-line 4-field parse contract and parser-corpus.json unchanged; contract + checksum tests green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Engine track (Task 1) of the Action Items redesign — the load-bearing fix. Rewrites the task-line authoring rules in
phases/core/action-items.mdso action items are generated clean at the source rather than cleaned in the app:[#TAG], Linear/GitHub ids, cross-ref hashtags, status words, dates, quotes, emoji (incl. priority 🔴🟡🟢), or an internal—separator.- Refs:sub-bullet (·-separated): Linear ids, GitHub refs, Slack permalinks, cross-ref hashtags, and pure-reference entity wikilinks.[#TAG]verbatim and preserving every fact). This is the entire corpus migration — there is no data migration; the live view converges within a carry cycle.Why
Titles today cram the bold segment with emoji,
[#TAG], Linear/GitHub ids, cross-ref hashtags, dates, quotes, and internal—clauses, so there's no short title to read and "usability is ZERO" (Adam's review). The prior design cleaned this in the app with regexes; the accepted approach fixes the producer and keeps the consumer dumb — no app-side display cleaning.Contract safety
No change to
parser.py,render.py,scout.ids, or the checksum-guardedparser-corpus.json. The new shape is a valid instance of the unchanged 4-field contract: the- Refs:sub-bullet is a sub-line the main-line parser already ignores.Verification
pytest engine/tests/unit/test_parser_contract.py engine/tests/unit/test_parser_corpus_checksum.py -q→ 45 passed.short_prefixextracted, title clean.Part of the two-PR Action Items redesign (spec + plan in Raven-Scout/Scout#76). The scout-app PR (rendering) follows.
🤖 Generated with Claude Code