Repository navigation
Name each domain event's raiser and adopt devbook 1.16.0 - #937
Merged
github-actions[bot] merged 1 commit intoOct 2, 2026
Merged
Conversation
Reconcile devbook 1.13.0 -> 1.16.0 (contract 25, additive, no migration): the devbook-meta tools gain units.mjs and the sync field, and four .agents/rules copies are refreshed. The customized devbook-meta.yml workflow is left alone. Trim `related` on all 13 domain events to the aggregate or domain service that raises it; consumers stay in each event's Consumers section. Drop the bare `tag` alias from Tasks' Roadmap Tag and the bare `roadmap` alias from Devbook's Roadmap Contribution, which resolved into several units. No `sync` direction is set yet: every unit stays on `report`. ai/05 records the pull and push sweeps as candidates beside devbook-verify; tech/ and ADR 0016 record 1.16.0 and contract 25. units.mjs --groups: 167 groups of 167 units; 0 set aside; 0 orphans (was 14). build.mjs --check: 0 errors. check-metadata: 0 blocking. Devbook unit tests incl. DevbookBuilderParityTests: 98/98. Plan item backlog-sync-tags (+devbook-sync-sweeps). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
4 of 5 tasks
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
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
Plan item
backlog-sync-tagsof+devbook-sync-sweeps: get Backlog's devbook ready for the devbook sync sweeps.devbook 1.13.0 → 1.16.0 (contract 24 → 25, additive, no migration).
.devbook/_tools/devbook-meta/is refreshed withunits.mjsand thesyncfield, and four.agents/rules/devbook-*.mdcopies are refreshed. The wrappers and the AGENTS.md section were already current.devbook-meta.ymlis customized and left alone.Domain events name their raiser.
relatedon all 13 events now names only the aggregate or domain service that raises the event. Consumers were listed there too, which made 9 events orphans inunits.mjs. They stay in each event's### Consumerssection. Each raiser comes from the event's own "Published by/when" line. RoadmapItemScheduled pointed only at Progress Signal, its consumer, and now names Roadmap Plan.Term orphans. Two aliases resolved into several units, so I removed them:
tagfrom Tasks' Roadmap Tag;roadmapfrom Devbook's Roadmap Contribution.This also clears two "both claim the term" warnings.
No
syncset yet. The owner will set directions when sync starts, so every unit stays onreport.Knowledge.
ai/05-unattended-runs.mdadds the pull and push sweeps besidedevbook-verifyas acandidate, not selected.tech/and ADR 0016 record 1.16.0 and contract 25.Checks
units.mjs --groups: 167 groups of 167 units; 0 set aside; 0 orphans (was 14)build.mjs --check: 0 errors, 2 fewer warningstools/devbook/check-metadata.mjs: 0 blockingBacklog.Infrastructure.Devbook.UnitTests, includingDevbookBuilderParityTests: 98/98No chapter status changed. Personal Validation: approved by the owner choosing Create PR.
🤖 Generated with Claude Code