garden-inbox

原文涵盖的主题

• Garden Inbox
• Safety contract
• Inputs
• 1. Scan
• 2. Confirm
• 3. Apply accepted selections
• Verify the bundled logic

Use the bundled script for every stage. Keep the workflow strictly ordered: scan → confirm → apply. Treat scan as read-only. It may read inbox, workspace, close-readiness, and local Git metadata only. Treat confirm as a confirmation-card write only. It must not archive inbox entries or mutate issue fields, branches, or workspaces. Run apply only after a resolved requestcheckboxconfirmation interaction. It archives only accepted option IDs that also occur in the originating candidates.json. Remember that inbox archive state is per-user presentation state. It is reversible and does not change the underlying issue. Never substitute issue status changes, branch deletion, workspace cleanup, or issue deletion for inbox archiving. Require PAPERCLIPAPIURL and PAPERCLIPAPIKEY. The script strips a trailing /api from the URL. It resolves the target user from the run JWT payload's responsibleuserid; use --user-id only for an explicit target override. Use a run-owned output directory when available: Inspect garden-inbox-report.md and candidates.json. The report groups every inbox row into exactly one bucket: The scan reads Mine separately for each included issue status so the endpoint's global

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