fix: write qdocco outputs atomically

[tiye]

Summary

• add RFC 0101 for qdocco atomic document output
• write generated documents through an exclusive same-directory temporary file
• preserve existing output and reserved temporary files on write collisions

Validation

• make check
• git diff --check

This PR is intentionally stacked on PR #42 and should not be merged independently of the chain.

[Copilot]

Pull request overview

This PR updates qdocco to write generated HTML/Markdown outputs via an exclusive same-directory temporary file and a final rename step, aiming to avoid leaving partial documents on interruptions, and documents the contract in a new RFC.

Changes:

• Add RFC 0101 specifying qdocco’s atomic output contract (temp file + sync + rename, collision handling).
• Implement write_output() in qdocco to write via an exclusive temp file and rename into place, replacing fs::write.
• Add a unit test for collision behavior and update project/RFC range references in docs.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File	Description
src/bin/qdocco.rs	Implements atomic-ish output writing via exclusive temp file + sync + rename, and adds a collision test.
RFCs/0101-qdocco-atomic-output.md	Defines the new atomic output contract for qdocco.
RFCs/0000-project-scope.md	Updates the documented RFC coverage range to include RFC 0101.
README.md	Updates the README’s referenced RFC range to include RFC 0101.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.