plan_issue/tracking/
mod.rs

1//! vNext tracking controller boundary.
2//!
3//! Design references:
4//!
5//! - `docs/source/plan-issue-redesign/plan-tracking-issue-run-state-controller-v1.md`
6//!   (run-state schema, event journal, FSM, reconciliation, command surface)
7//! - `docs/source/plan-issue-redesign/plan-tracking-issue-workflow-v1.md`
8//!   (workflow states and timing rules)
9//!
10//! Module map:
11//!
12//! - [`run_state`] — typed `plan-issue.execution-run.v1` schema and on-disk
13//!   helpers (`run-state.json`).
14//! - [`events`] — append-only `plan-issue.execution-event.v1` journal
15//!   (`events.jsonl`).
16//! - [`fsm`] — deterministic state machine over the lifecycle evidence.
17//! - [`reconcile`] — combines provider evidence, plan bundle, run state, and
18//!   events into a reconciled view that the FSM evaluates.
19//! - [`checkpoint`] — dry-run and live checkpoint behavior built on top of
20//!   the lifecycle renderer + visible-lint surfaces.
21//! - [`close_ready`] — non-mutating close-readiness probe that mirrors the
22//!   `record close` strict gate.
23//!
24//! The boundary is intentionally narrow: low-level provider IO and
25//! Markdown rendering are reused from [`crate::lifecycle_record`] and
26//! [`crate::lifecycle_vnext`]; this module owns local execution state,
27//! reconciliation, and the high-level commands.
28
29pub mod checkpoint;
30pub mod close_ready;
31pub mod events;
32pub mod fsm;
33pub mod reconcile;
34pub mod run_state;
plan_issue/tracking/mod.rs

plan_issue/tracking/
mod.rs
