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.

Aionis v0.3.11 Docker Lifecycle Recovery Candidate

Aionis v0.3.11 Docker Lifecycle Recovery Candidate

These notes describe the Aionis Runtime v0.3.11 patch 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, exact-digest image gates, and verified GitHub prerelease all succeed.

The patch corrects the Docker lifecycle boundary found after v0.3.10. The
v0.3.10 image starts through npm, so Runtime Node is not PID 1 and Docker
SIGTERM does not reliably execute the awaited shutdown drain. v0.3.11 starts
through the existing checked startup script and makes Node PID 1 with its final
exec.

What Changes

• Docker SIGTERM reaches Runtime's signal handler directly.
• Successful Docker stop must produce the Runtime drain log and exit code 0.
• The release workflow must recover memory and exact operation receipts in a
  fresh container after both graceful stop and SIGKILL using the same named
  /data volume.
• The recovery gate also requires operation-conflict rejection, healthy
  projection and learning workers, protected SQLite modes, and offline database
  verification.
• Image promotion occurs only after the basic and recovery smokes pass against
  the exact immutable digest built by the workflow.

Frozen Coordinates

Artifact	Version	Source ref
GitHub Runtime source	v0.3.11	Immutable tag created from verified origin/main.
Docker image	ghcr.io/ostinatocc/aionis:v0.3.11	Promoted linux/amd64 digest after both image gates.
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 external npm package is republished by this Runtime patch. The route surface,
schema v6, learning posture, and installer default remain unchanged.

Compatibility And Limits

• Runtime v0.3.10 remains immutable; its annotated tag and published digest
  must not be moved, deleted, or recreated.
• The supported deployment remains one self-hosted Runtime process with SQLite
  authority. Multi-instance HA and managed multi-tenancy remain out of scope.
• The image remains linux/amd64 only.
• Global admission-candidate serving remains off; this patch does not broaden
  autonomous-learning claims.
• Existing schema-v6 data remains compatible. Back up authority data before an
  upgrade and restore a backup rather than opening adopted data with an older
  Runtime.

Promotion Condition

The local engineering smoke is a checkpoint, not release evidence. Before
tagging, the settled candidate commit must pass full Runtime CI, exact external
package and Manifest checks, and the protected DashScope embedding smoke on
origin/main.

The protected provider gate is
.github/workflows/exact-main-embedding-smoke.yml. It is manual-only, has
read-only repository permissions, binds to the main-only
exact-main-embedding environment, and fails unless its requested SHA equals
both the dispatch commit and current origin/main. It accepts a candidate or
stable release train and gives every dispatch a random-nonce evidence ID; a
stable commit must produce its own same-SHA run. Using the frozen SDK, MCP, and
installer commits, it must prove available-mode SDK and MCP semantic recall
with qwen3.7-text-embedding, persisted model
dashscope:qwen3.7-text-embedding, and 1,536-dimensional queries. The
DASHSCOPE_API_KEY secret must be rotated and stored only in that environment;
it must not be committed, logged, or uploaded as an artifact. The workflow also
requires the immutable Runtime tag to remain absent through the final provider
check.

Only then may an annotated v0.3.11 tag be created from that verified commit.
The tag-triggered workflow first queries GitHub Actions and rejects the release
unless that exact commit has successful protected embedding evidence. It then
builds one image digest, runs the basic smoke and cross-process recovery smoke,
and promotes only that tested digest. A separate digest check completes before
the verified GitHub prerelease is created.

Aionis v0.3.10 Evidence Authority and Runtime Convergence Candidate

Aionis v0.3.10 Evidence Authority and Runtime Convergence Candidate

Aionis Runtime v0.3.10 is a release candidate for the self-hosted,
single-process Public Beta. This document does not claim that the Runtime tag,
Docker image, or GitHub Release exists. The tag is pushed only after the final
candidate commit reaches main and its pre-tag gates pass. That push triggers
the exact-tag workflow. A successful workflow publishes the candidate image;
an independent digest-pinned smoke then approves that image before the GitHub
Release is created.

Candidate Scope

• Feedback attribution and measure persistence are atomic SQLite authority
  operations with exact operation receipts and replay protection.
• Commit mutations include their authoritative state in the canonical digest;
  scoped heads use monotonic revisions and compare-and-swap parent binding.
• Episode-ledger learning control supports the two-arm evidence gate, fixed
  gate-policy authority, durable work, and verified exposure-to-outcome
  attribution. The shipped global admission-candidate policy defaults to off;
  explicit selected-profile operation remains an operator-controlled evidence
  posture.
• External evidence ingestion has lifecycle, provenance, and attestation
  authority instead of being treated as an unverified learning signal.
• Deployment-slot recovery, authority-writer extraction, filesystem hardening,
  awaited shutdown, and Linux CI convergence close the main Runtime integrity
  and operability gaps found during the v0.3.10 convergence sprint. The
  deployment-authority tooling has real SIGKILL replay evidence, but the
  production isolated one-shot worker remains deferred and the current
  authority is not signing-eligible.
• Runtime and Docker CI resolve the frozen SDK and Manifest coordinates, verify
  their exact source/package identities, and exercise the real integrations.

Product and Compatibility Boundary

• The governed /v1 product surface remains 21 routes and 177 environment
  fields. Research protocols, evaluation drivers, and
  deployment-authority tooling are not new public Runtime routes.
• The authoritative SQLite schema is v6. Complete v4 and v5 databases upgrade
  transactionally on startup. Downgrade is unsupported; back up the database
  before upgrading and restore that backup if rollback is required.
• This candidate is a single-process, self-hosted Public Beta. It does not
  claim high availability, a managed control plane, or general autonomous
  learning readiness.
• Formal learning-gate calibration is still pending. Global candidate serving
  and autonomous promotion remain off by default.
• Package coordinates are frozen and are not republished for this Runtime
  candidate. The default installer remains on Runtime v0.3.6.
• The candidate Docker coordinate is linux/amd64 only. It is not valid until
  the tag workflow publishes it, and it must not move the latest tag.

Frozen Coordinates

Artifact	Version or ref
Runtime source	v0.3.10
Docker image (linux/amd64)	ghcr.io/ostinatocc/aionis:v0.3.10
Default installer Runtime	v0.3.6
aionis	0.3.8
@aionis/create	0.3.8
@aionis/sdk	0.3.19
@aionis/manifest	0.1.1
@aionis/mcp	0.3.7
@aionis/aifs	0.3.4
@aionis/claude-code	0.3.5
@aionis/substrate	0.1.11

The package rows identify already-frozen immutable artifacts. No npm publish is
part of the v0.3.10 Runtime candidate promotion.

Pre-Tag Evidence

The last pre-promotion source snapshot, commit 2467af8, passed the complete
GitHub CI run
29684934464.
Its recorded convergence evidence includes:

• 99/99 static checks;
• 339 src source modules and 171,316 src source lines;
• a daemon startup closure of 285 modules and 140,346 lines;
• a 13-module, 11,319-line authority package;
• zero detected production import cycles;
• fresh-install and external no-embedding contract smoke coverage.

This evidence is a floor, not the final release claim. The exact candidate
commit must independently pass local release gates and exact-commit GitHub CI.
An external-package smoke using DashScope qwen3.7-text-embedding must also prove
the available-embedding path, semantic/ANN provenance, feedback attribution,
persisted measure authority, and exact replay before tagging.

Completion Conditions

The candidate becomes a published v0.3.10 release only when all of the
following are true:

1. The final candidate commit is merged to origin/main without changing its
   tree and exact-commit CI is green.
2. The available-embedding external-package smoke passes against that exact
   source and the frozen package coordinates.
3. Annotated tag v0.3.10 points to that main commit and the tag workflow
   publishes the immutable linux/amd64 image.
4. Digest-pinned post-publish smoke passes before the GitHub Release is treated
   as complete.

Historical v0.3.9 evidence is retained verbatim in
v0.3.9.md.

Aionis v0.3.9 Durable Learning Control Candidate

Aionis v0.3.9 Durable Learning Control Candidate

Aionis Runtime v0.3.9 is a Runtime-only Local Runtime Public Beta candidate.
It packages durable unused-exposure learning control and a bounded
confirmatory SQLite writer-contention repair on top of the immutable v0.3.8
guide-feedback attribution boundary.

It does not enable global autonomous learning. Formal feedback creates durable
work; the Runtime worker must still reload authority, recompute evidence, and
pass the controlled mutation boundary before memory posture can change.

Highlights

Durable Queue And Worker

• Feedback facts and the deterministic learning-control job commit together.
• The feedback response exposes queued or already_completed, not a false
  synchronous-application claim.
• Lease-token fencing prevents a stale worker from acknowledging a reclaimed
  job.
• Startup reclaim, bounded retry, retained dead letters, backlog health, and
  graceful shutdown make the work restart-safe.
• The worker reloads positive attribution before mutation, so newer supporting
  evidence can turn an old negative candidate into a no-op.

Atomic Controlled Mutation

The inspect-before-use posture change, audit commit, protected worker receipt,
and completed queue transition share one SQLite transaction. Exhausted enrolled
work can enter dead letter only with its independent safety pause and protected
receipt in the same transaction. Terminalization failure leaves the job
recoverable instead of publishing partial authority.

Confirmatory Writer Contention

Confirmatory provisioning retries only SQLITE_BUSY failures from
BEGIN IMMEDIATE within a fixed six-attempt budget. It does not retry a
transaction body or commit. A concurrent exact replay returns the stored
receipt before either authority entropy source runs.

Compatibility And Boundaries

• v0.3.8 SQLite data upgrades forward on schema v4 without a DDL migration.
  Once v0.3.9 writes queue-provenance events, downgrading that database to
  v0.3.8 is unsupported.
• The governed route matrix remains 21 routes and the environment schema
  remains 177 fields.
• Historical feedback without queue provenance is not retroactively enqueued.
• External package versions do not change.
• Candidate status keeps Docker latest unchanged.
• The supported shape remains one self-hosted Runtime process; multi-instance
  HA and managed-service GA are not claimed.
• Global admission-candidate serving stays off and later promotion work remains
  outside this checkpoint.

Frozen Coordinates

Artifact	Version or ref
Runtime source	v0.3.9
Docker image (linux/amd64)	ghcr.io/ostinatocc/aionis:v0.3.9
Default installer Runtime	v0.3.6
aionis	0.3.8
@aionis/create	0.3.8
@aionis/sdk	0.3.17
@aionis/mcp	0.3.7
@aionis/aifs	0.3.4
@aionis/claude-code	0.3.5
@aionis/substrate	0.1.11

The Runtime repository root is private package metadata and is not an npm
artifact. This release publishes the immutable Runtime source tag and verified
Docker image only. The unchanged external package rows are compatibility
coordinates; v0.3.9 does not republish or re-attest their historical npm
registry provenance.

Release Evidence

The latest pre-tag preparation run recorded:

• 56/56 focused worker, feedback, confirmatory contention, transaction, health,
  and readiness tests passed;
• the structural suite passed 83/83, followed by 1,121 Lite tests with 1,114
  passed, zero failed, and seven platform-optional skips;
• typecheck, SDK ownership sync, the 315-file/151,677-line complexity budget,
  21-route matrix, 177-field environment schema, and zero-cycle import gate
  passed;
• 24/24 release metadata, documentation, workflow, and Docker contract tests
  passed;
• all seven external compatibility source refs resolved to their frozen commits
  in isolated clean worktrees;
• exact published SDK 0.3.17, MCP 0.3.7, and Create 0.3.8 passed the
  no-embedding external-package loop, and aionis@0.3.8 passed the published
  operator CLI smoke;
• the same exact published SDK, MCP, and Create coordinates passed the
  credential-injected DashScope loop against Runtime commit
  132587537fe11c89d54c4e24020eafe90b4095a0:
  dashscope:text-embedding-v4 persisted ready embeddings, SDK and MCP queries
  used 1,536 dimensions with semantic recall provenance, the ordinary memory
  was recovered semantically, and formal feedback returned
  aionis_feedback_result_v1 (external-package-smoke-mrm3w3bl);
• PR #8 CI run 29418203507 passed both the full Runtime checks and the Node 22
  minimum-compatibility job for the same Runtime commit;
• a local linux/amd64 image built successfully and its immutable image-ID
  smoke verified startup drain, worker readiness, a valid zeroed learning-control
  backlog, observe, and durable replay.

Published Artifact

• Runtime tag: v0.3.9 at 5deade1bbdb47d50b2fc77860a8138ac810d6516
• Docker image: ghcr.io/ostinatocc/aionis:v0.3.9
• Immutable digest: sha256:fe988688cbde53b4346a2769f2ce58d4b29698d452bc7b0393fe0c4303be1829
• Platform: linux/amd64 with provenance attestation
• Release workflow: https://github.com/ostinatocc/Aionis/actions/runs/29421050536

The tag-triggered workflow repeated the frozen seven-repository checkout,
real SDK/MCP/Create tarball packaging, full Lite suite, cross-package smoke,
fresh install from the exact tag, single-build digest verification,
learning-control Docker smoke, and immutable promotion. This candidate is a
GitHub Prerelease and does not move Docker or GitHub latest, which remain
on Runtime v0.3.6.

Aionis v0.3.6 Local Runtime Public Beta

Aionis v0.3.6 Local Runtime Public Beta Candidate

Aionis Runtime v0.3.6 is a release-integrity maintenance candidate for the
single-process, self-hosted Local Runtime. It keeps the v0.3.5 public contracts
and SQLite schema while hardening startup compatibility, CI process cleanup,
exact-artifact verification, and Docker provenance.

This candidate is not GA, a managed multi-tenant service, or a multi-instance
HA release. SQLite remains the Lite authority. Local ANN state remains derived
from committed SQLite vectors and is rebuilt after restart.

What Changed

• Lite starts as the direct Node process, and smoke/fresh-install gates use
  bounded termination with a kill fallback.
• Linux Docker release smoke owns a process group and cleans the entire group,
  preventing loader or Runtime children from surviving an Actions job.
• Docker builds under a unique
  build-v0.3.6-<commit>-<run>-<attempt> subject, verifies and smokes its
  digest, then promotes only that digest to the version tag.
• Provenance identifies the unique staging subject rather than latest.
• Release verification checks exact Runtime and package refs, packs real SDK,
  MCP, and Create tarballs, and runs cross-package/fresh-install gates against
  those artifacts.
• The supported source-install floor is Node.js >=22.13.0. Earlier Node 22
  experimental node:sqlite releases are rejected because their empty-row
  behavior is incompatible with Runtime existence checks.
• Product documentation no longer describes a Dashboard/control-panel product
  outside the current repository and release boundary.

Compatibility

• No HTTP API changes.
• No SDK or MCP contract changes.
• No SQLite schema, migration, or durable event-format changes.
• Existing v0.3.5 data remains compatible.
• The container continues to use Node.js 24.

Frozen Coordinates

Artifact	Version	Immutable source ref
Runtime source	v0.3.6	v0.3.6
Docker image (linux/amd64)	ghcr.io/ostinatocc/aionis:v0.3.6	Runtime v0.3.6
aionis	0.3.8	v0.3.8
@aionis/create	0.3.8	v0.3.8
@aionis/sdk	0.3.15	v0.3.15
@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

Each package ref is paired with an exact source commit in
release-train.json. The release remains candidate, so Docker latest is
not moved. linux/arm64 remains outside the publication matrix until that
exact platform has its own runtime smoke gate.

Release Evidence

• Runtime PR CI passes the Node 22.13 minimum-version public smoke and the full
  Node 24 Runtime suite.
• Job teardown contains no Terminate orphan process record after Lite smoke.
• Local OCI provenance verification resolves the subject to the unique build
  staging tag rather than latest.
• The release workflow verifies the built digest before version-tag promotion
  and rejects an existing version tag with a conflicting digest.

Publication is complete only after the Runtime tag resolves, the Docker
workflow succeeds, provenance and digest checks pass, the GitHub prerelease is
created, and the exact @aionis/create@0.3.8 public fresh-install succeeds.

Aionis v0.3.5 Local Runtime Public Beta

Aionis v0.3.5 Local Runtime Public Beta Candidate

Aionis Runtime v0.3.5 is the release candidate for a single-process,
self-hosted Local Runtime. It combines the aggressive AgentContext compaction
repair with continuity, atomic-write, evidence-gate, and projection-recovery
hardening completed after v0.3.4.

This candidate is not GA, a managed multi-tenant service, or a multi-instance
HA release. SQLite is the Lite authority. The local in-memory ANN is rebuilt
from committed SQLite vectors after restart; several Runtime processes require
a shared persistent ANN or cross-instance reconciliation.

Public Contract Changes

• POST /v1/observe accepts an optional durable operation_id and returns
  aionis_observe_result_v1. The semantic memory write, execution state/tree,
  handoff, claims, durable receipt, and embedding/ANN projection intents share
  the SQLite transaction.
• Direct POST /v1/handoff/store accepts the same retry model and returns
  aionis_handoff_store_result_v1. An exact retry returns the stored receipt;
  reusing the ID for different effective content returns HTTP 409.
• Observe responses expose post_commit_projections: semantic commit is
  complete, while embedding and ANN values are scheduled or not_requested.
  Scheduled means durable work exists, not that the external side effect has
  already completed.
• Projection jobs expose pending, running, retry, dead_letter, and
  succeeded backlog states under /health, with separate worker health.
• POST /v1/measure returns evidence_assessment. Manual observations are
  unverified and cannot become export-ready. Client sufficient_evidence and
  evidence_ids claims are ignored by the gate and reported under
  client_claims_ignored.
• Runtime-verified learning/skill export requires paired durable guide
  receipts, task/run binding, ordered effect observations, a trusted Runtime
  verifier receipt, linked positive tool feedback, and complete passing kernel
  metrics.
• SDK 0.3.15 carries the typed observe result, measure evidence assessment,
  execution operation_id, and projection scheduling contracts.
• npm run -s runtime:data -- ... provides v0.3.4 schema preflight/upgrade,
  verified backup/restore, and projection repair. Verify and backup reject
  corrupt execution history and invalid projection payloads.
• Current schema startup validates required columns, primary/unique
  constraints, and critical receipt/projection indexes before business DDL.
• Docker builds one digest-pinned linux/amd64 artifact, smokes that exact
  digest, and only then promotes it to the candidate version tag.

Context And Continuity Changes

• Aggressive standard and full-power guide requests use the canonical bounded
  contract renderer while preserving the active target and safety boundaries.
• A stale execution snapshot cannot silently replace newer state or tree
  history. Revision and continuity history remain consistent.
• Observe is one atomic event rather than a memory commit followed by
  best-effort execution/handoff/claim writes.
• Embedding generation and ANN reconciliation use durable leased jobs with
  generation/CAS completion. A process crash immediately after commit leaves
  recoverable work, and stale workers cannot overwrite newer node state.
• ANN reconciliation reads SQLite truth. A fresh local ANN is rebuilt from
  committed ready vectors on startup.

Candidate Coordinates

Artifact	Version	Planned immutable source ref
Runtime source	v0.3.5	v0.3.5
Docker image (linux/amd64)	ghcr.io/ostinatocc/aionis:v0.3.5	Runtime v0.3.5
aionis	0.3.8	v0.3.8
@aionis/create	0.3.7	v0.3.7
@aionis/sdk	0.3.15	v0.3.15
@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

Every tag is paired with an exact source commit in release-train.json. The
final release must resolve every ref to that frozen commit before package
publication. Manifest is outside this train until it has a verifiable source
repository and immutable ref.

linux/arm64 is outside this candidate until the exact platform image passes
an independent runtime smoke gate.

Verification

• Real temporary SQLite and HTTP tests cover stale-snapshot rejection, atomic
  observe rollback, exact operation receipt replay, request-ID conflict, and
  corrupt receipt failure.
• Real child-process tests exit immediately after semantic commit, then verify
  restart recovery of embedding generation and ANN reconciliation.
• Projection tests cover expired leases, side-effect-before-ack failure,
  generation changes, stale ANN reconciliation, poison payload dead-letter,
  provider mismatch, and transactional enqueue failure.
• Evidence-gate tests prove missing/manual metrics and caller-supplied evidence
  claims cannot create export-ready learning or skill candidates.
• Destructive SQLite tests cover projection rollback, broken event chains,
  revision gaps, orphan events, missing current columns/constraints/indexes,
  and backup refusal on corrupt authority state.
• The most recent pre-freeze full Runtime run recorded 919 tests: 915 passed,
  zero failed, and four optional native Zvec tests skipped. Final candidate CI,
  cross-package checkout, Docker smoke, and exact-version smoke remain release
  gates and must be rerun against frozen refs.

Release Safety

• Runtime v0.3.4 remains immutable.
• SQLite remains the Runtime truth source; ANN and Substrate remain derived or
  governed sidecar surfaces.
• scheduled projection status must not be presented as synchronous embedding
  or ANN completion.
• Client evidence claims must not be presented as Runtime-verified evidence.
• Create 0.3.7 must not be published until Runtime v0.3.5 and its Docker
  image resolve because the installer selects that immutable tag by default.
• No package or image is announced until exact-version smoke tests pass.

Aionis v0.3.4

Aionis v0.3.4

Aionis v0.3.4 is the Runtime complexity-reduction and transport-boundary patch
for the v0.3 stable train.

It preserves the existing product loop while reducing accidental HTTP,
composition, configuration, and dependency complexity.

What Changed

• Reduced the active Runtime route matrix from 72 entries to 19 and removed the
  final eight temporary recall/context and tool-learning transports.
• Replaced internal route-to-route composition with typed product, planning,
  recall, learning, lifecycle, and storage services.
• Centralized governance decisions and AgentContext compilation/rendering.
• Added a narrow tool-selection receipt to /v1/guide and exposure-verified
  tool-selection learning through /v1/feedback.
• Migrated AionisManifest and active Runtime eval consumers away from retired
  internal HTTP routes.
• Reduced environment schema fields from 220 to 177 and import cycles from
  three to zero.
• Added structural CI budgets for source size, route exposure, configuration,
  import cycles, and SDK contract ownership.
• Unified Docker build and runtime stages on node:24-bookworm-slim, matching
  the validated release toolchain and removing the Substrate engine warning.

Release Coordinates

Artifact	Version
Runtime source	v0.3.4
Docker image	ghcr.io/ostinatocc/aionis:v0.3.4
aionis	0.3.8
@aionis/create	0.3.6
@aionis/sdk	0.3.14
@aionis/mcp	0.3.7
@aionis/aifs	0.3.4
@aionis/claude-code	0.3.5
@aionis/substrate	0.1.11
@aionis/manifest	0.1.1 source candidate

Verification

• Runtime typecheck, SDK ownership, complexity guard, and public smoke passed
  on integrated main.
• Full Lite suite passed: 63/63 JavaScript checks and 822/822 TypeScript tests,
  with zero skips.
• Real golden, ordinary-memory, multi-agent, negative-transfer, and judgment
  calibration product loops passed.
• Native zvec ANN contract and write-through verification passed without skips.
• External compatibility suites passed: 210 checks across Manifest, Substrate,
  SDK, CLI, Create, MCP, AIFS, and Claude Code.
• Same-machine Runtime-only A/B showed no regression in either execution order;
  the conservative round improved P50 by 13.77% and P95 by 0.49%.
• Local candidate SDK/MCP/Create entrypoint smoke passed.
• A fresh install from local Runtime main started without an embedding key
  and returned MCP context, receipt, and stable workspace scope.
• Docker image build passed. The candidate container returned a healthy
  /healthz response through a loopback-only host port and was removed after
  verification.

Release Safety

• SQLite remains the Runtime truth source.
• Zvec and Substrate remain governed candidate/sidecar sources.
• No compatibility route replaces the removed internal transports.
• Runtime tags are immutable; v0.3.3 remains unchanged.
• Create 0.3.6 must not be published until Runtime v0.3.4 and its Docker image
  resolve, because the installer selects that immutable tag by default.
• No package or image is considered published until exact-version post-publish
  smoke tests pass.

Aionis v0.3.3

Aionis v0.3.3

Aionis v0.3.3 is the Runtime trace-derived skill and release-hardening patch
for the v0.3 stable train.

It keeps the v0.3 product surface intact and closes the reviewed
Trace-Derived Skill Candidate loop into Agent context. Candidates still require
explicit review, materialization, and observe before they can influence
agent_context.

What Changed

• Closed the reviewed Trace-Derived Skill Candidate loop into Agent behavior:
  after materialize plus explicit observe, reviewed procedures are represented
  as execution-native workflow memory and can appear in agent_context.use_now
  and agent_context.prompt_text.
• Kept the candidate gate intact: /v1/skills/candidates remains review-first;
  unreviewed candidates are not injected into the Agent prompt.
• Added prompt ordering so execution memory and passed-solution procedure lines
  stay visible ahead of generic recovered-state lines under bounded prompt
  profiles.
• Prevented low-cost summary_only reviewed procedures from being surfaced as
  unnecessary rehydrate_payload tool hints.
• Hardened Runtime verifier execution boundaries, execution packet list limits,
  request guard recursion, IPv6 trusted proxy matching, SQLite migrations,
  recall rate-limit detection, and bounded stable JSON usage.
• Consolidated the Lite outbox surface to the associative-link worker that is
  actually present in the focused Runtime.
• Added default Runtime CI and release documentation version checks.
• Added published CLI release smoke coverage.
• Updated release records for the current public package train, including
  aionis@0.3.7, @aionis/sdk@0.3.8, and @aionis/substrate@0.1.11.

Current v0.3 Package Surface

Artifact	Version
Runtime source	v0.3.3
Docker image	ghcr.io/ostinatocc/aionis:v0.3.3
aionis	0.3.7
@aionis/create	0.3.4
@aionis/sdk	0.3.8
@aionis/mcp	0.3.2
@aionis/aifs	0.3.0
@aionis/claude-code	0.3.1
@aionis/substrate	0.1.11

Trace-Derived Skill Loop

The stable loop is:

1. Runtime derives a skill candidate from trace evidence.
2. Operator or host reviews the candidate through /v1/skills/candidates.
3. A promoted candidate is materialized into a procedure draft.
4. The host explicitly observes the materialized procedure.
5. /v1/guide can compile that reviewed procedure into Agent-facing context.

This release does not make trace-derived candidates automatic authority. It
makes the explicit reviewed path usable by the Agent after the host commits it.

Verification

Validated before release preparation:

npm run -s typecheck
node --test scripts/ci/lite-source-scope.test.mjs
npx tsx --test scripts/ci/lite-product-facade-route.test.ts scripts/ci/lite-skill-candidate-review-store.test.ts scripts/ci/lite-product-output-contract.test.ts scripts/ci/lite-product-output-assembler.test.ts scripts/ci/lite-runtime-tool-hints.test.ts scripts/ci/lite-sdk-client.test.ts scripts/ci/lite-sdk-guide-agent-context.test.ts
npm run -s lite:test
npm run -s runtime:smoke:fresh-install
AIONIS_PUBLISHED_CLI_SMOKE_SPEC="aionis@latest" npm run -s runtime:smoke:published-cli
git diff --check

Result:

• Typecheck passed.
• Source-scope checks passed.
• Focused trace-derived skill and Agent context regression group passed:
  124/124.
• Lite test suite passed: 732/736 passed, 4 skipped, 0 failed.
• GitHub CI passed on main before release preparation.
• Fresh install smoke passed with public @aionis/create@latest.
• Published CLI smoke passed with public aionis@latest.

Docker publishing is handled by the repository tag workflow
.github/workflows/docker.yml, which publishes:

ghcr.io/ostinatocc/aionis:v0.3.3
ghcr.io/ostinatocc/aionis:latest

Notes

The original v0.3.0 Runtime tag remains immutable as the first stable
baseline. v0.3.1 remains the cross-plane adjudication patch, and v0.3.2
remains the selected-profile admission activation patch. v0.3.3 is the
reviewed trace-derived skill Agent-context patch for the current Runtime source
and Docker release surface.

Aionis v0.3.2

Aionis v0.3.2

Aionis v0.3.2 is the Runtime profile-activation patch for the v0.3 stable
train.

It keeps the v0.3 product surface intact and adds the selected-profile
activation path for the reviewed closed-loop admission candidate. The global
Runtime default remains explicit and off.

What Changed

• Added profile-scoped admission candidate policy rules through
  AIONIS_ADMISSION_CANDIDATE_POLICY_PROFILE_RULES_JSON.
• Added a selected-profile activation quickstart:
  docs/AIONIS_ADMISSION_PROFILE_ACTIVATION_QUICKSTART.md.
• Added a copyable .env template:
  docs/examples/admission-profile-rules.env.
• Added profile-rule source/profile-id checks to the tool-E2E admission gate.
• Recorded the selected profile
  external-agent-e2e-worker-full-power as approved for profile-scoped
  activation.
• Kept global Runtime admission mode off; this release does not make the
  candidate a global default.
• Added DashScope text-embedding-v4 provider support.
• Added Substrate sidecar boundary documentation and external messaging
  contract documentation.
• Removed old Runtime demo/dashboard artifacts from the Runtime product
  surface.

Current v0.3 Package Surface

Artifact	Version
Runtime source	v0.3.2
Docker image	ghcr.io/ostinatocc/aionis:v0.3.2
aionis	0.3.4
@aionis/create	0.3.3
@aionis/sdk	0.3.1
@aionis/mcp	0.3.2
@aionis/aifs	0.3.0
@aionis/claude-code	0.3.1

Admission Evidence

The selected candidate policy is:

candidate_project_context_closed_loop_inspect

The selected profile id is:

external-agent-e2e-worker-full-power

The profile-scoped multi-step tool-E2E gate passed with:

• 40 / 40 completed records;
• 40 / 40 accepted-route;
• 40 / 40 action-completion;
• 0 route write/action violations;
• 0 terminal inspect exits;
• 0 report-conflict exits;
• 40 / 40 guide source checks from profile_rule;
• 40 / 40 guide profile checks for
  external-agent-e2e-worker-full-power.

The final profile-rule gate used the Aionis arm only, so it does not make a
same-run Full History budget claim. The same manifest has informational
profile-rule budget context from an earlier two-arm run: Aionis used 165,421
initial-context chars versus Full History 1,352,256 chars.

The global-active initial-context rerun remains the paired budget evidence for
the validated guide path: Aionis used 203,242 initial-context chars versus Full
History 1,352,256 chars while both arms completed 40 / 40 records.

Install

Recommended:

npx aionis setup

Docker:

docker run --rm \
  -p 127.0.0.1:3001:3001 \
  -v aionis-data:/data \
  ghcr.io/ostinatocc/aionis:v0.3.2

Selected-profile admission activation:

export AIONIS_ADMISSION_CANDIDATE_POLICY_MODE=off
export AIONIS_ADMISSION_CANDIDATE_POLICY_PROFILE_RULES_JSON='[
  {
    "profile_id": "external-agent-e2e-worker-full-power",
    "mode": "active",
    "scope_prefixes": ["my-project:"],
    "agent_roles": ["worker"],
    "context_modes": ["compact_agent"],
    "guide_modes": ["full_power"]
  }
]'

Replace my-project: with the scope prefix your host actually sends to
/v1/guide.

Verification

Validated before release preparation:

npm run -s typecheck
git diff --check

Docker publishing is handled by the repository tag workflow
.github/workflows/docker.yml, which publishes:

ghcr.io/ostinatocc/aionis:v0.3.2
ghcr.io/ostinatocc/aionis:latest

Notes

The original v0.3.0 Runtime tag remains immutable as the first stable
baseline. v0.3.1 remains the cross-plane adjudication patch. v0.3.2 is the
selected-profile admission activation patch for the current Runtime source and
Docker release surface.

Aionis v0.3.1

Aionis v0.3.1

Aionis v0.3.1 is the Runtime patch release for the v0.3 stable train.

It keeps the v0.3 product surface intact and adds the cross-plane adjudication
contract that stabilizes how lifecycle, tier, policy, credibility,
learning-control, execution, and rehydrate signals collapse into Agent Context.

What Changed

• Added docs/AIONIS_CROSS_PLANE_ADJUDICATION.md.
• Added product-output regression coverage for cross-plane precedence.
• Explicit lifecycle_state=archived and policy_memory_state=retired now
  block direct use during Agent Context assembly.
• policy_memory_state=contested and credibility_state=contested now route to
  inspect_before_use.
• Release docs now report the current npm patch versions in the v0.3 stable
  train instead of implying every external package must share the Runtime tag.

Current v0.3 Package Surface

Artifact	Version
Runtime source	v0.3.1
Docker image	ghcr.io/ostinatocc/aionis:v0.3.1
aionis	0.3.4
@aionis/create	0.3.2
@aionis/sdk	0.3.1
@aionis/mcp	0.3.2
@aionis/aifs	0.3.0
@aionis/claude-code	0.3.1

Verification

Validated locally before release preparation:

npm run -s typecheck
npx tsx --test scripts/ci/lite-product-output-assembler.test.ts scripts/ci/lite-cross-plane-adjudication.test.ts
npm run -s lite:test
npm run -s runtime:smoke:external-packages
npm run -s runtime:smoke:fresh-install
docker build -t aionis:release-smoke .
git diff --check

Result:

• Typecheck passed.
• Product output regression tests passed: 47/47.
• Lite test suite passed: 687/687.
• External package smoke passed with published @aionis/sdk@latest,
  @aionis/mcp@latest, and @aionis/create@latest.
• Fresh install smoke passed with public @aionis/create@latest.
• Docker build passed for aionis:release-smoke; /healthz and /readyz
  returned ok: true from the container.

Install

Recommended:

npx aionis setup

Docker:

docker run --rm \
  -p 127.0.0.1:3001:3001 \
  -v aionis-data:/data \
  ghcr.io/ostinatocc/aionis:v0.3.1

Notes

The original v0.3.0 Runtime tag remains immutable as the first stable
baseline. v0.3.1 is the patch release for the current Runtime source and release
documentation alignment.