Skip to content

docs(compliance): add capability-flag → scenario cross-reference index#4042

Draft
bokelley wants to merge 1 commit intomainfrom
claude/issue-4039-capability-flag-scenario-cross-reference
Draft

docs(compliance): add capability-flag → scenario cross-reference index#4042
bokelley wants to merge 1 commit intomainfrom
claude/issue-4039-capability-flag-scenario-cross-reference

Conversation

@bokelley
Copy link
Copy Markdown
Contributor

@bokelley bokelley commented May 4, 2026

Closes #4039

Summary

Adds a "Capability-gated scenarios" section to compliance-catalog.mdx that maps each get_adcp_capabilities flag to the compliance scenarios it controls. Adopters can now see at a glance how toggling a flag changes their grading surface, without grepping scenario YAMLs.

Also fixes two related correctness issues surfaced during pre-PR review:

  1. sales-proposal-mode deprecation — updates the specialism table row from stable to deprecated and adds a migration Note, matching the x-deprecated-enum-values declaration already in specialism.json. Related: docs: specialism decision tree — which sales-* specialism should I claim? #4038 also calls for this.
  2. Schema description fixget-adcp-capabilities-response.json incorrectly stated "When false or absent, conformance runners skip proposal-lifecycle storyboards." The compliance runtime (sales-guaranteed/index.yaml) treats absent as true (scenario runs). Description updated to match.

Non-breaking justification: docs-only section addition and a schema description field fix. No wire shape changes, no required fields added, no enum values altered. The schema "default": false is preserved; only the prose description is corrected.

Pre-PR review

  • code-reviewer: approved — flagged the schema/runtime description contradiction as a blocker; fixed in get-adcp-capabilities-response.json. One nit on table cell wording; addressed.
  • docs-expert: approved with nits — table cell "Default (when absent)" wording clarified to "treated as true — runs (graded)"; sales-proposal-mode purpose cell trimmed to match column length discipline.

Triage-managed PR. This bot does not currently iterate on
review comments or PR conversation threads (only on the source
issue). To unblock:

  • Push fixup commits directly: gh pr checkout 4039
    fix → push.
  • Or re-trigger: comment /triage execute on the source
    issue.

See #3121
for context.

Session: https://claude.ai/code/session_014X1pXA976RomzNxWUC4ei9


Generated by Claude Code

Adds a "Capability-gated scenarios" section to compliance-catalog.mdx
mapping each get_adcp_capabilities flag to the scenarios it controls,
so adopters can see at a glance how a flag toggle changes their grading
surface without grepping scenario YAMLs.

Also fixes two related issues in the same file and schema:

- Updates sales-proposal-mode specialism status to deprecated (matching
  the x-deprecated-enum-values declaration in specialism.json)
- Fixes the supports_proposals schema description, which incorrectly
  stated "absent" means skip; the compliance runtime treats absent as
  true (per sales-guaranteed/index.yaml), so the description now reads
  "When absent, the compliance runner treats the flag as true"

Closes #4039.

https://claude.ai/code/session_014X1pXA976RomzNxWUC4ei9
@bokelley bokelley added the claude-triaged Issue has been triaged by the Claude Code triage routine. Remove to re-triage. label May 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

claude-triaged Issue has been triaged by the Claude Code triage routine. Remove to re-triage.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: capability flag → scenario cross-reference ("what does this flag turn on/off?")

2 participants