Ashlrverse 3.22 — faster resources and execution evidence

Ashlrverse 3.22 makes connected resources available sooner and brings account usage, credit pools and execution evidence into the same workbench.

• Show dated, account-bound historical usage while independent refreshes complete.
• Track fresh Codex wallet availability separately from spent subscription windows, with an explicitly estimated dollar reference.
• Collapse projects and chat groups independently; use the official Devin mark in Resources.
• Inspect attempt timelines, verification, diffs, canonical PR links and recorded outcomes.
• Route useful work using observed durations and qualified subscription reset deadlines. Purchased credits do not receive subscription reset priority.
• Choose explicit uncapped preferences, retain larger account rosters, and use the refreshed two-mode website demo and operator guides.

Verified source: 1de703fa661e8f8a4a110e879bff036e0646cc8f. Release commit: fc1dcd993b95f9ac8eb0b0f25266ffb627b9aaca; both have tree 80ae86d4393f51ff385a371ef5a6a4485494e934.

Validation: 38,936 tests across 1,817 distinct files; all 12 backend stages and web passed, with 133 declared backend skips and two campaign-filter skipped executions recorded separately. Ten hosted CI jobs and dependency audit passed. All four native build phases passed; independent mounted verification matched 702 resources and the signed app. All 10,388 npm archive files matched frozen disk bytes. Clean consumers passed 30 CLI checks, 15 packaged guides, and Hub/Plugin coexistence with three commands and 40 MCP tools.

The attached 150-account benchmark is a single-run synthetic local fixture. All historical readings appeared before refresh completed; cache load was 4.206 ms and initial snapshot 1.984 ms. HTTP uses an injected deferred synthetic worker result; these timings do not measure live providers or the full disk worker and have no baseline or speedup claim.

The Mac image uses the existing Ashlr Local certificate and is not Developer ID notarized. Installation, physical-phone acceptance, account connections, signed resident authority and credit-spending activation remain separate from publication. SHA256SUMS covers the three main payloads; the optional benchmark JSON has its own independently verified digest.