Agent Wiki 0.8.15

Agent Wiki 0.8.15 adds an optional task-local trace index for installations whose persistent filesystem is slow for SQLite queries. Search, provenance and the conversation catalog use verified disposable indexes, while original JSONL records, source paths and citations remain authoritative and unchanged.

Enable it through the managed lifecycle with --trace-index-root /tmp/wiki-trace-index or WIKI_TRACE_INDEX_ROOT=/tmp/wiki-trace-index. The location must be outside the complete data root and owned by the serving user. Every replacement verifies or rebuilds its indexes before listening. The default remains unchanged. Full-corpus startup and serving performance must be qualified for the target installation.

This is an initial-development release from 942dc9e323625b383c83a5e680565fa0411b5cd0. The Linux x86-64 OCI artifact includes signed provenance, runtime qualification, security applicability and SBOM records. Native host closures are not included; clean-consumer installation remains unqualified. The OCI runtime requires no Nix installation.

Use the signed manifest and qualification record to verify the archive and image identity. Verify SSH signatures in namespace agent-wiki-release against the established maintainer key fingerprint SHA256:1Np/3VtW8SH6zILX+qft4EhOs5KnErjy0+RFr2zXrfQ. Preserve the prior artifact and a consistent recovery pair before upgrading. This release does not automatically change existing installations.

Validation passed on the exact source revision: 215 source tests and 72 browser tests on Linux and macOS, production dependency audit, nine locked Nix checks, 18 native builder checks, and six actual-container lifecycle scenarios covering replacement, fallback, persistence and recovery. Native builder checks do not qualify native closure distribution.

The runtime component scan reports 24 CVE matches across eight components; this is not a clean component scan. The signed applicability review found no known reachable High or Critical issue in inspected supported workflows and records residual limitations, including a reachable upstream Low OpenSSL memory-pressure issue. Review that record before deployment.

Private ECS installations needing a measured startup allowance can independently pin Wiki service module 0.1.2. Select a grace period from actual corpus initialization and verify the complete service lifecycle.