v0.3.45

Orion Code v0.3.45 — Release Notes

Summary

Docs-only delivery-status cycle (PR4 automatable portion of the v0.3.27 review loop).
This release:

• Settles the v0.3.44 open-version debt: the CHANGELOG [0.3.44] entry is corrected
  from candidate → published, with the real npm publish timestamp
  2026-10-28T06:08:32.080Z and the GitHub Release v0.3.44 link backfilled.
• Adds the [0.3.45] candidate entry and a rolling three-version delivery-status audit
  (0.3.42–0.3.44) in docs/plan/evidence/v0.3.45/status-audit.md.
• Six-place version bump to 0.3.45 + tests/coding-task-eval.test.ts packageVersion pin.
• No production code changes (src/, web/, tests/ untouched).

Changed

• CHANGELOG: corrected the 0.3.44 delivery status from candidate to published
  (tag v0.3.44, npm registry latest, npm publish timestamp and GitHub Release link
  backfilled).
• docs: added docs/plan/evidence/v0.3.45/status-audit.md — a three-version
  (0.3.42–0.3.44) delivery-status audit cross-checking git tags, registry versions and
  the latest dist-tag, plus the v0.3.44 release facts (PR #301, merge 95d5aa3,
  tag v0.3.44, registry latest=0.3.44).
• README / README.zh-CN: header summary and install pin updated to 0.3.45.

Quality Gate (CI run 40680689814 — 18/18 success)

Every conclusion below is taken from the actual job conclusion of this round's CI run.

#	Job	Conclusion
1	Release gate (release:check)	success
2	Build the exact release tgz once	success
3	Dependency security audit	success
4	Dependency health report (offline)	success
5	TypeScript type-check	success
6	Exact tgz on Node 22.12.0 floor	success
7	Exact tgz on Node 24.0.0 floor	success
8	Exact tgz on Node 26.0.0 floor	success
9	Node 22 verification	success
10	Node 24 verification	success
11	Node 26 verification	success
12	Web E2E critical journey on Node 22.12.0 floor	success
13	Web E2E critical journey on Node 24.0.0 floor	success
14	Web E2E critical journey on Node 26.0.0 floor	success
15	Web E2E full suite three consecutive runs	success
16	Lean Harness benchmark and confluence	success
17	Aggregate exact-artifact Web E2E receipt	success
18	Aggregate fail-closed v0.3.x release receipt	success

• Dependency security audit: 0 vulnerabilities (green).
• Web E2E full suite: three consecutive runs (25m31s), all passed — no flake, no rerun.

Tarball Integrity (hard safety net — must match)

• Local build sha256: a8079e2cbd0a266d3c0a6577df2f70fe62592ce8dc74488b9d12e9588abab5cc
• CI-built release-package tgz sha256: identical (byte-for-byte match) ✅
• CI web-e2e-receipt.json tarballSha256: identical (decision: GO) ✅
• npm registry shasum (SHA-1): cd499a01c076a2cf79b927051cd07efded4d76e1

Install

npm install -g @orion-agents/orion-code@0.3.45

Not run (honest)

The human-labeled paid quality benchmark and the real Host + Chrome full-chain review E2E
remain not_run (no model credentials in the automation environment). Not fabricated.

Note on versioning (flagged for maintainer)

This is a docs-only cycle with no product-code delta. Per the automation's main instruction
("advance one version per round → v0.3.99") it still consumes a version number and goes
through the full release pipeline (bump / tag / publish / Release), consistent with
v0.3.38–v0.3.44. Quality clause C ("docs-only cycles should not consume a version number")
conflicts with the main instruction; this tension is flagged here for the maintainer's
decision.