Distillation

Date: Sep 9, 2026

• 🔴 (16:17) User directive: buildDeleteCommand() must always inject --yes unless the command already defines it.
• 🔴 (16:17) User stated extractFlags() always returns one FlagInfo per input entry.
• 🔴 (16:17) User stated tuple handling in getPositionalString() always produces angle-bracket placeholders; required parameters render as <placeholder>, optional parameters as [<placeholder>], and missing names default to arg${index}.
• 🔴 (16:17) User stated array handling in getPositionalString() always includes an ellipsis; named arrays render as <placeholder...> and unnamed arrays default to <args...>.
• 🔴 (16:17) User stated resolveCommandPath(routeMap, []) always returns null.
• 🟡 (16:17) Tool diff showed packages/cli/src/lib/mutate-command.ts changing buildDeleteCommand() documentation typing to CommandDocumentation. Its auto-injection behavior is: --yes unless already defined; --force unless options.noForceFlag or already defined; --dry-run unless options.noDryRunFlag or already defined; aliases -y, -f, and -n only when their keys are free and corresponding flags are enabled. options.noNonInteractiveGuard disables the pre-hook safety guard.
• 🟡 (16:17) Tool diff showed the buildDeleteCommand() non-interactive pre-hook calling guardNonInteractive() with yes, force, and dry-run; dry runs bypass the guard, while commands remain responsible for resolved-data confirmation using confirmByTyping() and isConfirmationBypassed().
• 🟡 (16:17) Tool diff showed a new packages/cli/test/commands/agent-conversation/list.test.ts assertion that organization-resolution errors use canonical command usage sentry agent-conversation list [<org>].
• 🟡 (16:17) Tool diff showed packages/cli/test/commands/agent-conversation/view.test.ts adding malformed-target validation for 5 forms: ${ORG}/${CONVERSATION_ID}/extra, ${ORG}//${CONVERSATION_ID}, ${ORG}/${CONVERSATION_ID}/, /${CONVERSATION_ID}, and ${ORG}/. Each must throw ValidationError with field: "conversation-id" and a message containing sentry agent-conversation view [<org>/]<conversation-id> before resolveOrg() or getConversationSpans() is called.
• 🟡 (16:17) Tool diff showed packages/cli/test/lib/command.test.ts verifying buildCommand() retains structured docs.examples as __examples; example metadata contains { description: "Select an organization explicitly", command: "sentry thing list my-org" }.
• 🟡 (16:17) Tool diff showed packages/cli/test/lib/introspect.property.test.ts properties: extractFlags() preserves every flag name; boolean flags with unspecified optional default to optional: true; extractAllRoutes() never includes entries that are only hidden and returns no more routes than visible entries; resolved command paths begin with sentry .
• 🟡 (16:17) Tool diff showed packages/cli/test/lib/introspect.test.ts confirming optional tuple formatting as <required> [<optional>], while existing tuple formatting remains <org> <project>, unnamed tuples remain <arg0> <arg1>, named arrays remain <command...>, and unnamed arrays remain <args...>.
• 🟡 (16:17) Tool diff showed buildCommandInfo() prefers __primaryUsage over derived positional syntax and prefers structured __examples over legacy document examples. Structured examples are converted in order to comment-plus-command strings: # Use automatic organization detection\nsentry thing list and # Select an organization explicitly\nsentry thing list my-org.
• 🟡 (16:17) Tool diff showed packages/cli/test/script/generate-skill-markdown.test.ts verifying agent-conversation docs derive from command metadata rather than a __primaryUsage override. listCommand has positional syntax [<org>] and includes # Explicit organization\nsentry agent-conversation list my-org.
• 🟡 (16:17) Tool diff showed viewCommand has positional syntax [<org>/]<conversation-id> and exactly 3 ordered examples: 1. # View full transcript (organization auto-detected)\nsentry agent-conversation view conv-123, 2. # Explicit organization\nsentry agent-conversation view my-org/conv-123, 3. # JSON output\nsentry agent-conversation view my-org/conv-123 --json.
• 🟡 (16:17) Tool diff showed formatCommandExamples() rendering the 3 viewCommand examples under **Examples:** in one fenced bash block, preserving descriptions as shell comments and blank lines between examples.
• 🟡 (16:17) Tool diff showed generated project-reference constraints in plugins/sentry-cli/skills/sentry-cli/references/project.md: heading must be ### \sentry project create [<org>/]<name>:<platform>...`; platform must attach with :rather than a space; retained valid examples aresentry project create web:javascript api:python-django worker:nodeandsentry project create my-new-app:javascript-nextjs`.