srstack v0.2.0
Research and inspection, without the planner
srstack v0.2.0 is the independent, read-only Standard Reserve skill focused on source-grounded research and bounded public inspection. It publishes the exact reviewed candidate commit and runtime ZIP; no post-review usability redesign is included.
What changes
- Two routes: research and inspect. The pre-release strategy simulator, assumption-intake workflow,
scripts/scenario.py, fictional fixture and verifier--offlineflag are removed. Future-return requests receive qualitative research, not a replacement simulator. - Compact charter reads. A normal charter snapshot contains the requested owner, branches, pending balance and supported current-rate equivalent.
--detail fullopts into broader context and raw evidence. Current-rate equivalents are not promised earnings. - Expanded fixed inspection. Auction controllers/pending ownership, CentralBank queued policy/recycling, FeeSplitter current/queued allocations and team ETH liability, and vault controls are supported.
snapshot.py treasury --asset ADDRESSchecks same-block reserve approval before selected-asset holdings/pool reads. Unknown token/internal-ledger scales remain explicitly raw; queued settings do not replace current policy. - Bounded auction and buyback history.
history.py license,charterandbuybacksuse finite ranges and request/log/byte/time budgets. The default lookback is one million blocks, not a promised time interval. Empty checked windows are not all-time absence. Buyback totals are event-accounted, not independently reconciled transfers or aggregate protocol burns. - Better operational boundaries. Original bounded HTTP-denial diagnostics, clean replacement/rollback, and an external full-commit installation record improve troubleshooting without retries around denial or host-permission bypasses.
- Second Mandate research, not invented deployments. Announced strategy and sample positions remain distinct from observed holdings, deployed functionality and holder revenue rights.
Install or update
Use srstack-0.2.0.zip and verify its entry in SHA256SUMS. Only that complete runtime belongs in the skill directory; do not install the audit ZIP or GitHub's automatically generated source archive. Cleanly replace older versions rather than overlaying files, since the planner was removed.
The tagged README installation workflow describes staging, integrity verification, retained backups and rollback. Its reviewed-commit workflow can be used with this exact full commit:
660bdd315688e3962c40e65839764fcf5f6fa766
Frozen wording: the approved package still describes itself as an unpublished/candidate snapshot and includes the candidate branch installation example. That describes its prepublication review state; this GitHub release and annotated tag establish publication. No runtime bytes were changed merely to remove that wording. Pin the full commit above, not the moving branch or version string. Start a fresh host conversation after loading; replacing the files does not reset other chats.
Release checkout: the merged feature/v0.2.0 branch is retired. In README installation step 1, replace both occurrences of feature/v0.2.0 (the git clone --branch and git fetch origin arguments) with v0.2.0. Leave the remaining commands unchanged and confirm the resolved full commit matches the pin above. The permanent release tag and attached runtime ZIP remain available.
Default python3 -B -I scripts/verify.py is offline integrity verification. There is no --offline flag. Live helpers still require normal host execution/network permission. Integrity is not authenticity or sandbox certification.
Verification and limits
Release commit: 660bdd3. Runtime: 43 files, 16 source records, 115 parameter records and 14 publisher-listed identities. The fixed interface has 128 calls, nine getter roles and eleven authentication roles; this is not a complete contract audit.
- CI: 146 regressions passed per job on Python 3.10 and 3.14. Reviewed-commit run.
- Installer: six success/replacement/rollback/rejection cases passed using the actual installation instructions.
- Live smoke: protocol/auction/treasury reads and approval-based withholding were exercised. A million-block buyback scan completed all 100 windows and observed four events. That scan preceded the final one-line auction final-anchor error-flag fix; the exact committed export separately exercised treasury, license history and buyback history. Approved reserve-asset positive decoding was covered deterministically, not established by a live approved-asset smoke.
- Independent adversarial review: runtime/ABI/accounting and package/execution/documentation reviews completed. An auction completeness flag and build/install path-bound mismatch were reproduced and fixed with regressions. Conservative transitive authentication was retained and documented.
- Exact bytes: the committed export, final scanned runtime and runtime ZIP members match byte-for-byte.
Scanner results — findings retained
Cisco Skill Scanner 2.1.0, strict static/behavioral: 1 critical and 4 medium findings. This is not a clean scanner verdict. The critical flags exec(compile(...)) used to load the literal, descriptor-checked local snapshot.py sibling. Review found no caller/network-controlled executable input under the documented trusted-runtime preflight; the design was not disguised or weakened to silence the scanner. The medium findings cover two intentional fixed network clients, reference nesting and a declaration-channel conflict: Cisco expects optional compatibility frontmatter, while the pinned OpenClaw packager rejects it. Python/network requirements remain explicit in the integrity-bound skill body. Full findings and dispositions are attached.
Gitleaks 8.30.1 found no secrets in the final runtime directory. AgentSkills validation passed. Hermes normal guard allowed the temporary installation, and all 43 loaded resources matched. OpenClaw eligibility, official validation and local packaging passed; packaged members matched the runtime. Local ClawHub static moderation was clean; this is not hosted registry approval. Release evidence/assets receive a separate secret scan before upload.
Scans used pinned tooling, isolated temporary state and an offline sandbox. No findings were suppressed. These checks do not certify model-driven host behavior, smart-contract security, historical completeness, solvency or future returns. Trusted package/interpreter integrity and host approval enforcement remain external prerequisites.
Release assets
- srstack-0.2.0.zip — complete installable runtime.
- srstack-audit-0.2.0.zip — separate sanitized review, scanner, toolchain and verification evidence; not installable. Historical prepublication reports retain their original status labels; the publication record distinguishes the approved release.
- SHA256SUMS — hashes of both ZIP assets.
Runtime content SHA-256: 673265f5b78c36b695aa2715ccb20bd7e78f5125fcdf9ebe2c8578a526f9ea40.
Prior releases and their assets remain unchanged. No registry submission or hosted scanner upload accompanies this GitHub release.