Repository navigation
fix(benny): say Slack automations can't be created here - #55
Conversation
Antigravity has no surface that creates a Slack-triggered automation. Drop the nameless draft and handoff steps. Co-authored-by: Kaitian Xie <caelaxie@users.noreply.github.com>
|
Harness proof for head
|
caelaxie
left a comment
There was a problem hiding this comment.
verdict: changes requested (comment review, same-account author).
content takes the issue's fallback fix cleanly: the nameless draft/approval/handoff steps are gone from FOR_AGENTS.md, setup-benny and both templates, and the plain "can't be created in this harness" line replaces them. Closes #54 linkage is right, not a draft.
two things before merge:
- setup-benny/SKILL.md:191 adds the same sentence a third time under Creation boundary. First-time creation already says it; drop the append and keep upstream's line as it was.
- no harness proof yet. body says a proof comment follows; need
agy plugin install+ list on head 1c01031 showing pstack and the embedded deslop/control-cli/control-ui skills, plus green Validate plugin (still running at review time).
merge once both land.
| ### Creation boundary | ||
|
|
||
| Never call a direct automation backend service or backend automation tool. Never use a browser URL that carries draft fields. | ||
| Never call a direct automation backend service or backend automation tool. Never use a browser URL that carries draft fields. The Slack automations can't be created in this harness. |
There was a problem hiding this comment.
duplicate of the First-time creation line. drop the appended sentence so this line stays as upstream/main had it.
The can't-be-created statement already stands in first-time creation. Drop the duplicate sentence appended to the creation boundary. Co-authored-by: Kaitian Xie <caelaxie@users.noreply.github.com>
|
Harness proof for head agy
CI: Validate plugin succeeded on this head. https://github.com/pstack-ports/agy-pstack/actions/runs/41381575917 |
Closes #54
Antigravity has no surface that creates a Slack-triggered automation. The nameless draft, approval, and handoff steps are removed, and the setup says plainly that the Slack automations can't be created in this harness. The creation boundary line is unchanged from main.
Verification
Harness on
0d95110b33d7cabd2a188036139dc565254446eewith agy 1.4.12. Proof comment follows.