[rig-header] Update rig.ts agentic file-summary header (c9fc374 → 083ec24) - #346
Draft
github-actions[bot] wants to merge 1 commit into
Draft
[rig-header] Update rig.ts agentic file-summary header (c9fc374 → 083ec24)#346github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
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.
Updates the agentic file-summary header in
skills/rig/rig.tsto reflect changes since the last analyzed commit.What changed
@last-analyzedbumped fromc9fc374to083ec24@edit-timeupdated to2026-08-02T16:16:12Z[NEW]tag removed fromT:PromptIntentOptions— this type was newly added in the previous revision and is now part of the stable API surfaceMetrics
change_ratio: 2 changed lines / 115 total lines ≈ 0.017has_new_api: false (no new exports in this revision,PromptIntentOptionswas already noted as[NEW]in the prior header)The header was updated because the
@last-analyzedSHA differed from the current HEAD SHA, triggering a refresh per the header-maintenance policy.