feat(orchestrator): show firewall and hub rules in one table with hits

One rule table replaces the two lists: each allow, ask and deny rule shows its hits from the extracted dry-run matcher, ask patterns the matcher never grants read never granted instead of unused, and the table scrolls in its own container below 600 px. Tests run once on unify/skills-20261114 after the merge (operator order 2026-11-14).

🎯 Fix: 85 %
💥 Break: 10 %
💸 Tokens: 100 %
⏱️ Velocity: 103 %
🛡️ Security: 100 %
🏆 Score: 74
🚦 Gate: ⛔ fix 85 % < 90, break 10 % > 5; velocity 103 % > 100: ask the operator before the commit

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Kevin Veen-BirkenbachandClaude Opus 5.5 committed 2026-11-14 21:29:42 +00:00
1 parent 48f26b678a
commit 23a7d2dc1d
9 files changed
+377 -85

No files matched your search

+6 -2
View File
@@ -748,8 +748,12 @@ flowchart TD
### Phase 6: Firewall (S6)
- [x] The tab is called Firewall and lists hub rules, allow and deny
patterns and the settings permissions, grouped by tool and prefix as
read from the settings files.
patterns and the settings permissions in one rule table (Action, Tool,
Pattern, Scope, Source, Hits over 7 days) with Allow, Ask, Deny,
Sandbox and Signed filter chips and one folded group per source; hits
come from the ask ledger through the rule request dry-run matcher,
allow and deny rows show not seen, an ask row without hits is flagged
unused.
- [x] A rule or rule set applies to one agent, a named group or all agents.
- [x] A settings change is written only by the host executor after the
passkey check, only to a listed file, with a backup beside it; a forged,