chore(release): bump version set to 10.0.11

[Jurij89]

Summary

Release-prep bump for 10.0.11, per RELEASE_PROCESS.md §3. Moves the root package and all 20 packages/* workspaces to 10.0.11 in lockstep and adds the CHANGELOG.md entry.

Last gate before the comprehensive devnet run (§4) and the signed tag (§5). No functional changes — all 10.0.11 code landed via #1999.

Changes

• Version set → 10.0.11 (21 package.json files: root + 20 workspaces, including the two private ones so the publish graph stays aligned). Internal deps use workspace:*, so a partial bump would ship a skewed dependency graph.
• CHANGELOG.md: new ## [10.0.11] section with an ### Upgrading from 10.0.10 matrix. [Unreleased] was empty and stays empty.

Version-only: pnpm-lock.yaml is untouched, so pnpm install --frozen-lockfile stays valid. The engines.node ranges added in 10.0.10 on packages/cli and packages/agent are preserved unchanged.

Why an upgrade matrix this time

§10 requires upgrade guidance for a breaking or builder-impacting release. 10.0.11 changes the default admission behaviour and error contract of a public HTTP API, so the matrix fires. Each claim was verified in the shipped code rather than taken from PR descriptions:

• POST /api/query now defaults to the background store lane — packages/cli/src/daemon/api-query-priority.ts:8,12, fail-safe on invalid input. Reversible with DKG_API_QUERY_PRIORITY=normal (daemon/lifecycle.ts:1175, documented packages/cli/README.md:60).
• Under stock tuning that lowers API-read concurrency from 2 to 1 — store-priority-scheduler.ts:97-100,177-181: MAX_CONCURRENT=4 less ACK=1 and HEALTH=1 gives totalLimit=2, normalFloor=1, backgroundLimit=max(1, 2−1)=1. This is the row operators most need to see.
• A shed query now answers 503 + Retry-After: 1 where it previously fell through to a generic 500, with code: "STORE_SCHEDULER_BUSY" and retryable: true in the body.
• Dashboard successRate becomes success / (success + error), and dkg integration install <manual-entry> now exits 0 with a docs hand-off instead of 1.

Reviewer notes

• fix(integrations): conform the CLI to the published registry schema #1988 is a loosening, not a tightening. The CLI validator had drifted stricter than the registry's published JSON Schema — manual required a steps array the schema forbids, mcp required the schema-optional args, service rejected the schema's binary runtime — so no manual entry parsed at all, in either the CLI or the dashboard sidebar. The public registry cannot serve a shape this release newly rejects. Only a private/staging registry reached via DKG_REGISTRY_RAW_BASE can, hence that caveat in the matrix row.
• The graph-scope elision touches the ACL rewrite path — packages/query/src/sparql-graph-scope.ts:100-108 and its call site packages/query/src/dkg-query-engine.ts:1613. It is narrow and fail-closed (tuple VALUES, variables, literals, UNDEF, nested groups, unresolvable prefixes, or any out-of-scope graph all keep the intersection rewrite) and result sets are unchanged because a subset intersected with the allow-list is that same subset. Worth one deliberate read regardless, since graph-scoping is the ACL.
• CHANGELOG length — ~8.7k characters, comparable to 10.0.10's 8.6k despite a far smaller payload. The upgrade matrix accounts for roughly 2.5k of that; the bullets are proportionate.
• No contract deployment needed — git diff --name-only v10.0.10..origin/main -- '*.sol' 'packages/evm-module/abi/*' 'packages/evm-module/deployments/*' is empty. Dashboard SQLite stays at SCHEMA_VERSION 31, so no migration and no rollback question.

Test Plan

• pnpm release:verify-versions --version 10.0.11 → passes, 21/21
• Version-only diff: 21 insertions / 21 deletions across package.json files
• pnpm-lock.yaml untouched
• engines.node preserved on both publishable runtime packages
• CI green
• Comprehensive devnet gate on the resulting main commit (§4) — next gate, after merge

Related

• All 10.0.11 code landed via release: promote testnet-canary to main for 10.0.11 #1999 (testnet-canary → main, PRs fix: prevent scoped API queries from starving store work #1991, fix: address query scheduler follow-up review feedback #1994, fix(integrations): conform the CLI to the published registry schema #1988)
• mainnet: rs.loop.tick-threw from Store scheduler queue wait timeout in blazegraph.query #1989 remains open — this release fixes the query-amplification cascade but does not claim the separate mainnet Blazegraph atomic-replace failures
• Enforce the node:sqlite runtime floor at startup and before slot activation #1985 (node:sqlite runtime-floor enforcement) remains open and is not in this release

🤖 Generated with Claude Code

[otReviewAgent]

Review Agent completed this review and found no issues.