Record net-kingdom's Emission Cadence declaration and fix the stale digest (INFO-WP-0029)

net-kingdom published the first source-owned declaration (116643f). It passes
emission-review. Record it as feedback, and file its session-scoped-silence
incompatibility as demand/EmissionActivityScope.md. T02 is done, and T04 is in
progress until activity-core answers.

The adoption brief sent owners the 0.1.0 draft digest, because the candidate
promotion changed the standard's text after the digest was taken. The export
manifest also hard-coded status "draft". The manifest now derives status and
version from the standard, a test pins that, and the brief names the candidate
digest b08b4d95fc4b0bd3. The wire schema is unchanged.

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 121421@bnt-lap001
Assistant-Session: 36f8657c-ebfa-4a2e-9ba0-bff06738f233

docs/emission-cadence-adoption.md

@@ -27,7 +27,9 @@ and a declaration is never evidence that the emission actually happens.
      observer's.
 2. **The contract digest you implemented against**, so the declaration is pinned
    to a fixed reading of the contract rather than to whatever the canon says
-   later. Current digest: `972c0b6701d1693f`
+   later. Current digest: `b08b4d95fc4b0bd3`
+   (candidate, document 0.2.0; `972c0b6701d1693f` was the 0.1.0 draft text and
+   the same wire schema)
    (`info_tech_canon export-emission-contract <path.tar>` regenerates it).
 3. **Nothing else.** No deployment, no runtime proof, no conformance claim. A
    declaration is a statement of intended cadence.