User facing development progress model from Breadboard #13

Merged
Breadway merged 3 commits from feature/bug-22-progress into main 2026-10-12 09:53:03 +08:00
Owner

Part of BUG-EP1, implements breadboard issue BUG-22 (user facing development progress model). Stacked on the BUG-21 branch.

The hourly board sync now caches each promoted cluster's workflow status, and the public status endpoint exposes it as a coarse progress stage (accepted, in_development, in_review, completed, declined, deferred). Cluster verdicts take precedence, unlinked reports carry no progress field, and no board internals leak. Release targeting stays out of this field for BUG-23.

Verified: cargo test (all suites green, 3 new tests), cargo clippy with -D warnings clean, cargo fmt clean.

Closes BUG-22

Part of BUG-EP1, implements breadboard issue BUG-22 (user facing development progress model). Stacked on the BUG-21 branch. The hourly board sync now caches each promoted cluster's workflow status, and the public status endpoint exposes it as a coarse progress stage (accepted, in_development, in_review, completed, declined, deferred). Cluster verdicts take precedence, unlinked reports carry no progress field, and no board internals leak. Release targeting stays out of this field for BUG-23. Verified: cargo test (all suites green, 3 new tests), cargo clippy with -D warnings clean, cargo fmt clean. Closes BUG-22
feat: user facing development progress from the linked issue
All checks were successful
check / check (push) Successful in 1m2s
30608b1dad
Cache each promoted cluster's breadboard workflow status on the
hourly sync and expose it as a coarse progress stage on the public
status endpoint: accepted, in_development, in_review, completed,
declined or deferred. Cluster verdicts win (dismissed reads declined,
deferred reads deferred, fixed reads completed) and unlinked reports
carry no progress field. The admin cluster page shows the cached
board status next to the issue key.
fix: distinct fixed and targeting_release progress stages, follow board reopens
All checks were successful
check / check (push) Successful in 1m4s
33bcfe85c7
Address review on the progress model slice:
- progress mapping no longer collapses a fixed cluster to completed and no
  longer uses in_review (not in the stated lifecycle). review maps to fixed,
  a fixed cluster without a version maps to fixed, a fixed cluster with a
  recorded version maps to targeting_release, and a done issue maps to
  completed; dismissed and deferred verdicts still take precedence
- brings in the BUG-21 rework by merge: fixed and dismissed groups stay
  tracked and a board reopen re-derives the promoted state
- tests updated for the new stages plus a targeting_release case
# Conflicts:
#	src/db.rs
docs: list the real progress stages in the README
All checks were successful
check / check (push) Successful in 1m1s
c8b5c7377e
The status row advertised in_review and omitted fixed and targeting_release;
list the stages the server actually returns.
# Conflicts:
#	src/db.rs
Breadway force-pushed feature/bug-22-progress from 6c7223ccb9
All checks were successful
check / check (push) Successful in 1m14s
to 59711c7940
All checks were successful
check / check (push) Successful in 1m8s
2026-10-12 09:21:57 +08:00
Compare
Breadway changed target branch from feature/bug-21-promote-manual to main 2026-10-12 09:53:02 +08:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Breadway/breadbug-server!13
No description provided.