Skip to content

Scenario scorer: score the seven capability tags the mid-tier cards declare but the closed tag table leaves unscored #30984

Open

Description

@objectstack-fleet

epic:#3600#1 · hotlong · session_01Q4EjjPXwX1YfHyKJUh4agu

Filing-gate category: ② epic follow-up, planned when the mid-tier cards landed (#30476–#30481, all landed). Measured in the 8-card live run, 2026-11-06: the mid-tier cards declare capability tags the scorer's closed table does not score, so each shows unscored on the scorecard:

  • records-forms.formula-field
  • records-forms.validation-rule
  • approvals.multi-step-approval
  • approvals.dynamic-approver-routing
  • access-security.row-level-security
  • dashboards.report
  • ai.agent-actions

The Build half therefore never checks the capability each card was written to exercise. Routing, verbatim: 「能交给车队开发的你不要自己开发」.

Ask

Add one row per tag to the closed tag table (packages/qa/scenarios/src/score/scenario-tags.ts). Each row needs:

  • a structural check over the built artifact, read through the platform's own schemas;
  • the discrimination test the existing rows carry: one fixture that passes and one that fails for the stated reason.

Suggested checks, to be sharpened by the lane:

⛔ Never match by area prefix (the table's existing rule).

Reader: the domain:devx lane seat, from pm:queue.

Activity

  1. added
    priority:p1High: required for production / M2
    pm:queueReady for the PM dispatch loop
    domain:devxDomain lane — seat card indexed by label:pm:seat
    area:devpathThe road — create, dev, verify, publish/install, connect an agent, iterate
    on Nov 6, 2026
  2. objectstack-fleet commented on Nov 6, 2026

    @objectstack-fleet
    ContributorAuthor

    triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

    Path: none

    Triage: audit · p1 kept · domain:devx · 2026-11-06T15:59Z

    ⛔ Not a claim.

    • An epic follow-up (objectstack-ai/cloud#3600). Seven capability tags that the mid-tier cards declare are unscored by the closed tag table, so the Build half never checks the capability each card exists for. Each new row brings a structural check and a pass/fail discrimination fixture.
    • p1, domain:devx, area:devpath and pm:queue kept.

    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:devpathThe road — create, dev, verify, publish/install, connect an agent, iteratedomain:devxDomain lane — seat card indexed by label:pm:seatpm:queueReady for the PM dispatch looppriority:p1High: required for production / M2

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions