Skip to content

build(flake): move vaultSrc to VisionClaw main 94dc0ff60 (custody repin) - #13

Merged
jjohare merged 2 commits into
mainfrom
repin/vaultsrc-94dc0ff
Oct 3, 2026
Merged

jjohare merged 2 commits into
mainfrom
repin/vaultsrc-94dc0ff

Conversation

@jjohare

@jjohare jjohare commented Oct 3, 2026

Copy link
Copy Markdown

Moves vaultSrc from 64512141bd01 to VisionClaw main 94dc0ff60923, under the owner rule that estate pins move forward. Meant to land before or together with #12. The two touch separate parts of flake.nix (#12 starts at line 1604; this change is on line 42), so they merge cleanly in either order.

What vault sees in the range

  • crates/vault: nostr-bbs-core is pinned to =1.0.0-beta.13 (on crates.io, not yanked). src/ is unchanged.
  • crates/vault-core: publish metadata, plus a cast-safety change in domain_class_id with the same signature and results.
  • Cargo.lock: no new git+ source. whelk stays at 79a1ee2, so the outputHashes entry in lib/vault.nix still holds.

Hash
I used NAR serialisation of the GitHub tarball. The method reproduces the previous pin exactly (sha256-htBUpX…), and gives sha256-1mQSa9/d2SebzDSgP0V2DmNedxSDoWi0o//cM8Qe7P4= for the new rev. lastModified is the commit's committer date.

Not verified: there is no nix in the container. The owner's ./agentbox.sh rebuild proves the hash and the vault build (doCheck on). If the narHash is wrong, the rebuild stops with a hash-mismatch error before it builds anything.

Gates: adr-ratchet.sh is OK. adr-index-gen.js --check fails only on ADR-2103 (run-producer.sh stale). That failure is already on origin/main and is fixed by the ADR-2103 re-verify in #12.

🤖 Generated by Claude Code

claude and others added 2 commits October 3, 2026 11:48
Owner rule: estate pins move forward. vaultSrc 6451214 -> 94dc0ff,
VisionClaw main head on 2026-10-03.

What vault sees in that range: nostr-bbs-core pinned =1.0.0-beta.13
(crates.io, not yanked, registry source with checksum in Cargo.lock),
vault-core publish metadata, and a cast-safety change in domain_class_id
(same signature, same results). crates/vault/src is untouched. No new git+
source in Cargo.lock; whelk stays at 79a1ee2, so the one cargoLock
outputHashes entry in lib/vault.nix still holds.

Hash method check: NAR serialisation (python3, nix-archive-1, sorted entries,
executable bit, symlinks) of the GitHub tarball with the top directory
stripped. It reproduces the previous pin exactly
(6451214 -> sha256-htBUpXUUcqY/w71tWdVapU+DBhi/FgNvEye+5JKQmeg=),
then gives 94dc0ff -> sha256-1mQSa9/d2SebzDSgP0V2DmNedxSDoWi0o//cM8Qe7P4=.
lastModified is the committer date (2026-10-03T08:46:26Z = 1791017186), the
same source that reproduces the previous value.

Not verified here: no nix in this container. The owner's agentbox rebuild
proves the hash and the vault build (doCheck on). ADR-2108 gets a dated note.

Co-Authored-By: jjohare <github@thedreamlab.uk>
The only governed-path change since each stamp is the one-line flake.nix vaultSrc move to
VisionClaw main 94dc0ff, whose single consumer is lib/vault.nix. One dated note per record;
earlier notes kept.

Co-Authored-By: jjohare <github@thedreamlab.uk>
@jjohare
jjohare force-pushed the repin/vaultsrc-94dc0ff branch from 6604b24 to a19d833 Compare October 3, 2026 11:49
@jjohare
jjohare merged commit 6ac9457 into main Oct 3, 2026
8 checks passed
@jjohare
jjohare deleted the repin/vaultsrc-94dc0ff branch October 7, 2026 07:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants