verify(milestone-run): 0.0.5 runs on the orchestrator skill + milestone-run profile as its first real execution

[rickylabs]

Summary

Epic #1120's final acceptance criterion is observational — "the 0.0.5 milestone runs on this
system as its first real execution" (decision D2) — and no pull request can satisfy it: it is an
observation of a future milestone run. Per the #1090 pattern, it is relocated here rather than
ticked, deleted, or weakened. PR #1161 lands the three artifacts (the
agent-milestone-orchestrator skill, .llm/harness/workflow/milestone-run.md,
.llm/harness/workflow/canary-cadence.md); this issue owns the proof that they work.

The bar comes from the profile's own acceptance stance (mirroring seed-run.md): the artifacts'
acceptance test is the next real milestone run, not the PR that lands them. Until this issue
closes, the three artifacts are provisionally promoted.

Related: #1149 owns the narrower live-canary exercise of the label/note surface (0.0.5); this
issue owns the full run shape.

Acceptance

• The 0.0.5 milestone is orchestrated from the agent-milestone-orchestrator skill and
  milestone-run.md without rediscovering the pattern — the orchestrator's run dir cites
  the documents it followed, and any gap it had to improvise around is filed as a finding
• The run produces a cut-trace.md (instrumented during the run, not reconstructed), and
  every merge passed the profile's pre-merge gate with a per-PR record
• Every declared canary point carries the D3 label + note derived by release:canary-label,
  with the tool's explicit check records quoted — including the pass-vs-did-not-run
  distinction
• Each [asserted] rule the run exercised is upgraded to [observed] with a trace citation,
  or falsified and corrected — none silently absorbed