SPEC v0.3: orchestrator resolutions of the plans' open points

Records D-004 and D-015 to D-025: shells and ownership, server seams
(router middleware, rate_limit layer, tasks::start, AuditWriter and PushQueue
traits, next_occurrence_date in kvitt-domain, M3 owns recurring generation,
M4 lands after M3), OpenAPI parsed-value equality, feature convention and
strings, empty fake scenario and resolveRange exception, shared ledger rows and
editor fields in :core:design, no bundled font, pruning at 04:00, development
infrastructure as M2c-dev built it, M2c-pi allowances, release keystore,
production import procedure. Plans and prompts close their open points;
HANDOFF rewritten to the real state; CLAUDE.md: implementation agents never
edit SPEC.md or docs/decisions.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

prompts/M7e.md

@@ -4,9 +4,9 @@ You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/
 
 Read PLAN-M7e.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
 
-Numbers you may use (from the orchestrator):
+Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
 - Next free decision id: {{NEXT_DECISION}}
-- Spec version for any spec change: {{SPEC_VERSION}}
+- Spec version a proposed spec change would get: {{SPEC_VERSION}}
 - Schema version for any schema change: {{SCHEMA_VERSION}}
 If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.