usebeeline 0.1.9 → 0.1.11

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -96,6 +96,8 @@ A Room and a corner are the same conversation surface with different permissions
96
96
 
97
97
  **A corner** is a fresh worktree, its own branch, one owning agent, and one fixed objective of at most 24 words. In it the agent works, commits, pushes the branch, runs `gh pr create`, and prints the pull request URL. It then waits for the server's own checks fact — not for whatever `gh` printed locally — and merges only when the checks passed and no human has put the corner on hold. The merge webhook archives the corner and reaps the worktree.
98
98
 
99
+ When Beeline reads that a Room's repository allows GitHub auto-merge, it warns a Workspace manager while they choose a reviewer and shows an inline notice when one is already set. The warning does not prevent setting a reviewer. GitHub merges a pull request with auto-merge turned on as soon as its checks pass, before Beeline asks the reviewer to look; turn off auto-merge in that repository's GitHub settings to protect reviewer approval.
100
+
99
101
  The corner receives a GitHub App token scoped to **that one repository**, installed as a worktree-local git credential helper. Your host credential stores are masked out of the sandbox — with one deliberate exception: the Trusty Squire session directory stays readable, so a routed agent shares your one signed-in browser and vault instead of standing up its own.
100
102
 
101
103
  **Direct messages** are strictly conversational: no repository binding, no corners.
@@ -173,6 +175,7 @@ Rooms run CodeGraph without a file watcher and keep source files read-only; only
173
175
  | `pr_checks_status` | Corners | Read checks, human hold, and PR/head-bound merge approval |
174
176
  | `post_artifact` | Everywhere | Upload one file (path or html/bytes) as an attachment |
175
177
  | `fetch_image` | Everywhere | Download one photograph into scratch for a data: embed |
178
+ | `download_attachment` | Everywhere | Download one message attachment into scratch by its 📎 id |
176
179
  | `create_schedule`, `list_schedules` | Everywhere | Run a prompt again later — interval minutes or a 5-field cron |
177
180
  | `update_schedule`, `delete_schedule` | Everywhere | Edit or delete any agent-created schedule in the Room |
178
181
  | `request_grant` | Everywhere | Ask the correct Room manager or resource owner for access |