chore(coordination): clarify Cursor write access (org app has it; runtime config issue)#77
Merged
Conversation
…ntime may use wrong identity Diagnosis of Cursor's 2026-05-29 daily-status 403 errors: org-installed Cursor app has contents:write + pull_requests:write on all repos. The 403 is either from pushing to main (branch-protected) or runtime using cursor[bot] GitHub Actions identity (permission: none) instead of the org-installed app token. Pattern for Cursor: clone, create cursor/<branch>, push branch, gh pr create. Direct main push will always 403 — that's doctrine v6 protection working correctly. Signed-off-by: Stephen Paul Lutar JR <stephen@szlholdings.com>
stephenlutar2-hash
added a commit
that referenced
this pull request
May 30, 2026
## Summary Adds `coordination/CURSOR_READ_THESE_TWO_FIRST.md` so Cursor isn't lost across 11 open coordination PRs. ## Why 11 open coordination PRs (#71, #72, #73, #75, #76, #77, #78, #79, #80, #82, #83) — Cursor needs a single canonical entry point. ## What it does - Points Cursor at **#82** (canonical 30-day operational plan, supersedes #71/72/73/75/77/78/79/80) - Points Cursor at **#83** (canonical theorems plan, supersedes #78/79/80) - Includes the **sorry-count reconciliation: 7 not 6** (PhD audit ground truth) - Doctrine v6 quick-reference - PR proxy pattern explanation for `cursor[bot]` `permission: none` issue - Sign-off pattern for all Cursor commits ## Doctrine - No marketing superlatives - No emoji in `## ###` headers - Signed off with `-s` - Honest sorry count (7), honest declaration count (217), honest TH10 status (axiom-structured) ## Founder-approved Approved 2026-05-29 by Stephen Lutar. Signed-off-by: Stephen Lutar <stephen@szlholdings.com> Co-authored-by: Perplexity Computer <agent@perplexity.ai>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cursor's 2026-05-29 daily status reported 403s pushing to .github and agi-forecast. I verified the org installation:
cursorapp hascontents: write+pull_requests: write+workflows: writeon ALL repos (repository_selection: all). The 403 is either (a) pushing directly to main (blocked by branch protection, correct doctrine v6) or (b) Cursor runtime using the wrong identity (cursor[bot]Actions bot haspermission: none).See coordination/CURSOR_WRITE_ACCESS_CLARIFICATION.md for the recommended pattern (clone → feature branch → push → gh pr create) and the founder-side check (confirm Cursor runtime uses the org app token, not the Actions bot).