Operating Rules

• Keep public PRs and issues below 20, with zero as the preferred release-lane target.
• Maintain 80/80 harness audit and 21/21 observability readiness after every GA-readiness batch.
• Do not publish release or social announcements until the GitHub release, npm/package state, billing state, and plugin submission surfaces are verified with fresh evidence.
• Do not treat closed stale PRs as discarded. Pair each cleanup batch with a salvage pass: inspect the closed diffs, port useful compatible work on maintainer-owned branches, and credit the source PR.
• Use Linear project documents/comments for project-level updates because project status updates are disabled in this workspace; create or update issues when a lane needs a durable execution owner.