FoxIR v1.0.17
Two documentation commits on top of v1.0.16 and no code changes at all — runtime behavior is
what v1.0.16 already was. If you came here looking for a fix, there is none in this release.
What landed
docs/changes/pluggable-memory-provider/ — an SDD for a pluggable MemoryProvider front door:
FoxIR's core would know no specific memory service, and wiring mem0 / MemoryHub / anything later
would be one config entry or one adapter instead of an embedded code path. Status is draft, not
implemented — the existing deep_memory / SQLite behavior is untouched, and the baseline
recorded in the docs is b542a35.
Why the design body lives at specs/…-spec.md
.gitignore:54 carries the bare filename pattern SPEC.md ("local-only documentation"). A bare
pattern matches at any depth, and on this OS it is case-insensitive — so every
docs/changes/*/spec.md is silently un-addable. The first commit of this release contained
tasks.md and log.md and not the design body; the body was renamed to
specs/pluggable-memory-provider-spec.md, the same path style that let 72d62b8 publish a spec.
Three other design bodies are still under that rule and remain local: multi-agent-orchestration,
memory-hub-sync, adopt-agentskills-skill-spec. The rule itself was not changed — publishing
those was nobody's request.
Verification
cargo test --lib → 379 passed / 0 failed / 18 ignored, finished in 1.13s.
That is two more than v1.0.16's note recorded (377 passed, 2 known failures in cases that read the
real Prefetch / Recent files). Those two passed this round because they depend on machine state,
not because anything improved.
The 18 #[ignore] real-machine browser cases were not re-run: there is no code change for them
to guard. This is not a green-light claim about the browser path.
Release mechanics
Cargo.toml and Cargo.lock are bumped in this one commit. v1.0.15 split them across two commits,
which left the tag's lock file at 1.0.14 — building from that tag dirties the working tree.