Skip to content

feat(counts): sd-3wp.2 — epic titles and the current epic's roadmap slot - #115

Merged
dkoosis merged 2 commits into
mainfrom
sd-3wp.2-counts
Aug 20, 2026
Merged

feat(counts): sd-3wp.2 — epic titles and the current epic's roadmap slot#115
dkoosis merged 2 commits into
mainfrom
sd-3wp.2-counts

Conversation

@dkoosis

@dkoosis dkoosis commented Aug 20, 2026

Copy link
Copy Markdown
Owner

The rewritten wrap session banner (sdlc sd-3wp.2) names epics and states "epic 2 of 7". counts.json could supply neither: epics[] carried ids without titles, and its index counts only live epics, so it cannot express a position among all of them.

What changed

Two additive fields, derived from reads computeRow already makes — no new bd forks:

  • EpicRow.title — bd's own epic title, via the EpicStatus read the buckets already derive from. bd.EpicRef gains Title to carry it.
  • Row.roadmap {k, n} — the current epic's 1-based slot among all roadmap ids, closed included, so k/n reads as progress through the project. Explicit null when there is no roadmap or no live epic — the same two conditions that null epics.

Compatibility

Additive only, same rule as #112: every consumer decodes by name into its own struct (bdcounts.Reader, the statusline's jq), so a key it never mentions cannot affect it.

Verification

make check green (vet + golangci-lint 0 issues + full test suite + conform).

New coverage: TestRoadmapPos (k/n against all ids incl. closed; the three nil cases), TestEpicTitlesCoversWholeSet, title assertions in TestEpicBuckets and TestComputeRowAssemblesEpicsNextAndClaimed, roadmap added to both JSON-shape tests.

Live against sdlc:

"roadmap": { "k": 2, "n": 7 },
"epics": [ { "id": "sd-ev2", "title": "The SDLC works as one system: ...", "bh": 0, "bo": 1, ... } ]

wrap's rewritten session banner names epics and states "epic 2 of 7". counts.json
could supply neither: epics[] carried ids without titles, and its index counts
only live epics, so it cannot express a position among all of them.

Two additive fields, from reads computeRow already makes:
- EpicRow.title — bd's own epic title, via the EpicStatus read the buckets
  derive from (bd.EpicRef gains Title to carry it).
- Row.roadmap {k, n} — the current epic's 1-based slot among ALL roadmap ids,
  closed included, so k/n reads as progress through the project. Explicit null
  when there is no roadmap or no live epic — the same two conditions that null
  epics.

Additive only, same rule as #112: every consumer decodes by name into its own
struct, so a key it never mentions cannot affect it.

Verified live against sdlc: roadmap {k:2,n:7}, seven epic titles rendered.
@coderabbitai

coderabbitai Bot commented Aug 20, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8a1e7333-d279-4af0-8994-84c9b53aec1c


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

The four lane buckets partition only LIVE children — bd list omits closed — so
epics[] could not answer "how far through this epic are we", which the banner's
✓ tally and progress bar both need.

EpicRow gains bcl (closed children) and n (total children), taken verbatim from
the EpicStatus read epicBuckets already walks. They are bd's own roll-up, not a
re-derivation: a nested epic child counts there and not in the buckets, and the
comment says so.

epicTitles becomes epicMeta — the lookup now carries the whole EpicStatus row
rather than just the title.

Live against sdlc: sd-ev2 bcl 12 / n 13, matching bd epic status.
@dkoosis
dkoosis merged commit 70c9d75 into main Aug 20, 2026
2 checks passed
@dkoosis
dkoosis deleted the sd-3wp.2-counts branch August 20, 2026 05:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant