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

workplans/INFO-WP-0029-emission-cadence-adoption.md

@@ -4,11 +4,11 @@ type: workplan
 title: "Seek independent Emission Cadence adoption evidence"
 domain: infotech
 repo: info-tech-canon
-status: active
+status: blocked
 owner: claude
 topic_slug: canon-optimization
 created: "2026-09-21"
-updated: "2026-09-22"
+updated: "2026-09-27"
 flavor: coordination
 state_hub_workstream_id: "d743e220-9d2d-52d8-8df3-880805269639"
 ---
@@ -70,7 +70,7 @@ incompatibility finding. It is recorded under T04.
 
 ```task
 id: INFO-WP-0029-T03
-status: progress
+status: done
 priority: high
 state_hub_task_id: "bb74cce9-12d8-58e2-ad44-c4aeb7b72f37"
 ```
@@ -84,6 +84,10 @@ Sent 2026-09-21 as State Hub message `f1687805-3153-47c2-9744-05a2b1a6b8c1`.
 Both messages name the brief rather than restating the ask, and both say that a
 recorded incompatibility is a successful outcome.
 
+Answered 2026-09-22 (`161d5aa5`): a declaration was published at activity-core
+`f20db47`, `docs/emission-cadence/activity-core-evidence.yaml`, together with
+an incompatibility finding. It is recorded under T04.
+
 ## Recheck — 2026-09-21
 
 No reply, and none should be expected yet. Both requests are unread. Neither
@@ -103,7 +107,7 @@ of section 10 and defeat its purpose.
 
 ```task
 id: INFO-WP-0029-T04
-status: progress
+status: done
 priority: medium
 state_hub_task_id: "4771ff59-264e-5917-a49d-8989b361b8ed"
 ```
@@ -131,8 +135,28 @@ version from the standard. A test pins that behaviour, and the brief names the
 candidate digest `b08b4d95fc4b0bd3`. The wire schema did not change, so the
 declaration stays valid.
 
-This task stays in progress until activity-core's declaration (T03) arrives or
-the ask is withdrawn.
+### Recorded — 2026-09-27
+
+activity-core's declaration passes `emission-review` (`ok: true`, `errors: []`).
+It is recorded as
+`feedback/2026-09-22-activity-core-emission-cadence-declaration.md`. Its
+incompatibility is that `expected-rate`'s wall-clock window cannot express a
+weekday-only (calendar-shaped) schedule; the consumer used `reconciliation`
+instead for that entry. That finding goes to the standard as
+`demand/EmissionExpectedRateCalendar.md` and was not worked around in the
+declaration.
+
+audit-core also replied (unread until this session) with a structural-only
+observer evaluation of net-kingdom's declaration, explicitly stating it does
+not satisfy the stable gate because audit-core holds no `local-identity`
+traffic to evaluate against. Recorded as a steward note on
+`feedback/2026-09-21-net-kingdom-emission-cadence-declaration.md`. It found a
+second incompatibility (heartbeat `event_class` vs. `heartbeat_classes`
+drift), noted there rather than duplicated here.
+
+Both declarations now arrived and are recorded. This task is done. T05
+(observer result) stays open: no observer has evaluated a source with
+registered traffic against either declaration.
 
 ## Observer result
 
@@ -144,8 +168,17 @@ state_hub_task_id: "0486fcba-3609-50c5-b347-e7ee84f9f548"
 ```
 
 One result from a party other than the declaring source, evaluating a declared
-cadence against observed events. Blocked until at least one declaration exists,
-since there is nothing to evaluate before then.
+cadence against observed events. Two declarations now exist (net-kingdom,
+activity-core), so the earlier blocker is cleared, but no result exists yet:
+audit-core's 2026-09-22 reply evaluated net-kingdom's declaration structurally
+only and said plainly that this does not satisfy the gate, since audit-core
+holds no traffic from that source. A real result needs a source with an
+`expected-rate` or `reconciliation` declaration registered at an observer and
+sending it traffic — neither net-kingdom nor activity-core currently sends
+traffic that any known observer holds (activity-core's periodic emission into
+issue-core is off in production). This is now blocked on an external party
+(a source and an observer both taking action this repository does not
+control), so the workplan status moves to `blocked` pending that.
 
 ## Honest limit on what this can prove