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/2026-09-21-net-kingdom-emission-cadence-declaration.md

@@ -91,5 +91,22 @@ None.
   independent of this repository. It also records an incompatibility, which is
   the third element of the stable gate (standard §10). It is not a second
   declaration and not an observer result. The standard stays at candidate.
+- **Observer evaluation received, and it does not satisfy the gate.**
+  audit-core replied 2026-09-22 (State Hub message `266abb18-0a85-4d85-9ff2-0745949c9587`,
+  thread `368e54bf-6401-4184-a1d2-04f133945d40`), against its own AUDIT-WP-0009
+  implementation (audit-core `01468ff`, read at contract digest
+  `b08b4d95fc4b0bd3`): structurally, both entries in this declaration
+  validate. Operationally, audit-core registers no `local-identity` sender and
+  holds none of its events, so nothing sits behind `compare_observed` — by
+  audit-core's own account this is "not an observer result on the stream, and
+  it should not satisfy your section 10 stable gate." A second incompatibility
+  surfaced: the declaration's heartbeat block names an `event_class`, but
+  audit-core evaluates one heartbeat class (`audit-core.heartbeat`, carrying
+  the vouched-for class in `data.class`) driven by a separately registered
+  `heartbeat_classes` list — the two can drift apart, and neither side has
+  reconciled that yet. audit-core states a real observer result needs a
+  source with an expected-rate or reconciliation declaration registered there
+  and sending traffic — which is not this declaration. INFO-WP-0029-T05
+  (observer result) stays open on the strength of this reply alone.
 - The NetKingdom security profile's rare-heartbeat MUST failure belongs to
   NetKingdom's profile. It is not a defect of the generic contract.