docs(milestone): complete v1.19 — Nova 2nd-Release Sync

NFR-only chore milestone complete. P1 (nova-sync-script, v1.18.0) + P2
(final-review-ship, v1.18.1 = milestone release). REQ-229 satisfied.
Review clean, audit clean, 5 decisions locked (D-143..D-147).

---ci---
project: acdl
phase: 2
milestone: v1.19
status: complete
phase_role: final
requirements:
  covered: [REQ-229]
  partial: []
---/ci---

.ciagent/PROJECT.md

@@ -1334,7 +1334,7 @@ constraints or user-directed scope). New v1.18 decisions:
 | D-140 | MCP server extensibility = plugin-registry (`plugins/<name>.py` implementing `register(mcp)`). | Future capabilities (new scanners, policy evaluators, cost tools) drop in as new plugin files — no `server.py` edits. `server.py` scans `plugins/` and calls `register` on each. This is the extensibility insurance: plugins are decoupled from the server entrypoint. | P5 implements the plugin-registry; initial plugins are `principles.py` + `validation.py`. |
 | D-141 | PPTX storage = commit binary directly to `docs/presentations/` (no LFS). | Decks are small (~1-5 MiB); git handles binary blobs. LFS requires server-side support (unverified for git.cloudinit.dev) + client config. Committing directly is simplest and works without any repo/server config. Binary diffs are not delta-friendly, but deck changes are infrequent. | P1/P2/P6 commit .pptx directly. |
 | D-142 | Deck render trigger = any phase modifying `docs/presentations/*-marp.md` or `docs/presentations/assets/` must re-render HTML + PPTX, commit PPTX, and attach to the Gitea release. | PPTX was previously manual + release-only (not committed). v1.18 makes it a first-class artifact: committed (history) + attached (download), both always, not optional. Automated via `scripts/render_deck.sh` + `scripts/attach_release_asset.py`. | P1/P2/P6 run the render+commit+attach pipeline. |
-## Objective for Milestone v1.19 (active — Nova 2nd-Release Sync)
+## Objective for Milestone v1.19 (complete — Nova 2nd-Release Sync)
 
 > **NFR-only chore milestone.** Ships a patch on the v1.18.x line (tag
 > `v1.18.0`). Single execution phase. Establishes the manual-only "2nd