README: list the CATSTACK_DRAFTER_CORE flag

[EdbertChan]

Summary

The readme's settings table now lists the new setting that turns the outside PR rule package back on.

Without this row, a reader of the table would not know the PR rules are off by default or how to turn them on.

Review Claim

The readme settings table lists the new PR rule setting and what it does.

Review Lane

docs

Review Unit

docs

Safety Invariant

Text-only change to one table row; no code, hook, or install path reads it.

Slice Rationale

Docs are their own review unit here, so this row sits on top of the PR that adds the setting.

Non-goals

• Does not change any script or test.

Test Plan

Test Plan

• python3 engine/skills/make-pr/scripts/preflight.py --base <parent branch> --body-file <this body>
• Row reads: CATSTACK_DRAFTER_CORE=1 | env and files | the draft-pr scripts run the drafter-core PR rules; off, they print UNCHECKED and skip them

Revert Plan

Revert Plan

• Safe to revert? Yes
• Revert command: git revert <sha>
• Post-revert steps: None
• Data migration? No

🤖 Generated with Claude Code

Depends-On: #742

---

Note

Low Risk
Single README table row; no runtime, hook, or install behavior changes in this diff.

Overview
The Flags table in README.md now includes CATSTACK_DRAFTER_CORE=1, documenting that it is read from env and files (same lookup as other catstack flags) and that draft-pr scripts either run drafter-core PR rules when on or emit UNCHECKED and skip them when off.

This is a docs-only follow-up so readers see the opt-in switch and default-off behavior without digging into draft-pr or .env.example.

^{Reviewed by Cursor Bugbot for commit 62cd017. Bugbot is set up for automated code reviews on this repo. Configure here.}

[EdbertChan]

This pull request is part of a Mergify stack:

#	Pull Request	Link
1	Turn drafter-core PR rules off unless CATSTACK_DRAFTER_CORE=1	#742
2	README: list the CATSTACK_DRAFTER_CORE flag	#743	👈

[cursor]

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: serverGenReqId_b858d59c-1a99-46c0-8120-1444177e7ce9)

[cursor]

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: serverGenReqId_5952fa91-205b-43c9-8fee-0074bca9601e)