Repository navigation
build: estate pin upgrade (agentic-qe 3.14.7, wrangler 4.147.0, solid-pod-rs alpha.12; mermaid-cli and web-researcher held) - #18
Merged
Conversation
Owner-directed estate upgrade to npm latest (published 2026-10-02T09:25Z, inside the 72-hour window). Patch release; no major change at the root. Lock: --before=2026-10-02T09:35:00Z, 756 entries, 0 added, 0 removed, 50 changed. One transitive major: vibium 0.1.8 -> 26.8.21, now an optional peer of aqe and therefore not installed (`--production`); the qe-browser engine stays opt-in via `aqe init`. `aqe mcp` answers tools/list with 91 tools on both 3.14.4 and 3.14.7. Hash method proved on the existing pin first (flat tarball sha256; NAR of the FOD tree after `npm ci --production --ignore-scripts --legacy-peer-deps`): 3.14.4 tar sha256-9lwDo+qpSiIxVtg9r/Kee9TdZru9fVBXSp5/Vpy9x6c= mods sha256-Vvg/qJpAvOU9s2afX/JZLv1C6YJfHCVHo2R9T3BYuwA= (both = pin) 3.14.7 tar sha256-dtTtXe+f2O6gidB7xIIDJ3scr5XxdzdCwKqFRdLVuMY= mods sha256-r/FZrkcdDt1o+Tyrga6QcuEHcLPlgpY1t2efFgMyfP4= (stable over two installs) Image unverified until the host rebuild runs. Co-Authored-By: jjohare <github@thedreamlab.uk>
…52d3ee) Co-Authored-By: jjohare <github@thedreamlab.uk>
Owner-directed estate upgrade to npm latest (published 2026-10-02T11:30Z, inside the 72-hour window). Minor releases, no major change. Lock (stripDevDeps applied, --before=2026-10-02T11:40:00Z): 91 entries, 0 added, 0 removed, 9 changed: workerd/miniflare 20260926 -> 20261001, undici 7.29.0 -> 7.29.1. `wrangler --version` reports 4.147.0; `wrangler d1 --help` runs. Hash method proved on the existing pin first (flat tarball sha256; NAR of the FOD tree after stripDevDeps + `npm ci --production --ignore-scripts --legacy-peer-deps`): 4.142.0 tar sha256-yOmfTH0Xzq5Qizv1Xf6BSlt148KkH+pUJWvXmEwh7X4= mods sha256-6uc4Z3X3djtgPa9LgbEHunDlIrNFb7nDVMyJJyMp6WQ= (both = pin) 4.147.0 tar sha256-xC0hD6GfbkC2Oo3zsSd0ATbf/nUl7p7YK4qxg9LNg5U= mods sha256-VfJKdHz1BWwxofXSq70Un/gR4ooJo92GnzLzrHOPuD4= (stable over two installs) Image unverified until the host rebuild runs. Co-Authored-By: jjohare <github@thedreamlab.uk>
…1c8bd) Co-Authored-By: jjohare <github@thedreamlab.uk>
Estate upgrade pass, 2026-10-03. 12.0.0 is a major. Checked against the owner's rule (hold if any corpus render changes): - the VisionFlow render gate (`--check --render --only agentbox/36-`) passes 7/7 on both 11.17.0 and 12.0.0, run on a scratch copy of the corpus with the image's own mmdc wrapper (Nix chromium plus the puppeteer config); - but all 7 SVGs change geometry (viewBox: AB-36.3 2015x1903 -> 476.5x2506, AB-36.7 965x2044 -> 1953x1306, ...) and grow ~7x, because fonts are now embedded by default; - -w/-H/-f are removed (replaced by --size and --pdf-paper-format), and skills/mermaid-diagrams/scripts/render.sh passes -w/-H; - the 2026-10-01 audit blocker is resolved: a 12.0.0 lock audits 0 findings, against 1 low on 11.17.0. Pin, lock and hashes are unchanged; only the hold note moves. Co-Authored-By: jjohare <github@thedreamlab.uk>
cff75f7) Co-Authored-By: jjohare <github@thedreamlab.uk>
Estate upgrade pass, 2026-10-03. v1.49.4 (2026-09-28) is the latest release. Its go.mod moves the `go` directive from 1.25.13 to 1.27.1, but the pinned nixpkgs 9ae611a4 provides go_1_26 (1.26.3) at most, and buildGoModule builds with GOTOOLCHAIN=local, so the build would fail. Nix input pins stay fixed for this pass, so the package holds. Pin and hashes are unchanged; only the hold note is added. The source-hash method still checks out: the NAR of the v1.49.3 GitHub tarball reproduces the pin (sha256-+k2sEHfhmahCRXj60OGW8zYqb6iz0D8DQY2WSpBmSWA=), and v1.49.4 would be sha256-QqVWBKymcKgyBYW3vK9DiRb3lCo/qJdFn/sEvb+bUek=. go.sum also changed, so vendorHash would need recomputing. supercronic: v0.2.49 is still the latest aptible release, so it is unchanged. Co-Authored-By: jjohare <github@thedreamlab.uk>
…mmit (09e6271) Co-Authored-By: jjohare <github@thedreamlab.uk>
Estate upgrade to the crates.io max: tag v0.5.0-alpha.12, cut from main d64131b32be2fc07ea120195686d2e1d3fbbe3c2 on 2026-10-02T23:33Z. Upstream CI is green on that commit (msrv 1.88, test matrix, cargo-audit, cargo-deny). The image's Rust is rust-overlay stable latest, well above 1.88. Compatibility: alpha.12 changes the TxInfo.vin, BuiltTx.txid and Mrc20AnchorResult.report struct literals. These live in the library's mrc20/bitcoin_tx modules behind feature `mrc20`, which only the server's `forge-anchoring` enables, and no agentbox feature set does. lib/solid-pod-rs.nix builds only the solid-pod-rs-server binary and constructs none of these types. Server and library feature sets are identical to alpha.9. The postPatch `--replace-fail` target line is still present exactly once. `cargo check --locked --release -p solid-pod-rs-server` with the agentbox patch applied and every flake-selectable feature (security-primitives git config-loader acl-origin did-nostr rate-limit quota oidc dpop-replay-cache legacy-notifications webhook-signing) passes in 40 s, which also proves the vendored lock is consistent. lib/nostr-pod-bridge.nix stays on alpha.9 by its own solidRev and Cargo.lock: separate binary, no linkage. Its tests/fixtures/blocktrail-s3/emit.rs builds TxInfo literals but is not a compiled cargo target. The pin comment records the decoupling. Hash method proved on the existing pin (NAR of the GitHub archive tree, as fetchFromGitHub): 1d9da527 (alpha.9) sha256-0/iDL8E9J5SGFnnJQwR3wP/qAjl9AHiKyKxU1U6qRfc= (= pin) d64131b3 (alpha.12) sha256-nMqFCn/QKpl49nQ/voONbd4DRtW00wp8dnPieM4i4Aw= Lockfile: the tag's own Cargo.lock, byte for byte (the old vendored lock was byte-identical to alpha.9's Cargo.lock, sha256 14ec0c17…). Image unverified until the host rebuild runs. Co-Authored-By: jjohare <github@thedreamlab.uk>
…with the server Owner decision: the bridge moves with lib/solid-pod-rs.nix so the two again compile one upstream snapshot, and both pin comments say so. Lock: `cargo update --workspace` from the alpha.9 lock, against the Nix layout reassembled (bridge at project/agentbox/services/, forum at fe36bf36, solid-pod-rs at d64131b). Exactly three lines move: the solid-pod-rs and solid-pod-rs-nostr path packages 0.5.0-alpha.9 -> 0.5.0-alpha.12 and the dependency reference to them. No registry crate changes. `cargo check --locked --all-targets` passes. `cargo test --locked --no-fail-fast`: 209 passed, 0 failed. tests/fixtures/blocktrail-s3/emit.rs (TxInfo literals; alpha.12 changes TxInfo.vin) is not a cargo target and is not compiled. Hash method (NAR of the GitHub archive tree, as fetchFromGitHub), proved on the existing pins: forum fe36bf36 sha256-9HooIa4vyu0Iw47VPr7RkMDyKrEazcElR2xPIe0njvE= (= forumHash, unchanged) solid 1d9da527 (a9) sha256-0/iDL8E9J5SGFnnJQwR3wP/qAjl9AHiKyKxU1U6qRfc= (= old solidHash) solid d64131b3 (a12) sha256-nMqFCn/QKpl49nQ/voONbd4DRtW00wp8dnPieM4i4Aw= (= lib/solid-pod-rs.nix srcHash) Image unverified until the host rebuild runs. Co-Authored-By: jjohare <github@thedreamlab.uk>
… reads lib/nostr-pod-bridge.nix runs the bridge tests (doCheck = true) inside a reassembled source tree that carried only the egress-redaction fixture. tests/identity_port.rs::the_checked_in_acl_loads_and_grants_what_the_rehearsal_needs (added in a44ea41, custody W3, after the layout last changed in bce9061) reads ../../agentbox.toml and ../../config/custody/identity-port-acl.json, so the host rebuild would fail in checkPhase with ENOENT. Reproduced exactly in a layout without them (1 failed). With both copied in: 209 passed, 0 failed. Only the two files are copied, not config/custody, so unrelated custody edits do not invalidate the bridge. An agentbox.toml edit now does; that is the price of keeping the test that ties the ACL to the manifest. Co-Authored-By: jjohare <github@thedreamlab.uk>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CI vehicle for the owner-directed estate pin upgrade (lands on main by fast-forward once CI is green). Per-commit reasons and hash proofs are in each commit message. Follows #17 (ruflo 3.51.1, Claude Code 2.1.288, already merged).
Image unverified until the host rebuild.
🤖 Generated by Claude Code