docs(user-guide): clarify backfill-my-metrics --yes scope - #55
Open
audip wants to merge 1 commit into
Open
Conversation
--my-usage/--task-metrics only shape the dry-run preview; --yes alone only executes a Codex-source cost repair or a --campaign-gated managed replay. Users on other clients (e.g. Claude Code) were misreading the --dry-run help text as implying a real publish path that doesn't exist. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
1 participant
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.
Fixes #53
--my-usageand--task-metricsweren't documented anywhere in USER-GUIDE.md or METRICS-REFERENCE.md as being dry-run-only presets with no real-execution path of their own. This led to reading the-dry-runflag's help text ("use --my-usage --yes or --task-metrics --yes for an authorized historical repair") as implying a real publish path for non-Codex clients, when in practice--yesalways executes either the Codex-source cost repair or a--campaign-gated managed replay, regardless of which preset flag is passed.This adds a short clarifying note right after the existing Codex-repair example in USER-GUIDE.md, stating that plainly.
Docs-only change; no code/test impact.