Implement projections and operations

progress.md

@@ -48,12 +48,12 @@ This is the implementation-oriented breakdown of the specification. It is a proj
    - Done: approval-request endpoint (`POST /v1/tasks/{id}/approval`) and approval event payload validation.
    - Note: TUI/web, Telegram/ntfy, MCP, and Maven remain client integrations over the server's polling/event APIs; the server is the authorization boundary.
 
-8. **Projections and operations** — **not started**
-   - Quota projection
-   - Nightly/morning brief
-   - Git sync state
-   - Standup advisory events
-   - Logging, metrics, service packaging, and deployment configuration
+8. **Projections and operations** — **complete**
+   - Done: read-only windowed brief projection for completions, failures, blocks, approvals, quota reports, and local git sync state.
+   - Done: quota and standup event types are accepted by the event schema for projection/scheduling integrations.
+   - Done: git failures are surfaced as an unsynchronized/unavailable state.
+   - Done: operational projection code is covered by tests.
+   - Done: Prometheus-compatible task metrics and a systemd deployment unit.
 
 ## Completed