fix: clear script database before rebuild to prevent unique constraint violation

[ellie]

The script store build() replays all records from the record store into SQLite but never cleared the database first. Stale rows from previous builds caused unique constraint violations on the name index when scripts were renamed or recreated.

Checks

• I am happy for maintainers to push small adjustments to this PR, to speed up the review cycle
• I have checked that there are no existing pull requests for the same thing

[greptile-apps]

Greptile Summary

Fixes the reported bug where stale SQLite rows caused unique constraint violations during script rebuild. The fix correctly clears existing data before replaying records, preventing name conflicts from renamed scripts. The approach is straightforward and solves the problem as described.

Important Files Changed

Filename	Overview
crates/atuin-scripts/src/store.rs	Adds clear() call before replaying records in build(). Correctly prevents unique constraint violations when scripts are renamed or recreated. Includes helpful comment explaining the fix.
crates/atuin-scripts/src/database.rs	Adds new clear() method that deletes all rows from script_tags then scripts in the correct FK order. Effectively prevents stale rows from causing conflicts during rebuild.

_{Last reviewed commit: 5fa1fc0}

[greptile-apps]

_{2 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}