release: publish engram-parser v0.3.0 checkpoint-substrate release #89

Current qualification and remaining work — 2026-10-02 UTC

Keep this issue open: publication is not complete. The historical checklist below is retained; the measured snapshot and explicit outstanding items here supersede its unqualified unchecked implementation status.

Audit baseline: 70da04b35040e2a0865dfd0ef42d1ba5996ab06d. SHA256 comparison found all 57 audited local source/test/package-input files identical to this remote main commit. No source edits or publication were performed.

Verified at the audited baseline

The RustSec check has now completed successfully; it was pending when the initial audit response was written.

Packaging used a source-identical temporary copy without VCS metadata to respect the workspace no-Git-operations rule. The archive contained 40 files, versus the earlier 41-file report that included Cargo's VCS metadata. This validates package contents/builds, not clean-checkout or VCS provenance. Dry-run success does not establish registry ownership or actual publication.

Real-checkpoint evidence is recorded in RM-1794: prior Qwen GGUF/Phi-3 runs and fresh Granite 4.1 3B sharded Safetensors runs both passed their stated checks. No fresh local real-GGUF run occurred in this audit.

Remaining before publication

• Add docs.rs feature configuration (for example [package.metadata.docs.rs] with all-features = true) and verify documentation. Current manifest omits it, so default hosted documentation would omit Safetensors/mmap APIs. docs.rs reference.
• Reconcile the packaging warning policy: the intentional tests exclusion emits 11 ignored-integration-test-target warnings, while RELEASE.md says any packaging warning closes the gate. Explicitly handle the known exclusions or remove their cause; do not call the gate warning-free.
• Recommended final-candidate validation: rerun the pinned Qwen GGUF smoke from the guide, record source/fixture identity and first/warm results. Reuse the harness; no inference engine or GPU is required.
• Re-run the applicable release gate on the final clean release commit after changes; verify package provenance, metadata/name and publication authority.
• Publish v0.3.0 only with maintainer authorization; verify the registry version and docs.rs build.
• Only then dispatch the Release workflow with the published SHA and v0.3.0 tag.

Real-MoE extraction and independent numerical dequantization comparisons would provide additional confidence in those helpers; they are not silently added as new v0.3.0 scope.

Relationships and scope

Parent: RM-1787. Completed smoke scope: RM-1794. Existing native prerequisites, ownership, project and milestone are retained; this update does not bulk-close or reclassify other issues. GitHub delivery record: #89. Transformer topology discovery remains v0.4.0 work.

Audit logs are local temporary evidence under /tmp/engram-publish-audit/; results above are preserved in this issue rather than implying those paths are shared artifacts.

Original release requirements (retained for traceability)

Summary

Publish engram-parser v0.3.0 as the first public crates.io release, positioned as a general GGUF + Safetensors checkpoint substrate rather than a MoE-only extractor.

Operational tracking: ANN/SNN Hybrid

v0.2.0 is an unpublished development version and must not be treated as a registry release.

First-publication hardening

• GGUF tensor-directory invariants fail closed on duplicate names, invalid overlap policy, and out-of-bounds payloads (Linear RM-1460).
• Default-feature CI runs independently of all-feature CI (Linear RM-1464).
• Stale Azure Pipelines references are removed; Azure CI is not restored.
• REVIEW/CHANGELOG/version history explicitly record v0.2.0 as unpublished development history.

v0.3.0 checkpoint-substrate gate

• Architecture/scope documentation reflects ANN/SNN checkpoint-substrate direction.
• Safetensors raw payload access is implemented and validated.
• Common GGUF/Safetensors checkpoint/tensor abstraction is available.
• Existing GGUF mmap/K-quant behavior remains covered.
• MoE functionality remains supported or has a documented migration path.
• Cross-format fixtures/parity tests are green.
• README/package/rustdoc present v0.3.0 as the first public release.

Qualification

• Default features: cargo fmt --check, clippy, build, test.
• All features: clippy, build, test.
• MSRV gate green.
• cargo doc --all-features --no-deps.
• cargo package --list inspected.
• cargo package.
• cargo publish --dry-run.
• crates.io package name and metadata verified.
• crates.io publication succeeds before creating the matching v0.3.0 tag/GitHub Release.

Release boundary

Transformer role/topology discovery in RM-1785 belongs to engram-parser v0.4.0 and is not a v0.3.0 publication prerequisite. The checkpoint-substrate and publication gates above remain required.

Explicit exclusions

• GOZ1 remains in grok-ozempic.
• GPU/CUDA remains in myelin-accelerator.
• Transformer numerical execution remains outside this crate.
• ANN↔SNN orchestration remains in hybrid-fusion.
• SAAQ campaign policy remains outside this crate.

No tag or GitHub Release should be created until the publication gate is actually satisfied.