Make the line numbers in the link labels match the anchors again
Labels that named the line numbers of main 700a3ee now name their link's anchor. URLs are untouched, and the link checker finds every source link and anchor inside main b6baabd.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Move the source-link anchors from main 700a3ee to b6baabd
Main moved by four merges: the testnet state and counts in the README and whitepaper (#153), the MCP trust server (#154), evidence verification (#155) and the SDK release 1.0.0-alpha.15 (#156).
Only the digits of line anchors change in this commit. Each was mapped through the git diff between the two commits and checked for the same first and last line of text (535 compared, 0 mismatching). Three ranges moved approximately: two README ranges whose last line is the reworded counts line, and packages/sdk/src/index.ts, which grew.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Make the line numbers in the link labels match the anchors again
1,670 labels on 71 pages named the line numbers of main 17cccb8; each now names its link's anchor. URLs are untouched (5,656 links compared, 0 problems), and the link checker finds every one of 5,770 source links and 4,599 anchors inside main 700a3ee.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Move the source-link anchors from main 17cccb8 to 700a3ee
Main moved by 40 merges (#112 to #152): payer-signed outcomes (ADR 0006), SDK 1.0.0-alpha.13 and alpha.14, the gate's production profile, the operations runbook and state backups, the handover Safe checks, the slash split without a committee share, the explorer, the testnet simulation, verifiable builds, the authorisation matrix and the oracle bond's fixed exit time.
Only the digits of line anchors change in this commit: 1,670 anchors on 71 pages. Each was mapped through the git diff between the two commits and checked for the same first and last line of text (2,071 compared, 0 mismatching). Twelve ranges moved approximately because a line at their edge was edited: the slash event and its test, two README ranges ending on the reworded counts line, measuredFactorsFor in oracle/index.js, the gate's opening comment, and ranges in docs/arc.md, docs/counteraudit-integration.md, docs/payment-backed-attestations.md and oracle/README.md.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Describe 1.0.0-alpha.12 and bring the SDK test count to 201
The agent's blind signChallenge is gone in 1.0.0-alpha.12 (pull request 107,
released by 108). A call does not compile in TypeScript, and in JavaScript it
throws an error that names signChallengeFor.
The pages that describe the SDK now say 1.0.0-alpha.12 and list the removal as
new since alpha.11. Where a page said that signChallenge signs whatever it is
handed, it now says that the method is removed and that alpha.9 has only it.
The exported function signChallenge(payload, secretKey) is unchanged and stays
where a page shows it. The class diagrams drop the method, and the sequence
diagrams and the flowchart that showed an agent calling it show
signChallengeFor(payload, audience) instead. The Home page names main 3e8faed.
The SDK suite is 201 tests, not 197: 193 run and 8 skip without a live
deployment, in 13 files, measured with CI=1 on a clean export of main 3e8faed.
Six pages carried the old number.
62 replacements on 24 pages. 20 diagrams changed; all 532 still parse and the
20 render without an error or a clipped label.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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.