MemForge: Portable, agent-neutral persistent memory format for AI coding agents (v0.8.0)

MemForge v0.8.0: portable, agent-neutral persistent memory format for coding agents. This deposit anchors the v0.8.0 ship state (reference-CLI package 0.8.0; spec snapshot spec/VERSION 0.6.2). The bundle ships the spec snapshot plus the full reference-CLI artifacts (CHANGELOG, README, license, examples/). What v0.8.0 adds v0.8.0 is an additive, backward-compatible release. Three changes: - Wikilink rewriting in the link rewriter. memory-link-rewriter rename and rename-batch now rewrite [[wikilinks]] (both [[token]] and [[token|display]] forms) when a file is renamed, so a rename no longer orphans inbound wikilinks. Rewrites are restricted to the rename alias set (old filename stem, old name, uid) so prose, cross-reference text, and code fragments that happen to match the [[ ]] pattern are left untouched. Cross-root ambiguity is resolved within the linking file's own root; tokens that remain ambiguous are skipped and listed. Every rewrite is logged, and the pass is idempotent (a second run changes nothing).- Pointer-line and MEMORY.md length caps raised from 150 to 180. Descriptive filename slugs are longer than short identifiers; at the 150-byte ceiling the hook portion of an index pointer line had little room. The change loosens a SHOULD warning threshold, so no previously-conformant folder becomes non-conformant.- Non-spec-tier warning in memory-audit. The spec defines two tiers, index and detail. A file carrying any other tier value was previously excluded from MEMORY.md and rollup generation with no diagnostic. memory-audit now emits an advisory (non-blocking) warning naming the offending tier value. No auto-correction. All three changes are additive or threshold-loosening; every prior-version folder remains conformant, and upgrading requires no data migration. Release-rigor framing v0.8.0 ran an internal multi-voice review panel pre-tag (architect plus adversarial critic) on the spec delta and the new code surface; findings were addressed before tag. This is an internal review pass; it is NOT a substitute for independent red-teaming, third-party pentest, or formal security audit. No external security audit has been performed on this release. Residuals tracked in known-limitations.md reflect the internal panel's review scope. Reference implementation (PyPI package ildan-memforge==0.8.0) - The reference CLI ships under a single memforge dispatcher; the public command surface is unchanged from the prior release (the link rewriter gains wikilink handling within its existing rename / rename-batch subcommands).- 483 tests pass on the CI matrix (ubuntu, macos, windows across Python 3.10 / 3.11 / 3.12); 36 GPG-gated tests skip without secret material.- The release tag is signed and ships a CycloneDX SBOM, with a pip-audit supply-chain gate in CI. Bundle contents - SPEC.md (spec_version 0.6.2)- VERSION (spec version file; 0.6.2)- taxonomy.yaml- v0.8.0-known-limitations.md (living-doc snapshot at v0.8.0)- CHANGELOG.md (full history through v0.8.0)- LICENSE (Apache-2.0)- README.md- examples/ — drop-in scripts (commit-msg hook bash + PowerShell, auto-commit watcher bash + PowerShell, recall synonyms example, WebSocket scaffold) Bundle SHA-256 (v0.8.0-bundle.zip): b3348bc31a4d0d23e3b901006d65889e32a37ab08ef42f8c35382df84f2b4068 Defensive-publication context This is one of three timestamped anchors for the MemForge spec text and reference tooling (Channel 1: Software Heritage SWHID; Channel 2: this Zenodo deposit; Channel 3: GitHub release tags). The concept DOI 10.5281/zenodo.20113963 always resolves to the latest archived version. This version mints a fresh Zenodo version under that concept record. Install pip install ildan-memforge Source code + spec history https://github.com/ildan-ai/memforge https://github.com/ildan-ai/memforge/releases/tag/v0.8.0 License: Apache-2.0