Dashboard › cli › Distillation
f2371ba3-9745-47ae-b470-f835000b2fec["lore_tm_v1_5BhlnbFNmDRi61o8x85B5ljDHVSOFh4Nvp7JHB_BLMA"]
Date: September 8, 2026
/; unlike trace/replay IDs, they are not organization/project-scoped.apps/cli-docs/src/fragments/commands/agent-conversation.md was emptied, removing hand-written list and view examples because those examples now live in command metadata.packages/cli/script/check-fragments.ts now skips fragment subcommand-coverage validation for any cmd where cmd.examples.length > 0; commands without metadata examples must still be mentioned by a fragment heading or code example.packages/cli/script/generate-command-docs.ts now imports formatCommandExamples from ./generate-skill-markdown.js and appends formatted cmd.examples to each generated command section. Generated pages now treat reference material and examples as CLI-metadata-derived, while fragments contain guides, tips, and content that cannot live in command definitions.formatPositionalsTable() in packages/cli/script/generate-command-docs.ts now renders optional positional arguments as [<${p.placeholder}>] and required ones as <${p.placeholder}>.packages/cli/script/generate-skill-markdown.ts now exports formatCommandExamples(examples: readonly string[]): string; it returns an empty string for no examples, otherwise emits an **Examples:** section with one bash code fence and examples separated by blank lines.packages/cli/script/generate-skill.ts now imports and reuses formatCommandExamples() in generateFullCommandDoc() instead of constructing its examples section inline.packages/cli/src/commands/agent-conversation/list.ts now defines POSITIONAL as one optional tuple positional named org with brief Organization slug, parse: String, and optional: true; USAGE_HINT is derived as sentry ${COMMAND_NAME} ${getPositionalString(POSITIONAL)} using getPositionalString from ../../lib/introspect.js.agent-conversation list command removed docs.customUsage: ["[<org>]"]; its fullDescription now says the organization is auto-detected when omitted, and parameters.positional reuses POSITIONAL.agent-conversation list metadata now contains 5 ordered examples: 1. List recent agent conversations — sentry agent-conversation list; 2. Explicit organization — sentry agent-conversation list my-org; 3. Show more, last 24 hours — sentry agent-conversation list --limit 50 --period 24h; 4. Filter conversations — sentry agent-conversation list -q "has:errors"; 5. Paginate through results — sentry agent-conversation list my-org -c next.packages/cli/src/commands/agent-conversation/list.ts, failure to resolve an organization now throws new ContextError("Organization", USAGE_HINT) using the positional-derived canonical usage rather than the hard-coded sentry agent-conversation list <org>.packages/cli/src/commands/agent-conversation/view.ts now defines USAGE = "[<org>/]<conversation-id>" and derives USAGE_HINT as sentry agent-conversation view ${USAGE}; docs.customUsage reuses USAGE.parseConversationTarget(target) in packages/cli/src/commands/agent-conversation/view.ts trims the input and interprets at most one slash: without a slash, the entire value is conversationId and the organization is auto-detected; with a slash, text before the first slash is org and the remainder is conversationId; an empty organization or conversation-ID segment throws new ContextError("Conversation ID", USAGE_HINT, []).agent-conversation view description now states that the organization is optional and auto-detected from project context when omitted, and that an organization slug can prefix the ID to target a specific organization.agent-conversation view metadata now contains 3 ordered examples: 1. View full transcript (organization auto-detected) — sentry agent-conversation view conv-123; 2. Explicit organization — sentry agent-conversation view my-org/conv-123; 3. JSON output — sentry agent-conversation view my-org/conv-123 --json.