You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
L12-06 — Project client-visible status from receipts #91
Expose job/workflow progress, output, limitations, and required action through L07 projections.
Parent and boundary
Parent: #13. Owner: proposed Automation module. This issue owns one bounded slice of Automation Runtime; consume accepted upstream contracts and keep PDF/verdict/publication authority with Core.
Acceptance
Client-facing status can be reconstructed after restart from canonical receipts.
Failure case: No separate status database may claim success before Core validation.
Required proof
Editor/CLI status parity and reopen test. Record the exact source SHA, test command or hosted run, fixture/artifact identity, and any skipped or unavailable lane. Run the repository's mapped proof and check-change gate for a PR.
Handoff
Record changed files, observed result, remaining risk, and a 1–3 sentence anti-slop review. Completion means acceptance evidence, not merely a merged implementation.
Activity