docs: capture 3 todos from planning gap review

[FSM1]

• TEE critical integration bugs (C1/C2/H1) - breaks all IPNS republishing
• IPNS sequence fallback to 0 - silent data loss risk in desktop client
• Debug eprintln! cleanup - filename leakage in privacy-focused app

Area: api, desktop

https://claude.ai/code/session_01JJP6JPrN66GarDbui7r5mg

Summary by CodeRabbit

• Documentation
  • Project roadmap updated with six pending development items.
  • Planning documents added for upcoming improvements to system reliability, data integrity handling, and logging practices.

[coderabbitai]

Walkthrough

Planning documentation updated with pending todos count incremented from 3 to 6. Three new detailed planning documents added outlining TEE integration bug fixes, IPNS sequence fallback handling, and debug statement removal from desktop FUSE code.

Changes

Cohort / File(s)	Summary
State & Tracking .planning/STATE.md	Updated pending todos count from 3 to 6; completed items removed and three new pending items registered.
New Planning Documents .planning/todos/pending/2026-02-10-fix-tee-critical-integration-bugs.md, .planning/todos/pending/2026-02-10-ipns-sequence-fallback-to-zero.md, .planning/todos/pending/2026-02-10-remove-debug-eprintln-statements.md	Three new planning documents added documenting: TEE integration bugs (C1: missing epoch fields, C2: encoding mismatch, H1: health endpoint shape), IPNS sequence number fallback issue with proposed caching/serialization solution, and debug eprintln removal targeting FUSE operations with proposed log-level-aware replacement.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and specifically summarizes the PR's main purpose: capturing three pending planning items from a gap review into documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch claude/review-planning-gaps-pfXc4

---

No actionable comments were generated in the recent review. 🎉

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

Adds three new planning TODOs (API + desktop) identified during recent security/planning gap reviews, and updates the central planning state to track them.

Changes:

• Added a TODO to remove debug eprintln! statements in the desktop FUSE layer (privacy/logging hygiene).
• Added a TODO to fix IPNS sequence fallback-to-zero behavior in the desktop client (data integrity risk).
• Added a TODO to fix critical TEE ↔ API integration mismatches preventing automatic IPNS republishing.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
.planning/todos/pending/2026-02-10-remove-debug-eprintln-statements.md	New pending TODO capturing stderr filename leakage from debug eprintln! in FUSE ops.
.planning/todos/pending/2026-02-10-ipns-sequence-fallback-to-zero.md	New pending TODO capturing IPNS sequence rollback risk and mitigation ideas.
.planning/todos/pending/2026-02-10-fix-tee-critical-integration-bugs.md	New pending TODO capturing three API/TEE integration bugs blocking republish.
.planning/STATE.md	Updates pending TODO count and list to include the three new items.

[Copilot]

.planning/STATE.md is being updated (pending todo count + list), but the _Last updated: metadata at the bottom still says 2026-02-09. Please bump it to reflect this change so the state file stays self-consistent.