Skip to content

cat-mode: lead the thrash-stop default with the general catch lesson. - #1314

Merged
mergify[bot] merged 6 commits into
mainfrom
stack/EdbertChan/automate/dashboard-health-receipt/cat-mode-lead-thrash-stop-default-general-catch--eedc8823
Oct 12, 2026
Merged

mergify[bot] merged 6 commits into
mainfrom
stack/EdbertChan/automate/dashboard-health-receipt/cat-mode-lead-thrash-stop-default-general-catch--eedc8823

Conversation

@EdbertChan

@EdbertChan EdbertChan commented Oct 8, 2026 •

Copy link
Copy Markdown
Owner

Summary

A dashboard story waits until the health receipt is in the reply.

The stop-work rule leads with the general case. A flag name is only an example.

A backticked flag is not counted as a missing skill.

Review Claim

A dashboard story cannot skip the health receipt, and a flag token is not a missing skill.

Review Lane

behavior

Review Unit

corpus-lesson

Safety Invariant

The check fires when a dashboard story starts before the health receipt. A reply that shows the receipt and then diagnoses stays quiet. A backticked flag is not treated as a skill that must exist.

Slice Rationale

The receipt rule, the wording that leads with the general case, and the flag allowlist are one lesson. They read the same page, so they land together.

Non-goals

Does not change the dashboard product. Does not add a new checker process. Does not merge the lower slices on their own.

Measured

Command: python3 -m unittest tests.test_cat_mode.TestPublishingAnalyticsDefaults -q

  • base: Ran 4 tests in 0.001s then OK, exit 0
  • head: Ran 9 tests in 0.002s then OK, exit 0

Test Plan

Test Plan
  • python3 -m unittest tests.test_cat_mode.TestPublishingAnalyticsDefaults -q — head Ran 9 tests in 0.002s then OK
  • python3 -m unittest tests.test_cat_mode.TestCatModeReferences -q — Ran 1 test in 0.001s then OK
  • Not run: a live dashboard in the product. Blocker: this change is the written lesson and its tests, and there is no dashboard app in this repo

Revert Plan

Revert Plan

Revert this pull request. The lesson goes back to letting a dashboard story start without the receipt, and the flag token is counted as a skill again.

EdbertChan and others added 6 commits October 8, 2026 06:55
Agents kept narrating by-model health and patching charts before splitting volume, fill, resolve, and filter — lock that check into standing defaults.

Co-authored-by: Cursor <cursoragent@cursor.com>
Change-Id: I8efc336daf9878751865cf3c4bac4d55cd50733f
Phrase-judge rejected leads that named only the trigger phrase; state the split and the stop-first catch as the lesson, with the triggers as examples.

Co-authored-by: Cursor <cursoragent@cursor.com>
Change-Id: I7dad9e54f9d280bb4d8f41ac06662293e39c9e05
…mple phrasing.

Co-authored-by: Cursor <cursoragent@cursor.com>
Change-Id: Idebc0f0ba74e47864bf479446a8e27b0574cdcde
…lesson.

Co-authored-by: Cursor <cursoragent@cursor.com>
Change-Id: Iaa84683fcf5a66e8f70a0dbf99ebcf19acc1d7a7
The dashboard-health defaults name that audit flag in backticks; the
skill-existence check must treat it as a process token, not a skill path.

Co-authored-by: Cursor <cursoragent@cursor.com>
Change-Id: I1afa1d44a91d2886300ab5f17843b8e583dbda0c
Rule-scope rejected a lead that named automate-mandate mid thrash; keep
named flags only as examples after the same-type-catch rule.

Co-authored-by: Cursor <cursoragent@cursor.com>
Change-Id: Ieedc8823a35a6be02d6b392d5c704f1b817d7ea1
Co-authored-by: Cursor <cursoragent@cursor.com>
@cursor

cursor Bot commented Oct 8, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 42c6b393-2c8d-4661-9081-61350984d74e)

@EdbertChan
EdbertChan changed the base branch from stack/EdbertChan/automate/dashboard-health-receipt/cat-mode-allowlist-intervention-must-automate--1afa1d44 to main October 12, 2026 14:43
@EdbertChan

Copy link
Copy Markdown
Owner Author

@Mergifyio queue

@mergify

mergify Bot commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 3 hours 38 minutes 11 seconds in the queue, including 2 hours 28 minutes 5 seconds running CI.

Required conditions to merge
  • check-success = lint
  • check-success = test
  • check-success = validate

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant