feat(info): display commit-snapshot provenance (P1) - #114
Conversation
VersionEntry gains an optional provenance field parsed from the
registry index. numan info shows a note when a version's provenance
is "commit-snapshot" ("built from a commit snapshot, not a tagged
release"). Other fixture-only VersionEntry literals across
tests/cmd updated for the new field.
Ref: docs/plans/2026-08-09-intake-process-reform.md (P1)
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
🔗 Linked repositories identifiedCodeRabbit considers these linked repositories for cross-repo context during reviews:
📜 Recent review details🧰 Additional context used📓 Path-based instructions (9)**/*📄 CodeRabbit inference engine (CLAUDE.md)
Files:
**/*.{js,jsx,ts,tsx,py,java,go,rs,rb,php,c,cpp,h,hpp,cs,swift,kt,kts}📄 CodeRabbit inference engine (CLAUDE.md)
Files:
!**/.env,!**/credentials.json,!**/*.pem📄 CodeRabbit inference engine (CLAUDE.md)
Files:
**/*.rs📄 CodeRabbit inference engine (CONTRIBUTING.md)
Files:
**/*.{rs,toml}📄 CodeRabbit inference engine (CONTRIBUTING.md)
Files:
**/*.{rs,nu}📄 CodeRabbit inference engine (CONTRIBUTING.md)
Files:
**/*.{rs,md}📄 CodeRabbit inference engine (CONTRIBUTING.md)
Files:
**/*.{rs,md,toml}📄 CodeRabbit inference engine (CONTRIBUTING.md)
Files:
src/cmd/**/*.rs📄 CodeRabbit inference engine (AGENTS.md)
Files:
🔍 Remote MCP DeepWiki, GitHub CopilotRelevant review context
🔇 Additional comments (8)
📝 WalkthroughWalkthroughChangesVersion provenance metadata
CLI help and completion updates
Estimated code review effort: 2 (Simple) | ~15 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 7 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (7 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
✨ Simplify code
Warning Review ran into problems🔥 ProblemsLinked repositories: Public OSS repositories can only analyze public repositories installed in this organization. Analyzed Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/cmd/info.rs`:
- Around line 203-220: Add a test alongside
format_info_omits_provenance_note_when_absent that sets
sample_plugin(false).versions[0].provenance to an unrecognized value such as
"future-marker", calls format_info, and asserts the commit-snapshot note is
absent, preserving the existing special handling for "commit-snapshot".
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: bb25698a-5681-4ff8-8e04-ef72b1253087
📒 Files selected for processing (8)
src/cmd/info.rssrc/cmd/search.rssrc/cmd/try_cmd.rssrc/core/package.rssrc/core/registry.rssrc/core/resolve.rstests/install_test.rstests/support/active_update/mod.rs
🔗 Linked repositories identified
CodeRabbit considers these linked repositories for cross-repo context during reviews:
tonythethompson/QuickShell(manual)tonythethompson/numan(manual)tonythethompson/dependency-chain-substrate(manual)
📜 Review details
⏰ Context from checks skipped due to timeout. (2)
- GitHub Check: Real-Nu acceptance (windows-latest)
- GitHub Check: Test (windows-latest)
⚠️ CI failures not shown inline (2)
GitHub Actions: Trigger Kiro Crew / trigger _ trigger-agent: feat(info): display commit-snapshot provenance (P1)
Conclusion: failure
##[group]Run set -euo pipefail
�[36;1mset -euo pipefail�[0m
�[36;1m: "${***REDACTED_SECRET_ASSIGNMENT*** missing}"�[0m
�[36;1m: "${***REDACTED_SECRET_ASSIGNMENT*** missing}"�[0m
�[36;1m: "${GATEWAY_URL:?KIRO_GATEWAY_URL missing}"�[0m
�[36;1m�[0m
�[36;1mif [ -n "${GATEWAY_ORIGIN:-}" ]; then�[0m
�[36;1m ORIGIN="$GATEWAY_ORIGIN"�[0m
�[36;1melse�[0m
�[36;1m ORIGIN=$(printf '%s' "$GATEWAY_URL" | sed -E 's#(https?://[^/]+).*#\1#')�[0m
�[36;1mfi�[0m
�[36;1mREPO_SHORT="${REPO##*/}"�[0m
�[36;1mSESSION_KEY="hook:github:${REPO_SHORT}:${EVENT}:${RUN_ID}"�[0m
�[36;1m�[0m
�[36;1mONE_OFF=""�[0m
�[36;1mif [ -n "${ONE_OFF_RAW// }" ]; then�[0m
�[36;1m ONE_OFF=$(printf '%s' "$ONE_OFF_RAW" | sed -E 's|^[[:space:]]*/[Kk][Ii][Rr][Oo][Cc][Rr][Ee][Ww][[:space:]]*||')�[0m
�[36;1m ONE_OFF=$(printf '%s' "$ONE_OFF" | sed -E 's|/kirocrew||Ig' | sed -E 's/^[[:space:]]+//;s/[[:space:]]+$//')�[0m
�[36;1mfi�[0m
�[36;1m�[0m
�[36;1mif [ -n "${PR_NUMBER}" ]; then�[0m
�[36;1m COMMENT_TARGET="Leave a single GitHub PR comment on ${REPO}#${PR_NUMBER} (gh pr comment ${PR_NUMBER})."�[0m
�[36;1m PR_LABEL="PR #${PR_NUMBER}"�[0m
�[36;1melse�[0m
�[36;1m COMMENT_TARGET="If an open PR contains commit ${SHA}, comment on that PR; otherwise leave a commit comment on ${SHA}."�[0m
�[36;1m PR_LABEL=""�[0m
�[36;1mfi�[0m
�[36;1m�[0m
�[36;1mMSG=$(jq -nr \�[0m
�[36;1m --arg prefix "$MESSAGE_PREFIX" \�[0m
�[36;1m --arg event "$EVENT" \�[0m
�[36;1m --arg repo "$REPO" \�[0m
�[36;1m --arg ref "$REF" \�[0m
�[36;1m --arg sha "$SHA" \�[0m
�[36;1m --arg run_id "$RUN_ID" \�[0m
�[36;1m --arg run_url "$RUN_URL" \�[0m
�[36;1m --arg pr_number "$PR_NUMBER" \�[0m
�[36;1m --arg pr_label "$PR_LABEL" \�[0m
�[36;1m --arg daytona "$DAYTONA_OS" \�[0m
�[36;1m --arg one_off "$ONE_OFF" \�[0m
�[36;1m --arg comment_url "$COMMENT_URL" \�[0m
�[36;1m --arg comment_target "$COMMENT_TARGET" \�[0m
�[36;1m '�[0m
�[36;1m def nl: "\n";�[0m
�[36;1m (if ($prefix | length) > 0 then $prefix ...
GitHub Actions: Trigger Kiro Crew / 0_trigger _ trigger-agent.txt: feat(info): display commit-snapshot provenance (P1)
Conclusion: failure
##[group]Run set -euo pipefail
�[36;1mset -euo pipefail�[0m
�[36;1m: "${***REDACTED_SECRET_ASSIGNMENT*** missing}"�[0m
�[36;1m: "${***REDACTED_SECRET_ASSIGNMENT*** missing}"�[0m
�[36;1m: "${GATEWAY_URL:?KIRO_GATEWAY_URL missing}"�[0m
�[36;1m�[0m
�[36;1mif [ -n "${GATEWAY_ORIGIN:-}" ]; then�[0m
�[36;1m ORIGIN="$GATEWAY_ORIGIN"�[0m
�[36;1melse�[0m
�[36;1m ORIGIN=$(printf '%s' "$GATEWAY_URL" | sed -E 's#(https?://[^/]+).*#\1#')�[0m
�[36;1mfi�[0m
�[36;1mREPO_SHORT="${REPO##*/}"�[0m
�[36;1mSESSION_KEY="hook:github:${REPO_SHORT}:${EVENT}:${RUN_ID}"�[0m
�[36;1m�[0m
�[36;1mONE_OFF=""�[0m
�[36;1mif [ -n "${ONE_OFF_RAW// }" ]; then�[0m
�[36;1m ONE_OFF=$(printf '%s' "$ONE_OFF_RAW" | sed -E 's|^[[:space:]]*/[Kk][Ii][Rr][Oo][Cc][Rr][Ee][Ww][[:space:]]*||')�[0m
�[36;1m ONE_OFF=$(printf '%s' "$ONE_OFF" | sed -E 's|/kirocrew||Ig' | sed -E 's/^[[:space:]]+//;s/[[:space:]]+$//')�[0m
�[36;1mfi�[0m
�[36;1m�[0m
�[36;1mif [ -n "${PR_NUMBER}" ]; then�[0m
�[36;1m COMMENT_TARGET="Leave a single GitHub PR comment on ${REPO}#${PR_NUMBER} (gh pr comment ${PR_NUMBER})."�[0m
�[36;1m PR_LABEL="PR #${PR_NUMBER}"�[0m
�[36;1melse�[0m
�[36;1m COMMENT_TARGET="If an open PR contains commit ${SHA}, comment on that PR; otherwise leave a commit comment on ${SHA}."�[0m
�[36;1m PR_LABEL=""�[0m
�[36;1mfi�[0m
�[36;1m�[0m
�[36;1mMSG=$(jq -nr \�[0m
�[36;1m --arg prefix "$MESSAGE_PREFIX" \�[0m
�[36;1m --arg event "$EVENT" \�[0m
�[36;1m --arg repo "$REPO" \�[0m
�[36;1m --arg ref "$REF" \�[0m
�[36;1m --arg sha "$SHA" \�[0m
�[36;1m --arg run_id "$RUN_ID" \�[0m
�[36;1m --arg run_url "$RUN_URL" \�[0m
�[36;1m --arg pr_number "$PR_NUMBER" \�[0m
�[36;1m --arg pr_label "$PR_LABEL" \�[0m
�[36;1m --arg daytona "$DAYTONA_OS" \�[0m
�[36;1m --arg one_off "$ONE_OFF" \�[0m
�[36;1m --arg comment_url "$COMMENT_URL" \�[0m
�[36;1m --arg comment_target "$COMMENT_TARGET" \�[0m
�[36;1m '�[0m
�[36;1m def nl: "\n";�[0m
�[36;1m (if ($prefix | length) > 0 then $prefix ...
🧰 Additional context used
📓 Path-based instructions (12)
**/*
📄 CodeRabbit inference engine (CLAUDE.md)
**/*: Use Serena's semantic, symbol-aware tools as the primary tools for reading and editing code; use built-in Read, Glob, Grep, and Edit only under the stated exceptions.
Before editing a code file, inspect its symbol overview, read the specific symbols being changed, and edit them with Serena's symbol-aware tools.
Understand the existing code before changing it and make the smallest change that satisfies the request; avoid unrelated cleanup, premature abstractions, unnecessary error handling, feature flags, and compatibility shims.
Prefer editing existing files over creating new ones, and never create Markdown or README files unless explicitly requested.
For exploratory questions, provide a 2–3 sentence recommendation with the main tradeoff and do not implement until the user agrees.
For UI or frontend changes that cannot be tested in a browser, explicitly state that browser testing was not performed rather than claiming success.
Address security issues when discovered, including injection, XSS, SQL injection, path traversal, and secret leaks.
Pause and obtain confirmation before destructive, hard-to-reverse, externally visible, or third-party-upload actions, including deleting files or branches, dropping tables, force-pushing, modifying CI/CD, posting externally, or uploading content.
When blocked, investigate the root cause instead of bypassing it with --no-verify, --force, or deletion; investigate unfamiliar files, branches, and configuration before deleting them.
Only commit when explicitly asked; do not proactively update git configuration or push changes.
Do not skip Git hooks unless explicitly asked; if a pre-commit hook fails, fix the issue, re-stage, and create a new commit rather than amending.
Stage files by name rather than using git add -A or git add ., to avoid accidentally including secrets or large binaries.
Use a HEREDOC for commit messages, and add co-author attribution only when the user explicitly requests the exact trailer.
Do not force-pus...
Files:
src/cmd/try_cmd.rssrc/core/registry.rstests/install_test.rstests/support/active_update/mod.rssrc/cmd/info.rssrc/core/package.rssrc/cmd/search.rssrc/core/resolve.rs
**/*.{js,jsx,ts,tsx,py,java,go,rs,rb,php,c,cpp,h,hpp,cs,swift,kt,kts}
📄 CodeRabbit inference engine (CLAUDE.md)
Add comments only when the WHY is non-obvious; do not narrate what the code does, reference the current task, or reference the PR in comments.
Files:
src/cmd/try_cmd.rssrc/core/registry.rstests/install_test.rstests/support/active_update/mod.rssrc/cmd/info.rssrc/core/package.rssrc/cmd/search.rssrc/core/resolve.rs
!**/.env,!**/credentials.json,!**/*.pem
📄 CodeRabbit inference engine (CLAUDE.md)
Do not commit files that appear to contain secrets, including .env, credentials.json, and PEM files; warn before doing so even if explicitly requested.
Files:
src/cmd/try_cmd.rssrc/core/registry.rstests/install_test.rstests/support/active_update/mod.rssrc/cmd/info.rssrc/core/package.rssrc/cmd/search.rssrc/core/resolve.rs
**/*.rs
📄 CodeRabbit inference engine (CONTRIBUTING.md)
**/*.rs: Use the Rust 2021 edition.
Useanyhow::Resultwith.context(...)in application code; usethiserrorfor library error types that callers match on.
Useclapderive macros for CLI definitions.
Useserdewithserde_jsonortomlfor serialization.
Function parameters must use&Path, not&PathBuf.
Library code must not panic; error paths should returnanyhow::Resultwith context where appropriate.
Add or update tests for behavior changes, including relevant failure paths.
New mutating code paths must acquire the mutation lock viaacquire_mutation_lock(root)and snapshot the lockfile before writes.
Lockfile, journal, and state-file JSON writes must usewrite_json_atomic.
numan installmust write only to$NUMAN_ROOT; it must not invoke Nu or register plugins/autoloads.
Onlyactivateanddeactivatemay modify Nu integration state.
Treat the lockfile as the authoritative source of truth; derived projections such as autoload state must not be authoritative.
Install payloads under versioned, content-addressed paths and never overwrite them in place.
Never overwrite foreign autoload files; respectOWNERSHIP_MARKER.
Pass plugin paths through environment variables only; do not use runtime interpolation in Nu program strings.
**/*.rs: All CI gates must pass:cargo test,cargo clippy -- -D warnings, andcargo fmt --check.
Every mutating command—includinginstall,remove,update,gc, and futurenupm import—must callacquire_mutation_lock(root).
Lockfiles, journals, and state files must usewrite_json_atomic; partial writes are not allowed.
Pending activation, autoload, and lifecycle journals must be stored under$NUMAN_ROOT/state/.
Module autoload identity must match all four fields: Nu executable hash, Nu version, vendor autoload directory, and managed file path; the lockfilemodule_activationvalue is authoritative.
Never overwrite foreign autoload files; respectOWNERSHIP_MARKER.
Pass paths to Nu only throu...
Files:
src/cmd/try_cmd.rssrc/core/registry.rstests/install_test.rstests/support/active_update/mod.rssrc/cmd/info.rssrc/core/package.rssrc/cmd/search.rssrc/core/resolve.rs
**/*.{rs,toml}
📄 CodeRabbit inference engine (CONTRIBUTING.md)
Run and keep
cargo fmt/rustfmtclean, and ensurecargo clippy -- -D warningspasses.
Files:
src/cmd/try_cmd.rssrc/core/registry.rstests/install_test.rstests/support/active_update/mod.rssrc/cmd/info.rssrc/core/package.rssrc/cmd/search.rssrc/core/resolve.rs
**/*.{rs,nu}
📄 CodeRabbit inference engine (CONTRIBUTING.md)
**/*.{rs,nu}: Real-Nu acceptance tests must be marked#[ignore]and should be run when changes affect activation or nupm import; unit tests must not spawn realnuand should use injectable seams such asFakeCandidateRunneror registrars.
The nupm integration must be read-only towardNUPM_HOME, must not executebuild.nu, and must not perform bidirectional synchronization.Unit tests must use
FakeCandidateRunneror injectable registrars and must not spawn a realnuprocess.
Files:
src/cmd/try_cmd.rssrc/core/registry.rstests/install_test.rstests/support/active_update/mod.rssrc/cmd/info.rssrc/core/package.rssrc/cmd/search.rssrc/core/resolve.rs
**/*.{rs,md}
📄 CodeRabbit inference engine (CONTRIBUTING.md)
Match existing naming, module layout, and documentation level in the file being edited; update
AGENTS.md,docs/, or command help when structure, conventions, or user-visible behavior changes.Tests must cover failure modes, not only successful execution.
Files:
src/cmd/try_cmd.rssrc/core/registry.rstests/install_test.rstests/support/active_update/mod.rssrc/cmd/info.rssrc/core/package.rssrc/cmd/search.rssrc/core/resolve.rs
**/*.{rs,md,toml}
📄 CodeRabbit inference engine (CONTRIBUTING.md)
Use the repository's established serialization and module conventions rather than introducing unrelated refactors.
Files:
src/cmd/try_cmd.rssrc/core/registry.rstests/install_test.rstests/support/active_update/mod.rssrc/cmd/info.rssrc/core/package.rssrc/cmd/search.rssrc/core/resolve.rs
src/cmd/**/*.rs
📄 CodeRabbit inference engine (AGENTS.md)
Pass Nu paths and names through environment variables (
NUMAN_PLUGIN_BINARY,NUMAN_PLUGIN_CONFIG, andNUMAN_PLUGIN_NAME); the Nu program string must be a compile-time constant with no runtime interpolation.
Files:
src/cmd/try_cmd.rssrc/cmd/info.rssrc/cmd/search.rs
src/core/**/*.rs
📄 CodeRabbit inference engine (AGENTS.md)
Derive the platform triple from compile-time
#[cfg(target_env)]values, notstd::env::consts;LIBCmust be a compile-time constant.
Files:
src/core/registry.rssrc/core/package.rssrc/core/resolve.rs
src/core/{trust.rs,official_registry.rs,registry.rs}
📄 CodeRabbit inference engine (AGENTS.md)
Verify Ed25519 signatures over the exact
index.jsonbytes; use the built-in production trust root for theofficialregistry. Unsigned bypass is allowed only withNUMAN_ALLOW_UNSIGNED=1for development.
Files:
src/core/registry.rs
tests/**/*.rs
📄 CodeRabbit inference engine (AGENTS.md)
Test platform-specific behavior with mock platforms, and use injected fakes rather than real Nu for unit tests.
Files:
tests/install_test.rstests/support/active_update/mod.rs
🔍 Remote MCP DeepWiki, GitHub Copilot
Additional review context
- PR
#114addsVersionEntry.provenance: Option<String>with#[serde(default)], preserving parsing of existing registry indexes. The client renders a note only for the exact value"commit-snapshot". - The companion registry PR
#63is still open/draft. It adds an optional string schema property and passthrough from package specs; it does not constrain values to an enum. - The companion plugins PR
#80defines the producer contract: snapshot entries retain a mandatory immutablesource_commit, derive versions like0.0.0-snapshot.YYYYMMDD.<sha>, and emitprovenance: "commit-snapshot". - The intake plan states that tagged releases remain preferred; snapshots are a fallback for untagged upstream commits. SHA-256 artifact verification, Ed25519 index signatures, and immutable commit provenance remain mandatory.
- The changed client code does not alter resolver or update behavior; the documented design relies on SemVer ordering so normal tagged releases outrank synthetic prerelease snapshot versions.
- At the time checked, Ubuntu/macOS tests, formatting, Clippy, MSRV, and deny checks succeeded; Windows test and Windows real-Nu acceptance were still in progress, while the
trigger / trigger-agentcheck had failed and CodeQL was neutral.
🔇 Additional comments (9)
src/cmd/search.rs (1)
254-254: LGTM!src/cmd/try_cmd.rs (1)
471-471: LGTM!src/core/registry.rs (1)
409-409: LGTM!src/core/resolve.rs (1)
729-729: LGTM!Also applies to: 747-747, 1060-1060
tests/install_test.rs (1)
140-140: LGTM!Also applies to: 385-385, 468-468, 539-539
tests/support/active_update/mod.rs (1)
509-509: LGTM!src/core/package.rs (1)
115-118: 🗄️ Data Integrity & IntegrationVerify the serialized representation of absent
provenance.
#[serde(default)]makes a missing field deserialize asNone. It does not omitNoneduring serialization. The new tests callserde_json::from_stronly, so they do not detect an omitted-field versusnullmismatch in registry JSON. Confirm the registry schema, then add serialization assertions for bothNoneand"commit-snapshot". If omission is required, addskip_serializing_if.Possible fix when omission is required
- #[serde(default)] + #[serde(default, skip_serializing_if = "Option::is_none")] pub provenance: Option<String>,Also applies to: 276-298
Source: MCP tools
src/cmd/info.rs (2)
82-85: LGTM!
168-168: LGTM!
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Sorry @tonythethompson, you have reached your weekly rate limit of 500000 diff characters.
Please try again later or upgrade to continue using Sourcery
PR Summary by QodoDisplay commit-snapshot provenance in
AI Description
Diagram
High-Level Assessment
Files changed (8)
|
Greptile SummaryImplements client-side commit-snapshot provenance display while keeping older registry entries backward compatible.
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains.
|
| Filename | Overview |
|---|---|
| src/core/package.rs | Adds backward-compatible optional provenance metadata and tests parsing with and without the field. |
| src/cmd/info.rs | Renders the provenance note only for commit-snapshot versions and covers matching, absent, and unrelated values. |
| src/cmd/completions.rs | Recursively removes help subcommands from completion generation and updates installation hints and tests. |
| src/cli.rs | Updates the use command help text to describe its supported forms. |
| src/core/resolve.rs | Updates resolver test fixtures for the new optional version field without changing resolution behavior. |
Reviews (3): Last reviewed commit: "fix(completions): slim scripts and corre..." | Re-trigger Greptile
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can reply 'qodo' on any finding to push back, ask questions, or dig deeper |
Qodo FixerNo findings are available for this PR yet. Findings appear here once Qodo has reviewed the PR. |
Cover the forward-compatible string contract so future provenance values do not accidentally trigger the commit-snapshot message. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Added format_info_omits_provenance_note_for_other_values in e1d28e5 to assert non-commit-snapshot provenance values do not emit the snapshot note. |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Drop help subcommands from generated completion trees to cut script size, fix the invalid mkdir --all Nushell hint, update use command docs, and remind users to refresh completions after upgrading numan. Co-authored-by: Cursor <cursoragent@cursor.com>
2afc50e
|
Addressed in e1d28e5: added format_info_omits_provenance_note_for_other_values covering non-commit-snapshot provenance values. |
1 participant
Summary
VersionEntrygains an optionalprovenance: Option<String>field (#[serde(default)], backward compatible).numan infoprints a note under a version whenprovenance == "commit-snapshot": "built from a commit snapshot, not a tagged release".latest_compatibleand update already order purely bysemver::Version::cmp, which correctly ranks a real tagged release above a0.0.0-snapshot.*prerelease with no special-casing required.Test plan
cargo build— cleancargo test— 659+ passed across lib and all integration test binaries, 0 failedcargo fmt --check— cleanVersionEntryprovenance parsing (present/absent),numan infonote rendering (present/absent)Ref:
docs/plans/2026-08-09-intake-process-reform.md(P1, innuman-registry/ADR PR #113 context).🤖 Generated with Claude Code