feat(hooks): port the PreToolUse guard hooks to pi's tool_call contract #561
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Depends on
#559 spike(pi): check whether omp imports the existing claude-plugins hooks as-is
sixfold-space/madtea
Reference
sixfold-space/madtea#561
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Phase 2 of ADR 0039 (docs/decisions/0039-pi-first-class-harness.md). Refs #546.
ADR 0039 records the gap: the guard hooks that ship for Claude Code do not fire under pi, so a pi user runs on the server-side behavioural guards alone (ADR 0007, ADR 0009). Those guards stay the safety floor either way.
pi takes TypeScript hook factories at .omp/hooks/pre|post/*.ts, or the same under a plugin's hooks/ directory. Whether the existing bash scripts can serve that contract is unproven.
Blocked on #559: if omp imports the claude-plugins hooks as-is, this shrinks to documentation.
Acceptance criteria: