chore: sync with cursor/plugins — feat(pstack): setup-pstack budget ask (max/xhigh/high/medium) (#366) - #41
Merged
github-actions[bot] merged 4 commits intoSep 13, 2026
Conversation
…gquery feat(third_party): add Google Cloud BigQuery plugin
…#366) * feat(pstack): setup-pstack budget ask (max/xhigh/high/medium) Step 3 of /setup-pstack asks for a budget first (unlimited, large, medium, small), rewrites the effort token of every real slug in the working table to the budget's target, clamps to the detected set within the same family, and then shows the roles for confirmation. Step 2 reads the recorded budget line and step 5 writes it. No version bump. Co-authored-by: lauren <poteto@users.noreply.github.com> * docs(pstack): mention the setup-pstack budget in README and setup guide Co-authored-by: lauren <poteto@users.noreply.github.com> * refactor(pstack): tighten setup-pstack step 3 to three short parts Drop the four-by-four example table, the repeated family and fast explanations, and the re-run essay. Keep the four budget labels, one remap rule with a one-line example, the confirm paragraph, and the budget line in the written rule. Co-authored-by: lauren <poteto@users.noreply.github.com> * fix(pstack): setup-pstack step 3 rebuilds before the budget, keeps aliases, records the chosen budget Bugbot on cursor#366. The working table is built from the defaults first, on every run, so unlimited on a re-run restores the default efforts. The carry-over set names alias roles. Step 5 says the budget line holds the chosen label and target effort. Co-authored-by: lauren <poteto@users.noreply.github.com> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com>
…tup-pstack-budget-ask-max-xhigh-high-medium-36-3-commits # Conflicts: # README.md
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
3 participants
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.
Upstream changes
5bf2b15 feat(pstack): setup-pstack budget ask (max/xhigh/high/medium) (cursor#366)
9d3fc71 Merge pull request cursor#355 from cursor/minu/plugin-google-cloud-bigquery
00ea25b feat(third_party): add Google Cloud BigQuery plugin
Automated sync via sync-upstream workflow