Reset inodes on index writes to better support hard links

[jviotti]

Signed-off-by: Juan Cruz Viotti jv@jviotti.com

[augmentcode]

🤖 Augment PR Summary

Summary: This PR updates index/build output writes to recreate files instead of truncating them in-place.

Changes:

• Deletes existing dependency/index/metapack output files before rewriting to force a fresh inode
• Applies the inode-reset behavior across filesystem adapter writes, JSON output writes, URI-template route generation, and metapack stream writes
• Adds a CLI regression test that rebuilds an index and asserts only the version marker keeps its inode

Technical Notes: The intent is to avoid hard-link side effects by ensuring rebuilds create new files rather than modifying existing hard-linked inodes.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.

[cubic-dev-ai]

1 issue found across 6 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/index/output.h">

<violation number="1" location="src/index/output.h:91">
P2: Unconditionally removing the file before opening the stream can delete the existing file if the open fails, causing data loss on error paths (and in release builds the assert doesn’t guard against a bad stream). Consider a safer write strategy that preserves the old file until the new write succeeds.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}