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>
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>
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>
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>
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>
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.