fix-slow-queries

原文涵盖的主题

• Fix Slow Queries
• 1. Establish the target and finish line
• 2. Find the actual database and rank the work
• 3. Trace each candidate to its behavior
• 4. Reproduce the baseline locally
• 5. Implement and prove both kinds of green
• 6. Verify the blast radius
• 7. Create the PR and carry it through checks

Deliver a measured improvement with preserved behavior and a reviewable PR whose latest commit passes checks. A list of suspicious SQL or an unverified rewrite is an intermediate result. Respect a narrower request for diagnosis only. Resolve the reported URL, environment, company/workspace, deployed revision, owning repository, and local checkout. Read its AGENTS.md and scoped rules. Paperclip and the private paperclip-cloud control plane have different rules. Work in a dedicated branch/worktree. Reuse suitable existing work; keep the checkout running a live server out of branch switching and benchmark setup. Select a bounded batch, usually the top two or three query families. Record deferred candidates so discovery does not turn into an unbounded rewrite. The finish line is: reproducible baseline, faster treatment, output/behavior proof, relevant regression coverage, and green checks on each final PR head. A concrete access or infrastructure blocker must be reported as incomplete. Read Cloud discovery when starting from a hosted workspace. Follow the chain from Paperclip Cloud fleet admin to the stack's Neon project, branch, endpoint, database, and runtime role. Record the corresp

这里只展示节选，请以完整原文和当前要求为准。