Aionis v0.3.12 Replay Upgrade Hardening Candidate

Aionis v0.3.12 Replay Upgrade Hardening Candidate

These notes describe the Runtime-only v0.3.12 candidate for the self-hosted
Local Runtime Public Beta. Candidate status alone does not create or validate
release artifacts; publication is complete only after the immutable tag,
protected-provider evidence, exact-digest image gates, and verified GitHub
prerelease all succeed.

The last published candidate remains v0.3.11. Its immutable source commit and
linux/amd64 digest are recorded in
v0.3.11-publication-evidence.json.
That receipt remains unchanged and does not claim that v0.3.11 can upgrade a
legacy replay database created with mode 0644.

What Changes

• runtime-data-ops upgrade accepts --replay-db PATH for deployments that
  persist the replay mirror.
• Before schema mutation, the offline operation binds write/replay SQLite main
  files and WAL/SHM/journal sidecars by filesystem identity and rejects
  symlinks, hard links, replacement, namespace overlap, or unexpected sidecar
  drift across the two complete artifact sets.
• Before either database opens, Runtime startup rejects overlap between the
  complete reserved write/replay path sets after nearest-existing-ancestor
  realpath canonicalization plus NFC/case-insensitive comparison, and rejects
  any existing main or sidecar artifact whose hard-link count is not exactly
  one. Names distinguished only by case or Unicode normalization are
  intentionally unsupported across platforms.
• Replay validation requires strict SQLite integrity and exactly four schema
  objects: the canonical v1 table, both canonical explicit indexes, and the
  sole sqlite_autoindex_lite_replay_nodes_1 primary-key autoindex with null
  SQL. Every other object fails closed.
• Only validated, identity-bound artifacts are hardened to owner-only modes.
• An uninitialized write database is rejected rather than silently initialized
  by an upgrade command pointed at the wrong file.

The route surface, schema-v6 target, learning posture, external packages, and
installer default do not change. Global admission-candidate serving remains
off.

Candidate Coordinates

Artifact	Version	Source ref
GitHub Runtime source	v0.3.12 candidate tag	Not created; candidate metadata only.
Docker image	ghcr.io/ostinatocc/aionis:v0.3.12 candidate coordinate	No official digest exists before the tag workflow succeeds.
Default installer Runtime ref	v0.3.6	Frozen installer default.
aionis	0.3.8	v0.3.8
@aionis/create	0.3.8	v0.3.8
@aionis/sdk	0.3.19	v0.3.19
@aionis/manifest	0.1.1	v0.1.1
@aionis/mcp	0.3.7	v0.3.7
@aionis/aifs	0.3.4	v0.3.4
@aionis/claude-code	0.3.5	v0.3.5
@aionis/substrate	0.1.11	v0.1.11

No npm package is republished by this patch. In particular, do not republish
@aionis/create@0.3.8; it continues to select Runtime v0.3.6.

Evidence Required Before Candidate Publication

The bounded local checkpoint for commit 2c933f1d3f716e00bc0c5e5bdf4760043073839e
is recorded in
v0.3.12-development-consumer-lifecycle-evidence.json.
It records successful ordinary and v0.3.6 cross-version recovery gates, but
explicitly carries no publication or stable-promotion authority because the
Darwin/arm64 Docker Desktop run disabled Docker healthchecks under emulation.

The candidate implementation and local tests are checkpoints, not publication
evidence. Publication requires all of the following against clean, exact commits:

1. Typecheck, full static and Runtime suites, complexity ratchet, release-doc
   contracts, and installer/package compatibility.
2. A local linux/amd64 image built from the clean v0.3.12 implementation commit.
3. Real v0.3.6 data upgraded with both write and replay databases, followed by
   restart, replacement-container recovery, and rollback from an untouched
   pre-upgrade volume snapshot.
4. The checked-in real Docker/SQLite cross-version gate passing against the
   exact candidate digest before Docker tag promotion.
5. A later exact-origin/main candidate commit with its own protected
   DashScope embedding run and full GitHub CI.
6. Exact-digest fresh-install, lifecycle, recovery, and cross-version gates
   before a verified non-latest GitHub prerelease is created.

The supported deployment remains one self-hosted Runtime process with SQLite
authority on linux/amd64. This train does not claim GA, multi-instance HA,
managed multi-tenancy, hostile-same-UID filesystem isolation, or Windows ACL
equivalence.