chore(understanding-gate): release 0.4.10

[LanNguyenSi]

Cuts the release that has been sitting finished on master since #154.

malformedSections was implemented, tested and merged weeks ago, but never
released. npm still serves 0.4.9, harness pins ^0.4.9, and the field is
absent from the installed package, so a report whose section is present but
written as prose is still reported as "Missing required sections" rather than
"present but not a markdown list". Three lost approve roundtrips or audit
gaps are documented against exactly this, the most recent during this batch.

Unblocks task 823837fd.

Why patch, not minor

This is the one real judgement in the PR, and it goes against the brief I gave
the implementer, which expected 0.5.0. The implementer pushed back with
evidence and was right:

version	satisfies harness's ^0.4.9?
0.4.10	yes
0.5.0	no

Shipping 0.5.0 would have required a manual re-pin in harness before anyone
saw the fix, defeating the reason for cutting the release. It also matches this
package's own precedent: 0.4.6 and 0.4.9 both shipped additive-optional fields
as patches with that rationale written into the changelog, and the underlying
commit is typed fix(understanding-gate), not feat.

Changelog provenance

This repo has a recorded changelog-fabrication incident, so the entry was
derived from history rather than from my brief:

• Release point confirmed as tag understanding-gate-v0.4.9 = 208f7007.
• Exactly two commits touch master since then. Only 6647c506 (fix(understanding-gate): diagnose present-but-prose list sections instead of reporting them missing #154) touches
  this package; the other is a lockfile-only CVE fix at the repo root with zero
  files under packages/understanding-gate/.
• Each bullet traces to a commit that was read, and the feature was confirmed
  present at HEAD (parser, both adapter log writers, parametrised tests) before
  any release note was written.

Verification

• Package build clean; suite 38 files / 534 tests green, run before and after
  the edit with identical counts, confirming a version-and-changelog-only
  change caused no regression.
• Preflight after the edit: typecheck pass, test pass, npm-audit unchanged at
  0 critical / 20 high (pre-existing, dev-side, upstream-blocked).

After merge

Publishing is tag-driven. Nothing reaches npm until
understanding-gate-v0.4.10 is pushed, which triggers
publish-understanding-gate.yml. Once published, harness picks it up inside
its existing ^0.4.9 range with no re-pin, and the remaining surfacing work in
823837fd (CLI summary and hook reason strings) becomes implementable.

Review

Reviewed by the orchestrator rather than a reviewer subagent, per the AGENTS.md
"Scaling delegation" clause: one version field and one changelog entry, no
source, test or workflow change. Recorded in the evidence ledger, including
that no subagent ran.