Repository navigation
Conversation
Give --snapshot.version a distinct clap argument ID so it does not collide with the built-in --version flag. Add a command-definition regression test.
Keeps working notes and machine-specific agent instructions out of the published fork: .dev.local/, /tmp/, and any *.local.md override files.
Four-layer scaffold (user, functional, architecture, contributor) with layer indexes, a root router, and CONTRIBUTING.md as the contributor layer's public landing page. The architecture layer carries a decision-record router from the outset, per the standard, rather than deferring it until decisions accumulate. DD-0001 records the reasoning behind the indexer task-dependency and rollback cache-recovery fix, which until now existed only as a pull request body. Contributor content is split by concern: branching, versioning, commit conventions and testing, rather than one undifferentiated policy file. Conforms to the Agent-Ready Documentation Standard v1.0 at Level 1 (Bootstrapped), partially and with one declared deviation: our discovery entry point is upstream's AGENTS.md, where we keep to a single pointer line, so the bootstrap contract is satisfied by delegation rather than directly. Also documents the test-fixture requirement that otherwise makes most of the torii-indexer suite fail in a way that resembles a code fault.
Routes agents to the fork's purpose and scope, the contributor-layer policy artefacts, the documentation map, and decision-record conventions. Routing only — policy detail lives in the contributor layer rather than being duplicated here. Reached from AGENTS.md via a single pointer line, keeping our footprint in upstream's files to one line.
Derive the fork version from the reachable uw-v tag and the upstream base from upstream/main at build time. Use the resulting specification consistently for the Torii CLI and runtime metadata.
Build only uw-v tags that point at the current fork main commit. Name release artifacts from the Underware tag and validate the binary version before cross-platform bundling.
Keep branch promotion outside the release command. Validate local main against origin/main, build the tagged binary locally, and push only the immutable Underware release tag.
feat: harden indexing recovery and Underware releases
- /static/{contract_address}/metadata
- /static/{contract_address}/{token_id}/metadata
feat: static /metadata routes
windows-latest no longer exposes the Visual Studio generator to the cmake crate, so the aws-lc-sys build script panics and, with fail-fast on, cancels every other platform. Run vcvars via ilammy/msvc-dev-cmd before building and disable fail-fast so one platform cannot take the release down. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01R8RxNfmJUqdatNdRt87gRY
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.