Make the line numbers in the link labels match the anchors again
59 source links had a label whose line numbers no longer matched the anchor
that the previous commit moved. The label now takes the anchor's range. Only
the text between the square brackets of a link changed: the URLs are
byte-identical and everything outside the labels is unchanged.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
62db642
Move the source-link anchors from main 58d6b27 to 3e8faed
Main moved by three commits: the test counts (ecc3dfa), the removal of the
agent's blind signChallenge (9c38a44) and the 1.0.0-alpha.12 release (3e8faed).
59 line anchors on 16 pages moved: 37 into packages/sdk/src/agent.ts, 20 into
packages/sdk/README.md and 2 into docs/ai-frameworks.md.
Only the digits of an anchor changed. With every anchor replaced by #L, the old
and new text of each page is identical, and the line endings are unchanged.
Four ranges (eight anchors) have a first or last line that changed in the move:
two in agent.ts, whose last line, the return of the removed method, is now the
end of the stub that throws, and two in README.md, whose last line is the test
count paragraph reworded on 29 October. They keep pointing at the same part of
the file.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
dd2f5e8
Describe the three merged changes and bring the test counts to 29 October
Pull requests 103, 104 and 105 change what the pages say.
The oracle answers 202 with durable false for a flag, a resolve and a link when
the state file cannot be written, as it already did for an attestation, and
counts them in sigvara_oracle_writes_not_durable_total. The monitoring, API,
flag and deployment pages say so.
The renounce phase refuses a timelock with a delay under 48 hours, one the Safe
cannot propose to or cancel on, one that not everyone can execute on or that the
Safe or the deployer administers, a timelock address with no code, and a Safe
with a threshold under 2. Governance and Deployment Strategies list the errors
and what to do about each. The deploy script now records the block it starts at
as deployBlock, and the role replay starts there.
The attestation page says why one confirmation is enough on Arc, as Arc's
documentation states it, and why the scan keeps six. The pages that describe the
alpha.9 key leak say that a key that was ever logged or serialized should be
treated as exposed and rotated.
Test counts follow main 58d6b27: 698 contract tests (691 run without a fork
URL), 784 oracle and 197 SDK. The Home page names 58d6b27.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
f527b7d
Make the line numbers in the link labels match the anchors again
The label of a source link names the lines its anchor points at, and the
previous commit moved 359 anchors, so their labels said the old numbers. Each
label now takes the range of its anchor. The URLs are untouched, and nothing
outside the square brackets of a link changes.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
aafc27b
Move the source-link anchors from main ff0fa68 to 58d6b27
Three pull requests landed after the pages were last checked: the durable
answer for flag, resolve and link in the oracle, the timelock and Safe policy
in the handover script with the recorded deploy block, and the key-rotation
and finality notes in the docs. Only the digits of the line anchors change, so
that each link points at the lines it named before. 359 anchors on 36 pages
moved; 5 end on a paragraph whose wording changed and are approximate.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
d73500a
Say that the pages were last checked against main ff0fa68
The text and the source links now follow the same commit, and the line says the SDK pages describe
1.0.0-alpha.11.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
af48361
Say that the SDK pages describe 1.0.0-alpha.11 and that the audience is required
alpha.11 reached npm on 29 October 2026 from main ff0fa68, and its tarball hash matches a local
pack of that commit. verifySignature now requires the expected audience: a call without it throws,
and a v1 payload is always refused. The opening paragraph of each SDK page names the version it
describes and says what is new since alpha.10. The pages that treated the audience as optional
("if an expected audience is provided", "audience?") no longer do, in the text and in seven
diagrams (all 532 diagrams parse and the eight changed ones render). The SDK test count follows
the new tests: 197 in 13 files, 8 of which skip, measured with CI=1 on a clean copy of ff0fa68.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
f4978ef
Make the line numbers in the link labels match the anchors again
A label such as verifier.ts:124-183 names the lines its link points at. The anchors moved with the
previous commit, so 201 labels on 35 pages showed the old numbers; they now take the anchor's
range. 4,398 labels were already right. Only link text changed, and every URL is byte-identical.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
1197e7b
Move the line anchors from main 652beca to main ff0fa68
Pull requests 99, 100 and 101 and the two dependency bumps (83 and 84) changed lines in README.md,
the docs, deployments/5042002.json, the package files and packages/sdk/src/verifier.ts, so the
anchors below those edits drifted. Each anchor was mapped through the git diff between the two
commits: 201 anchors on 35 pages moved, none was dropped, and the one that spanned the audience
check in verifier.ts, which the release rewrote, now covers the new block. Nothing but the digits
of an anchor changed.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2ff9705
Say that the pages were last checked against main 652beca
The text and the source links now follow the same commit, and the line says which SDK version
the SDK pages describe.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
1a05f34
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>
42bc7e0
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>
65bd619
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>
3429949
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>
48263e7
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>
4424243
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>
fd2758b
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>
7208826
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>
4f3585f
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>
d7bfee6
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>
bce18fa
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>
46fba91
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>
a8ac534
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>
f155837
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>
809bbc9
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>
14593b6
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>
558d43a
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>
85d5bf6
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>
421eab4
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>
5e9456f
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>
5311c33