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

MemForge v0.8.1: portable, agent-neutral persistent memory format for coding agents. This deposit anchors the v0.8.1 ship state (reference-CLI package 0.8.1; spec snapshot spec/VERSION 0.6.3). The bundle ships the spec snapshot plus the full reference-CLI artifacts (CHANGELOG, README, license, examples/). What v0.8.1 adds v0.8.1 is a patch release: one generator fix plus the matching spec clarification. It is additive and backward-compatible; regenerating an index only shortens over-cap hooks, and no existing folder breaks. - Deterministic pointer-hook truncation in memory-index-gen. The generator embedded the full frontmatter description in each MEMORY.md pointer line, so a rich description produced a pointer line over the spec's 180-byte cap that the audit already flagged as an integrity violation. The generator now truncates the hook to fit (split on a UTF-8 codepoint boundary, append a literal ellipsis); the authoritative full description stays in the file frontmatter and the recall index, so truncation is lossless for recall (recall reads the frontmatter description, never the MEMORY.md hook). When the title and path prefix leaves three or fewer bytes for a hook, the hook is omitted entirely rather than appended over-cap. - Spec 0.6.2 to 0.6.3. The MEMORY.md format section gains the generator pointer-truncation rule as a generation-time guarantee. No new folder integrity invariant: truncation is a property of how the index is generated, not of folder conformance, so older generated indexes are not retroactively invalidated. The change reconciles the generator with the existing 180-byte audit check. Release-rigor framing v0.8.1 ran an internal cross-family review panel pre-tag (architect plus an adversarial critic on a different model family) on the spec delta and the new code surface. The critic caught an edge-case correctness bug in the truncation path (the prefix-over-cap case appended an over-cap hook instead of omitting it); it was fixed before tag. The new code surface is pure string formatting with no new input, output, subprocess, filesystem, or cryptographic surface, so the threat-modeler pass was waived with documentation. 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. Reference implementation (PyPI package ildan-memforge==0.8.1) - The public command surface is unchanged from the prior release; the change is internal to the index generator.- 492 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.3)- VERSION (spec version file; 0.6.3)- taxonomy.yaml- v0.8.1-known-limitations.md (living-doc snapshot at v0.8.1)- CHANGELOG.md (full history through v0.8.1)- LICENSE (Apache-2.0)- README.md- examples/ drop-in scripts (commit-msg hook bash plus PowerShell, auto-commit watcher bash plus PowerShell, recall synonyms example, WebSocket scaffold) Bundle SHA-256 (v0.8.1-bundle.zip): 8cf75d37308281e1e5798598506e2cfa984fcff7dad17d734a81a5febad7bf08 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 plus spec history https://github.com/ildan-ai/memforge https://github.com/ildan-ai/memforge/releases/tag/v0.8.1 License: Apache-2.0