feat(memory): path-scoped rules + project memory write-path (#-remember)

[oratis]

Summary

Closes two §3.6a memory gaps from the audit.

Path-scoped rules — .deepcode/rules/*.md were loaded flat with no scope info. Now each rule's frontmatter globs (or applyTo/paths) is surfaced in its injected header — # rule: ts.md (applies to: src/**/*.ts, test/**) — so the model applies it only when editing matching files, and the frontmatter fence is stripped from the body.

Agent/user memory write-path — there was a read path but nothing ever wrote project memory (the "# to remember" in /help was aspirational):

• projectMemoryKey(cwd) / projectMemoryPath(home,cwd) → ~/.deepcode/projects/<slug>/memory/MEMORY.md (mirrors the harness layout).
• rememberFact(cwd, fact) appends a bullet (writes a header on first write).
• loadMemory now reads that project-memory file too (step 1b, after user memory).
• REPL: a #<text> line remembers the fact (no agent turn) — the documented shortcut, now real.

Tests

+2 (loader.test.ts): rule glob annotation + frontmatter strip; rememberFact → loadMemory round-trip (both facts present, header written once). Core suite 608 green.

Note

Path-scoping is annotation-based (the scope is declared + visible to the model) rather than hard filtering — a CLI agent doesn't know the "active file" at memory-load time, and globbing the whole tree per launch would be costly. This matches how an LLM-driven agent self-applies scoped rules.

🤖 Generated with Claude Code