Ruoshui Doc Sync

• docs/project/state.md for current project status or active defaults
• docs/project/tasks.md for next actions, open work, or iteration tracking
• docs/project/engineering-memory.md for durable pitfalls and default workflow changes
• focused docs in docs/project/** for stable architecture, style, platform, or handoff topics
• docs/assets/** for asset policy, inventory, PoC, or validation records
• docs/iterations/** for iteration-specific experiment records

Decision Heuristics

• If the fact helps a future thread resume correctly, it probably belongs in docs.
• If the fact only matters for one narrow experiment, put it in the iteration doc, not project-wide docs.
• If the lesson changes the default workflow, add it to engineering-memory.md.
• If the change affects a stable domain workflow such as React, Node, Web3D, or Cloudflare, also update the corresponding skill.
• If a doc update would only repeat information already captured in the right canonical file, link or refine instead of duplicating it.

Good Outcome

• current docs match current code and workflow
• status, task tracking, and durable lessons land in the right files
• no parallel handoff note exists without a clear reason
• future resume work needs less thread archaeology