Skip to content

fix(work-items): read frontier tier from capability-tier label (#1716) - #2565

Merged
kyle-sexton merged 10 commits into
mainfrom
cursor/frontier-tier-label-1716-d116
Aug 13, 2026
Merged

fix(work-items): read frontier tier from capability-tier label (#1716)#2565
kyle-sexton merged 10 commits into
mainfrom
cursor/frontier-tier-label-1716-d116

Conversation

@kyle-sexton

@kyle-sexton kyle-sexton commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Closes #1716

Summary

Moves the work-loop frontier-tier signal from triage briefing body prose onto the provider-permissioned capability-tier: frontier label. Missing label fails closed to the general tier.

Fix

  • work-loop Adaptive item cap reads the label from list-frontier projections
  • item-content-trust: remove tightening-only body carve-out; add enforced-by-name entry
  • label-taxonomy / capability-tier-labels docs
  • triage Capability-tier stamp rule
  • evals updated for label-based prompt
  • work-items version bump

Verification

  • CI skill-quality / changelog-parity / plugin-options-docs

Related

Refs #1721 — prior containment superseded by this reader flip.

@github-actions github-actions Bot deleted a comment from claude Bot Aug 13, 2026
@kyle-sexton
kyle-sexton marked this pull request as ready for review August 13, 2026 05:56
@cursor

cursor Bot commented Aug 13, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@claude

claude Bot commented Aug 13, 2026

Copy link
Copy Markdown

Claude encountered an error after 0s —— View job


I'll analyze this and get back to you.

@github-actions

github-actions Bot commented Aug 13, 2026

Copy link
Copy Markdown

Warning

Automated security review did not complete — this is an infrastructure failure, not a review verdict.

Treat any Claude comment on this PR (including a placeholder like "I'll analyze this and get back to you") as incomplete, not "no findings."

The check is green on purpose, and it is not evidence. It certifies that a security pass ran, and this one did not complete — but the cause is outside this PR's control, so merging is deliberately left unblocked rather than locking every merge for the length of the outage. Nothing was reviewed at this head. Where this check is required, it is satisfied without that evidence; a human should review security-sensitive changes here before merging.

Re-run the job, or workflow_dispatch this workflow with the PR number, to retry the review (ci-workflows#227). A new push also retries it only if the caller's pull_request triggers include synchronize (the canonical security caller keeps it). An automatic retry may already have run — it is skipped when a partial review could duplicate comments, or when the failure class needs an operator.

Re-running does NOT help for every class:

  • rate-limit that persists across re-runs, or auth — the credential or usage budget needs an operator; retrying will not clear it.
  • a run that exhausted its turn budget ("subtype":"error_max_turns" above) will exhaust it again. As the PR author, split the change into smaller PRs; raising --max-turns is a change to the caller workflow, not something you can set on this PR.

@github-actions github-actions Bot deleted a comment from claude Bot Aug 13, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a9fbad8983

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread plugins/work-items/reference/capability-tier-labels.md
Comment thread plugins/work-items/reference/capability-tier-labels.md
@github-actions github-actions Bot deleted a comment from claude Bot Aug 13, 2026
@claude

claude Bot commented Aug 13, 2026

Copy link
Copy Markdown

Claude encountered an error after 2s —— View job


I'll analyze this and get back to you.

@cursor
cursor Bot force-pushed the cursor/frontier-tier-label-1716-d116 branch from 9bcc9e8 to ecda054 Compare August 13, 2026 06:01
@claude

claude Bot commented Aug 13, 2026

Copy link
Copy Markdown

Claude encountered an error after 0s —— View job


I'll analyze this and get back to you.

@github-actions

github-actions Bot commented Aug 13, 2026

Copy link
Copy Markdown

Warning

Automated review did not complete — this is an infrastructure failure, not a review verdict.

Treat any Claude comment on this PR (including a placeholder like "I'll analyze this and get back to you") as incomplete, not "no findings."

Re-run the job, or workflow_dispatch this workflow with the PR number, to retry the review. A new push re-triggers this lane only if the caller's pull_request triggers include synchronize (the canonical caller omits it).
An automatic retry may already have run — it is skipped when a partial review could duplicate comments, or when the failure class needs an operator (auth).

@github-actions github-actions Bot deleted a comment from claude Bot Aug 13, 2026
@claude

claude Bot commented Aug 13, 2026

Copy link
Copy Markdown

Claude encountered an error after 0s —— View job


I'll analyze this and get back to you.

@github-actions github-actions Bot deleted a comment from claude Bot Aug 13, 2026
@claude

claude Bot commented Aug 13, 2026

Copy link
Copy Markdown

Claude encountered an error after 0s —— View job


I'll analyze this and get back to you.

cursoragent and others added 6 commits August 13, 2026 06:29
Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
Add capability-tier-labels.md reference, tracker-seam axis row, and
manifest/README descriptions. Document github-iac provisioning requirement
and security-surface dispatch vs quota-guard separation.

Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
…ll (#1716)

Add setup check probe 8 and apply steps for capability-tier: frontier
label provisioning, plus a one-shot backfill path for items that carry
only pre-#1716 triage-briefing body stamps. Triage refuses to re-triage
already-triaged output, so setup apply runs backfill-capability-tier-labels.sh
after the axis exists.

Bump to 0.35.21.

Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
Move capability-tier migration and backfill procedures to progressive-
disclosure reference spokes. Shorten the setup description to stay under
the 1536-char listing cap and bring SKILL.md under the 500-line hard cap.

Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
@cursor
cursor Bot force-pushed the cursor/frontier-tier-label-1716-d116 branch from e60e9ba to 626b348 Compare August 13, 2026 06:40
@github-actions github-actions Bot deleted a comment from claude Bot Aug 13, 2026
…vals JSON

changelog-parity --check-preserved requires the fork-point ## [0.35.19]
section to remain; keep #1716 notes under 0.35.20/0.35.21. Insert the
missing comma before eval cases 14–15 so check-jsonschema can parse.

Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
@claude

claude Bot commented Aug 13, 2026

Copy link
Copy Markdown

Claude encountered an error after 0s —— View job


I'll analyze this and get back to you.

@github-actions github-actions Bot deleted a comment from claude Bot Aug 13, 2026
@claude

claude Bot commented Aug 13, 2026

Copy link
Copy Markdown

Claude encountered an error after 0s —— View job


I'll analyze this and get back to you.

…egacy signal lib

Flatten nested setup SKILL list to satisfy markdownlint. Invoke label-existence
checks outside if conditions for SC2310. Mark legacy-frontier-tier-signal.sh
executable in the git index.
@github-actions github-actions Bot deleted a comment from claude Bot Aug 13, 2026
@claude

claude Bot commented Aug 13, 2026

Copy link
Copy Markdown

Claude encountered an error after 0s —— View job


I'll analyze this and get back to you.

@kyle-sexton
kyle-sexton merged commit 305d31a into main Aug 13, 2026
38 checks passed
@kyle-sexton
kyle-sexton deleted the cursor/frontier-tier-label-1716-d116 branch August 13, 2026 06:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

work-items/work-loop: the frontier-tier signal is read from the issue body with no refusal attached

2 participants