christian/commitea
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Lifecycle inference from the issue timeline #5

New Issue
Closed
opened 2026-07-08 15:15:08 +00:00 by christian · 1 comment
christian commented 2026-07-08 15:15:08 +00:00
Owner
Copy Link

Pure core fn mapping timeline events to the five columns (pm-state.md), writing the lifecycle table; computes Steeping->Done working-time segments (reopens append segments). Feeds both calibration (P2-5) and scheduler actuals (P2-3).

Acceptance: table-driven tests per transition + a reopen + a stalled issue.

Open scope: verify what the gitea timeline API surfaces for 'first branch/commit ref' and 'PR opened/merged' vs needing separate commit/branch/PR queries.

Pure core fn mapping timeline events to the five columns (pm-state.md), writing the `lifecycle` table; computes Steeping->Done working-time segments (reopens append segments). Feeds both calibration (P2-5) and scheduler actuals (P2-3). **Acceptance:** table-driven tests per transition + a reopen + a stalled issue. **Open scope:** verify what the gitea timeline API surfaces for 'first branch/commit ref' and 'PR opened/merged' vs needing separate commit/branch/PR queries.
christian added this to the P1 — Sync + data model milestone 2026-07-08 15:15:08 +00:00
christian added the
est
3d
p
2
 labels 2026-07-08 15:15:08 +00:00
christian added a new dependency 2026-07-08 15:15:42 +00:00
#4 Full reconcile-on-launch of the work repo
christian added a new dependency 2026-07-08 15:15:42 +00:00
#9 Deterministic scheduler (topo order -> dated plan)
christian added a new dependency 2026-07-08 15:15:43 +00:00
#11 Calibration fit + cold-start switchover
christian commented 2026-07-09 05:21:03 +00:00
Author
Owner
Copy Link

Shipped — inferLifecycle over the issue timeline; five-column board.

Shipped — inferLifecycle over the issue timeline; five-column board.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
deadline
hard
CommiTea: milestone has a hard deadline
est
1d
CommiTea estimate: 1 ideal-day(s)
est
2d
CommiTea estimate: 2 ideal-day(s)
est
3d
CommiTea estimate: 3 ideal-day(s)
est
5d
CommiTea estimate: 5 ideal-day(s)
est
8d
CommiTea estimate: 8 ideal-day(s)
p
1
CommiTea priority 1 (1 = most urgent)
p
2
CommiTea priority 2 (1 = most urgent)
p
3
CommiTea priority 3 (1 = most urgent)
p
4
CommiTea priority 4 (1 = most urgent)
No Label
est
3d
p
2
Milestone
No items
No Milestone P1 — Sync + data model
Projects
Clear projects
No project
Assignees
Clear assignees
christian
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#9 Deterministic scheduler (topo order -> dated plan)
christian/commitea
#11 Calibration fit + cold-start switchover
christian/commitea
Depends on
#4 Full reconcile-on-launch of the work repo
christian/commitea
Reference: christian/commitea#5
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?