History

Drop the unreleased marks from the SDK pages alpha.10 is on npm, so the marks that called its changes unreleased come off 14 pages (112 edits). Where a mark carried a contrast with alpha.9, the contrast stays without the word unreleased ("alpha.9 has only signChallenge"). Where a sentence said "on main" only to set a behaviour apart from the npm release, those words go. The not_active lists read as they did before the marks went in: unbonded (or bonded below the minimum stake in force now), suspended, or slashed. The two notes on the future-date refusal now say that alpha.9 still accepts a payload dated ahead. All 532 Mermaid blocks still parse, and the three that changed render. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 28, 2026

Say that the SDK pages describe 1.0.0-alpha.10, now on npm The opening paragraph of each SDK page said that npm had 1.0.0-alpha.9, that the items under Unreleased in the changelog were not in it, and that the pages marked them. alpha.10 reached npm on 28 October 2026 from main 652beca, and its tarball hash matches a local pack of that commit. The paragraphs now say which version the page describes and list what is new since alpha.9. The version in the package.json diagram and the versioning note on the code quality page follow. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 28, 2026

Move the line anchors from main 457fa9e to main 652beca The release pull request for the SDK (97) added a line to packages/sdk/README.md and took one from each of docs/quickstart.md and docs/ai-frameworks.md, so the anchors below those edits drifted. Each anchor was mapped through the git diff between the two commits: 22 anchors on 9 pages moved, none was dropped. Nothing but the digits of an anchor changed. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 28, 2026

Say that the pages were last checked against main 457fa9e The text and the source links now follow the same commit. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 28, 2026

Stop describing the testnet as running the September contracts Five statements still said the Arc testnet committee resolves disputes with no veto or lapse, that its reputation proxy reads the live window when finalizing, or that it is a proxy from before finalizableAt existed. The testnet has run the contracts as of fdce1a7 since 26 October 2026. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 28, 2026

Cover what the first pass left out A read-only review of the pages against the code turned up pages that still described the old behaviour or lacked the new: - the primary replaces a stranded proposal from its finalizableAt, not from proposedAt plus the window in force now - /attest answers 202 on the payment page, the operations troubleshooting list and the service page - check-role-holders.mjs runs before the renounce as well, and the registries are required in the four phases that read them (deploy-timelock only creates the timelock) - the AI framework diagrams read the bond with the status, and the bond check is marked unreleased wherever a page mentions it - maxScoreAgeSeconds is among the values the constructor refuses - the summaries of the dispute lifecycle say an uphold is refused once the dispute can be expired Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 28, 2026

Describe the bound on upholding a dispute and say what the testnet runs On main an uphold is refused with DisputeResolutionExpired once the dispute can be expired, so the admin's ruling and the expiry never overlap. ADR 0005's note on re-filing is added to the slashing and unbonding pages. The Arc testnet proxies run the contracts as of fdce1a7, so they take the bound at their next upgrade. Every page that said they run the contracts on main now says so with that exception. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 28, 2026

Describe the 202 answer of /attest, the proposal's own deadline and the handover checks /attest answers 202 with durable: false while the oracle cannot write its state file, and the metric accepted_not_durable counts it. The oracle and the watcher decide when a proposal can be finalized from the contract's stored finalizableAt, and judge a proposal that predates the field against the live window, as the contract does. SplitAuthority needs the four launch registries in every phase, and check-role-holders.mjs runs with BEFORE_RENOUNCE=1 before the last phase and again after it. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 28, 2026

Update the test counts to main 457fa9e Measured on a clean copy of main: 697 contract tests (690 run without a fork URL and 7 skip) in 30 files with 19 invariants, 781 oracle tests, and 189 SDK tests in 13 files, 8 of which skip without a live deployment. The pages said 693, 760 and 168. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 28, 2026

Say what the SDK gate checks now The gate also reads the bond held now (hasMinimumStake) and refuses an agent below the minimum stake in force as not_active, and an optional maxScoreAgeSeconds refuses a score written longer ago than that, or never, as stale_score. verifier.getScoreUpdatedAt is the read behind it. All of it is unreleased: npm has 1.0.0-alpha.9. The pages that said the gate does not check the bond now say it does. The reason lists, the flow diagrams, the configuration table and the unreleased lists gain the new refusal and option, and the testing page covers the test of the compiled package for the agent's secret key. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 28, 2026

Say that the testnet oracles run 457fa9e The primary and the checker were re-pinned from fdce1a7 to 457fa9e on the evening of 27 October 2026 and report 457fa9e in /health. The sentence said fdce1a7. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 28, 2026

Say which commit the source links on the home page follow The anchors moved to main 457fa9e in the commits above. The line about the last check still names the commit the text was audited against, 638650f, and now adds the one the links follow. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 28, 2026

Make each source link's label show the lines its anchor points at The previous commit moved 911 anchors, so the line numbers printed in their labels were out of date. Each label now takes the numbers of its anchor. The 3,688 that were already right and every URL are untouched; the links, their order and all text outside the labels are byte-identical. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 28, 2026

Move the line anchors from main 638650f to main 457fa9e Pull requests 91 to 95 changed lines in SigvaraStaking.sol, the oracle, the SDK and their README files, so the floating blob/main links drifted. Each anchor was mapped through the git diff between the two commits: 911 anchors on 58 pages moved, 8 that spanned an edited block now cover the whole block, none was dropped. Nothing but the digits of an anchor changed. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 28, 2026

Point the home page at main 638650f Main now holds the 26 October documentation, the site pull request and two changes the wiki does not link to (a test-harness fix and an SDK lockfile bump). The source links were checked against a fresh export of that commit: 5,761 links, 4,599 anchors and 80 internal links, 0 problems. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 27, 2026

Make each source link's label show the lines its anchor points at A label such as verifier.ts:15-209 was written from the tree the wiki was generated from, and its anchor was moved later, so the two disagreed. 576 labels now take the range of their anchor; 4,023 already did. Only the text inside the square brackets changes, and the URLs are byte-identical. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 27, 2026

Move the line anchors to the pull requests that carry the 26 October documentation Source links point at blob/main, so they drift as main moves. They were taken from 27d03c4. Each anchor is mapped through the diff to the combined tree of the documentation and site pull requests; 1,182 anchors moved exactly, 3,405 files did not change, and 12 moved in blocks that were rewritten (the slash drill fork tests among them) and were read by hand. Links only: 1,175 exact moves were compared by their first and last line and none differed. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 27, 2026

Say that the testnet proxies run the contracts on main since 26 October 2026 The four Arc testnet proxies were upgraded in place on 26 October 2026, so about 30 pages that said the testnet still runs the 21 September implementations, "(main only)", or "the testnet predates this" were wrong. - The page header notes say the testnet has run the contracts on main since the upgrade and keep the one thing an upgrade cannot change: role administrators are written when a proxy is initialised, so the testnet's admin still grants the slasher, committee and staking-core roles and the timelocked grants do not apply there. - The "(main only)" markers on the guardian pause, the admin ruling, the veto and the lapse are gone. - The signer registry is live on the testnet, but neither operator has named a signer. - The two proposals pending at the upgrade have finalized, and a proposal made before the upgrade reads zero in the two new PendingScore fields. - The VPS deployments fetch one pinned commit, not main; both testnet oracles run fdce1a7. - Test counts match the README (693 contract tests, 686 run, 19 invariants in five campaigns, 760 oracle tests, 168 SDK tests); seven pages still carried the 22 October numbers. - The slash drill is described with testnet faucet tokens. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 27, 2026

Point the home page at main 2da02b7 Main now carries the README and docs changes the wiki's line links were mapped to, so the links and the code they cite agree. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 23, 2026

Record the new test counts and say what the testnet proxies do not run yet The contract suite is now 693 tests in 30 files, 686 of which run without a fork URL. The staking and security pages' notices about the September implementations now include the reporter check at slash execution, the fixed claim time of a queued withdrawal and the refusal of rejected evidence, and two sentences say that revoking a committee member stops what it had filed from being executed. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 23, 2026

Make each source link's label show the lines its anchor points at Follows the anchor move to main 27d03c4. A label such as SigvaraStaking.sol:441-488 has to say the lines its link points at, so the 587 whose anchor moved are updated to match. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 23, 2026

Move the line anchors to main 27d03c4 The staking contract gained about 100 lines across PRs 72 to 74, and the README and four docs changed, so the wiki's links into them moved. Each anchor is mapped through the git diff from the tree the wiki was last pinned to (1e5d833). 665 moved exactly (the first and last line of each still match), 15 moved approximately because the cited lines were edited (six distinct ranges, each read by hand), none was dropped. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 23, 2026

Describe the three staking changes that merged in PRs 72 to 74 executeSlash now requires the reporter to still hold the committee role, a withdrawal's claim time is fixed when it is queued, and evidence the admin rejected is refused for that agent. The slashing lifecycle, staking contract, stake management, unbonding, contract reference, FAQ, economic and security pages say so, the testing page lists the three new test files, and the lifecycle page's demo note says what the site demo does not model. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 23, 2026

Bring the wiki in line with main 1e5d833 and fix two diagrams An oversize request body is answered 413 now, and the API Reference said the oracle drops the connection. The test counts and invariant suites moved: 665 contract tests, 19 invariants in five suites, 760 oracle tests, and CI typechecks the SDK's tests. The Home page names the commit it was checked against. Key Management and Rotation: a subgraph and one of its nodes were both called Tests, which current Mermaid refuses to render ('Setting Tests as parent of Tests would create a cycle'). The node is IdentityTests now. SDK Overview and Setup: a node and a subgraph were both called Contracts, so the node's label was lost. The edge points at the subgraph, which carries the label. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 23, 2026

Make each source link's label show the lines its anchor points at A label such as verifier.ts:15-209 was written from the tree the wiki was generated from, and the anchor behind it was moved to main later, so the two disagreed on 3,871 links. With an anchor, the label now takes the anchor's range (the wiki writes 'to the end of the file' as one past the last line, so the label is clamped to the file). A label with numbers and no anchor linked the whole file and claimed a range nothing backed, so 414 of those lose their numbers. Link targets are untouched. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 23, 2026

Move the line anchors to main 1e5d833 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 23, 2026

Move the README line links after the README change The README gained a line near the top when it was updated to say the wiki was republished, which put 161 links to README lines in 23 pages one line off. They now point at main at 6b4c6ee. No page text changed. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 23, 2026

Bring the wiki in line with the code on main Rewrote the prose of 74 of the 75 pages against main at d8e44c2, and marked what the Arc testnet proxies, which still run the September 2026 implementations, do differently. Each page was read again against the code by an independent reviewer, and every finding was checked before it was applied. Notable corrections: the admin, not the committee, rules on disputes and an upheld ruling waits for the challenge deadline; a slash nobody executes can be lapsed by anyone 14 days after its deadline; the outcome in an evidence leaf is not on chain; meetsThreshold ignores status and bond; the archived SVR sale and vesting contracts are not the mainnet design; SDK changes after alpha.9 are marked as unreleased. Also fixed four Mermaid diagrams that did not parse. All 532 diagrams now parse, and every source link resolves against main. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 23, 2026

Fix dead source links and move line anchors to main 1,755 source links carried a stray Sigvara-main/ path segment and returned 404; the segment is removed. Two links were malformed by hand (a space inside packages/sdk, a stray character inside test/E2E.t.sol) and are repaired. The line anchors were taken from the tree the wiki was generated from (main at f852051, 2 October 2026). Each one is now mapped to the current main through the git diff: 3,788 land on the same code they started on, 312 sit on code that changed and are approximate, 413 pointed at code that no longer exists and become plain file links, and 488 are in files that did not change. No prose is changed in this commit. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

RunTimeAdmin committed Oct 23, 2026

Publish the repository wiki, edited for a reader rather than a generator 73 pages generated from the source tree at f852051, plus a landing page and a sidebar. Three changes were needed before any of it was fit to publish. 5,591 citation links pointed at `file://` paths, which resolve to nothing on a wiki. Repointed at the repository, line ranges intact, so every claim on a generated page can be checked against the code it came from. That turns the densest thing about these pages into the most useful. 124 placeholder lines reading "[No sources needed since this section provides general guidance]" are generator scaffolding and are gone. One claim was misleading rather than wrong: System Overview said payment scanning is off by default, which is true of the shipped default and not of this deployment, where it has been on since 3 October. Now says both. Flattened from nine nested sections into page names, since wiki pages are addressed by name. No collisions, and the generator never cross-linked pages, so nothing broke: 75 pages, zero broken internal links. The landing page is written rather than generated. It leads with what the protocol is, the six factors and their caps, what has actually been proven on a live deployment, and what has not — no audit, admin rights still on a deployer EOA, both operators run by the same party. It also says these pages are derived and that the code and `docs/` win where they disagree, because a generated wiki drifts and readers should know which half to trust. The `.qoder/repowiki/knowledge` tree is deliberately not published: ten pages of tool-internal notes carrying `kind:` and `scope:` frontmatter and source paths prefixed `Sigvara-main/`, written for a machine rather than a reader.

RunTimeAdmin committed Oct 7, 2026