faf 8.2.1 → 8.2.2

package/dist/core/safe-write.d.ts

@@ -22,8 +22,8 @@
  * writing a file it was never asked to write. A read of project context
  * through a link must land on a .faf or .fafm file instead, so `project.faf →
  * .env` is refused even though .env is in the project — or, for a read of an
- * AI context file, on another AI context file (`faf recover` reads CLAUDE.md →
- * AGENTS.md), the rule the writers use.
+ * AI context file, on another AI context file (CLAUDE.md → AGENTS.md), the
+ * rule the writers use.
  *
  * Rule 3 — never leave a half-written file. A write goes to a temp file in the
  * same folder, is flushed to disk (fsync), then renamed over the original in

package/dist/core/version.d.ts

@@ -2,7 +2,7 @@
  * The `.faf` format series a freshly written file is stamped with — the single
  * source of truth for `faf_version`.
  *
- * Everything that authors a new `.faf` (detect, recover, conductor) and the
+ * Everything that authors a new `.faf` (detect, conductor) and the
  * `migrate` target reads it from here, so the version can never drift file-to-
  * file again. (That drift is exactly what left those paths stranded on the old
  * `2.5.0` while the ecosystem moved to the `3.0` series.)