Close out INFO-WP-0030; record second Emission Cadence declaration

INFO-WP-0030: register practice-pattern/explicit-unsafe-diagnostic-mode
(adapted from coordination-engine's OrwellLoggingDiagnostics candidate,
INFO-DEC-2026-003) at canon 0.13.0, close the assimilation, and notify
coordination-engine for COORDINATION-WP-0004-T02. Workplan finished.

INFO-WP-0029: record activity-core's source-owned declaration (T03/T04
done) with its expected-rate/calendar-schedule incompatibility as
demand/EmissionExpectedRateCalendar.md, and record audit-core's
structural-only observer evaluation of net-kingdom's declaration as a
steward note. No party has yet produced a real observer result against
traffic, so T05 and the workplan stay blocked on external action.

Updated artifact-count and practice-pattern-count assertions in
tests/test_cli.py and tests/test_service.py for the new artifact.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: sonnet
Assistant-Process: 317218@bnt-lap001
Assistant-Session: a8d6c0ab-c70f-4610-a288-576f44d747d4

feedback/index.yaml

@@ -98,3 +98,25 @@ reports:
       - demand/EmissionActivityScope.md
     related_workplan:
       - INFO-WP-0029
+  - id: feedback/2026-09-22-activity-core-emission-cadence-declaration
+    path: feedback/2026-09-22-activity-core-emission-cadence-declaration.md
+    date: "2026-09-22"
+    consumer: activity-core
+    consumer_domain: infotech
+    status: reviewed
+    canon_version: "0.13.0"
+    artifacts:
+      - standard/emission-cadence
+    hits:
+      - expected-rate (fixed-time schedule)
+      - heartbeat-or-reconciliation (reconciliation)
+      - extensions
+    friction:
+      - emission-review not runnable by adopter (infospace-bench not installable)
+    gaps:
+      - expected-rate cannot express a weekday-only (calendar-shaped) schedule
+    drop_candidates: []
+    related_demand:
+      - demand/EmissionExpectedRateCalendar.md
+    related_workplan:
+      - INFO-WP-0029