@jaguilar87/gaia 5.0.9 → 5.0.10

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.
Files changed (32) hide show
  1. package/.claude-plugin/marketplace.json +2 -2
  2. package/.claude-plugin/plugin.json +1 -1
  3. package/CHANGELOG.md +2 -0
  4. package/bin/README.md +4 -2
  5. package/bin/cli/_install_helpers.py +0 -3
  6. package/bin/cli/brief.py +32 -4
  7. package/bin/cli/cleanup.py +304 -4
  8. package/bin/cli/doctor.py +0 -4
  9. package/bin/cli/uninstall.py +20 -0
  10. package/dist/gaia-ops/.claude-plugin/plugin.json +1 -1
  11. package/dist/gaia-ops/hooks/modules/core/plugin_setup.py +0 -5
  12. package/dist/gaia-ops/hooks/modules/security/capability_classes.py +83 -6
  13. package/dist/gaia-ops/hooks/modules/security/inline_ast_analyzer.py +237 -0
  14. package/dist/gaia-ops/hooks/modules/security/mutative_verbs.py +410 -0
  15. package/dist/gaia-ops/hooks/modules/tools/bash_validator.py +177 -20
  16. package/dist/gaia-ops/skills/security-tiers/SKILL.md +1 -1
  17. package/dist/gaia-security/.claude-plugin/plugin.json +1 -1
  18. package/dist/gaia-security/hooks/modules/core/plugin_setup.py +0 -5
  19. package/dist/gaia-security/hooks/modules/security/capability_classes.py +83 -6
  20. package/dist/gaia-security/hooks/modules/security/inline_ast_analyzer.py +237 -0
  21. package/dist/gaia-security/hooks/modules/security/mutative_verbs.py +410 -0
  22. package/dist/gaia-security/hooks/modules/tools/bash_validator.py +177 -20
  23. package/gaia/briefs/__init__.py +4 -0
  24. package/gaia/briefs/store.py +91 -0
  25. package/hooks/modules/core/plugin_setup.py +0 -5
  26. package/hooks/modules/security/capability_classes.py +83 -6
  27. package/hooks/modules/security/inline_ast_analyzer.py +237 -0
  28. package/hooks/modules/security/mutative_verbs.py +410 -0
  29. package/hooks/modules/tools/bash_validator.py +177 -20
  30. package/package.json +1 -1
  31. package/pyproject.toml +20 -1
  32. package/skills/security-tiers/SKILL.md +1 -1
@@ -911,6 +911,57 @@ class BashValidator:
911
911
  reason="Safe by elimination (not blocked, not mutative)",
912
912
  )
913
913
 
914
+ def _is_ungranted_t3_component(
915
+ self, component: str, session_id: str
916
+ ) -> bool:
917
+ """Classify a chain component as ungranted-T3 WITHOUT minting or consuming.
918
+
919
+ Returns True when the component is a T3 (mutative-verb or
920
+ flag-dependent) operation for which NO active grant exists -- i.e. the
921
+ component would, on its own, be blocked pending approval. This is a
922
+ read-only probe used by the chain COMMAND_SET intake (AC-8) to decide
923
+ whether >= 2 sub-commands need grouping under ONE consent, BEFORE any
924
+ per-component minting happens.
925
+
926
+ It deliberately does NOT call decide_t3_outcome (no pending minted) and
927
+ does NOT consume any grant (match_command_set_grant /
928
+ check_approval_grant are pure lookups; consumption happens later in the
929
+ real _validate_single_command pass at retry). A component that already
930
+ matches a COMMAND_SET or semantic grant is treated as NOT ungranted, so
931
+ it is excluded from a fresh batch.
932
+ """
933
+ component = component.strip()
934
+ if not component:
935
+ return False
936
+
937
+ # Is this T3 (mutative verb or flag-dependent mutation)?
938
+ detect = detect_mutative_command(component)
939
+ is_t3 = detect.is_mutative
940
+ if not is_t3:
941
+ flag_result = classify_by_flags(component)
942
+ if (
943
+ flag_result is not None
944
+ and flag_result.outcome == FLAG_MUTATIVE
945
+ and not flag_result.command_family.startswith("git_")
946
+ ):
947
+ is_t3 = True
948
+ if not is_t3:
949
+ return False
950
+
951
+ # Already covered by an active grant? Then it is NOT ungranted -- exclude
952
+ # it from a fresh batch (pure lookups, no consumption).
953
+ try:
954
+ if match_command_set_grant(component) is not None:
955
+ return False
956
+ except Exception:
957
+ pass
958
+ try:
959
+ if check_approval_grant(component, session_id=session_id) is not None:
960
+ return False
961
+ except Exception:
962
+ pass
963
+ return True
964
+
914
965
  def _validate_compound_command(
915
966
  self,
916
967
  components: List[str],
@@ -918,9 +969,68 @@ class BashValidator:
918
969
  session_id: str = "",
919
970
  agent_type: str = "",
920
971
  ) -> BashValidationResult:
921
- """Validate a compound command (multiple components)."""
972
+ """Validate a compound command (multiple components).
973
+
974
+ Chain COMMAND_SET intake (AC-8): when a chain ``a && b && c`` has TWO OR
975
+ MORE sub-commands that are ungranted T3, classifying them one-at-a-time
976
+ mints a single-signature pending for the FIRST and short-circuits -- so
977
+ one approval covers only the first sub-command and the next re-blocks
978
+ (the double-approval the user hit). To group them, a NON-MINTING
979
+ classification pass runs FIRST (``_is_ungranted_t3_component``); if >= 2
980
+ sub-commands are ungranted-T3 (and we are a subagent under the
981
+ orchestrator), ONE COMMAND_SET pending is minted over exactly those T3
982
+ sub-commands via ``decide_t3_outcome(command_set=...)``. One approval
983
+ then covers the chain; each sub-command is still consumed byte-for-byte
984
+ by its own signature at retry (no consent is widened -- the commands are
985
+ only grouped). Critically, the per-component minting path
986
+ (_validate_single_command) is NEVER entered for the batch, so no stray
987
+ single pendings are minted alongside the COMMAND_SET.
988
+
989
+ For every other shape (0 or 1 ungranted-T3, no orchestrator above, or a
990
+ component that is hard-blocked) the original per-component pass runs
991
+ unchanged: a hard block fails the chain fast, a lone T3 keeps the
992
+ singular grant path, and an all-granted/safe chain is allowed.
993
+ """
922
994
  logger.info(f"Compound command detected with {len(components)} components")
923
995
 
996
+ # NON-MINTING pre-pass: which components are ungranted T3? (AC-8)
997
+ if is_subagent and is_ops_mode():
998
+ ungranted_t3_idx = [
999
+ idx
1000
+ for idx, comp in enumerate(components)
1001
+ if self._is_ungranted_t3_component(comp, session_id)
1002
+ ]
1003
+ if len(ungranted_t3_idx) >= 2:
1004
+ chain_set = [
1005
+ {"command": components[idx].strip(), "rationale": ""}
1006
+ for idx in ungranted_t3_idx
1007
+ ]
1008
+ first_cmd = chain_set[0]["command"]
1009
+ first_detect = detect_mutative_command(first_cmd)
1010
+ verb = first_detect.verb or "command"
1011
+ category = first_detect.category or "MUTATIVE"
1012
+ native_ask_reason = (
1013
+ f"[T3_APPROVAL_REQUIRED] Chain of {len(chain_set)} T3 commands.\n"
1014
+ f"Commands:\n"
1015
+ + "\n".join(f" - {it['command']}" for it in chain_set)
1016
+ )
1017
+ logger.info(
1018
+ "Chain COMMAND_SET intake: %d T3 sub-commands grouped under "
1019
+ "one consent (chain=%s)",
1020
+ len(chain_set),
1021
+ " && ".join(it["command"][:30] for it in chain_set),
1022
+ )
1023
+ return decide_t3_outcome(
1024
+ first_cmd,
1025
+ verb=verb,
1026
+ category=category,
1027
+ has_orchestrator_above=True,
1028
+ native_ask_reason=native_ask_reason,
1029
+ session_id=session_id,
1030
+ agent_type=agent_type,
1031
+ command_set=chain_set,
1032
+ )
1033
+
924
1034
  component_results: List[BashValidationResult] = []
925
1035
  for i, component in enumerate(components, 1):
926
1036
  result = self._validate_single_command(
@@ -1385,6 +1495,7 @@ def decide_t3_outcome(
1385
1495
  native_ask_reason: str,
1386
1496
  session_id: str = "",
1387
1497
  agent_type: str = "",
1498
+ command_set: list | None = None,
1388
1499
  ) -> BashValidationResult:
1389
1500
  """Single decision point for the outcome of a T3 (state-mutating) command.
1390
1501
 
@@ -1416,34 +1527,68 @@ def decide_t3_outcome(
1416
1527
  native_ask_reason: Reason text for the native-ask fallback branch.
1417
1528
  session_id: Session ID for pending-approval scoping.
1418
1529
  agent_type: Originating agent name (for the sealed payload).
1530
+ command_set: Optional list of ``{command, rationale}`` dicts. When it
1531
+ carries MORE THAN ONE item, this T3 decision covers a chain
1532
+ (``a && b && c``) whose sub-commands are all T3, and the pending is
1533
+ minted as ONE COMMAND_SET envelope (the chain-intake path, AC-8)
1534
+ instead of a single semantic-signature pending. ONE user approval
1535
+ then covers the whole chain; each sub-command is still consumed
1536
+ byte-for-byte by its own signature at retry. A None / single-item
1537
+ set keeps the singular behaviour. Only honoured in the
1538
+ subagent-under-orchestrator branch (the native-ask branch has no
1539
+ COMMAND_SET concept).
1419
1540
 
1420
1541
  Returns:
1421
1542
  A blocked BashValidationResult (allowed=False, tier T3) whose
1422
1543
  block_response is either a "deny" (with approval_id) or an "ask".
1423
1544
  """
1545
+ # A genuine multi-command chain is a set of >= 2 items. Anything else
1546
+ # collapses to the singular path so we never mint a COMMAND_SET for one
1547
+ # command (mirrors _build_sealed_payload's is_command_set guard).
1548
+ _normalized_set: list = []
1549
+ if command_set:
1550
+ for _item in command_set:
1551
+ if isinstance(_item, dict) and _item.get("command"):
1552
+ _normalized_set.append(
1553
+ {
1554
+ "command": _item["command"],
1555
+ "rationale": _item.get("rationale", ""),
1556
+ }
1557
+ )
1558
+ is_chain_command_set = len(_normalized_set) > 1
1559
+
1424
1560
  if has_orchestrator_above:
1425
1561
  # Subagent-under-orchestrator: deny + persisted approval_id so the
1426
1562
  # orchestrator can run the approval cycle. Reuse an existing pending
1427
1563
  # approval on retry to avoid generating duplicates while the user reviews.
1428
- approval_id = _find_pending_in_db(session_id or "", command)
1429
- if approval_id:
1430
- logger.info(
1431
- "Reusing pending approval_id=%s for retry: %s",
1432
- approval_id, command[:80],
1433
- )
1434
- reason = build_t3_blocked_denial_message(
1435
- approval_id=approval_id,
1436
- command=command,
1437
- verb=verb,
1438
- category=category,
1439
- )
1440
- hook_deny = build_hook_permission_response("deny", reason)
1441
- return BashValidationResult(
1442
- allowed=False,
1443
- tier=SecurityTier.T3_BLOCKED,
1444
- reason=f"T3 {category.lower()} command: {command[:60]}",
1445
- block_response=hook_deny,
1446
- )
1564
+ #
1565
+ # For a COMMAND_SET chain the pending id is CONTENT-derived (matching the
1566
+ # plan-first intake), so a retry of the same chain produces the same id
1567
+ # and the fingerprint-dedup in insert_requested reuses the pending. The
1568
+ # singular reuse probe (_find_pending_in_db) matches a SINGLE command's
1569
+ # signature and must NOT be consulted for the chain -- it would match one
1570
+ # leftover single pending of a sub-command and degrade the chain back to
1571
+ # a single grant. So the chain path skips it entirely.
1572
+ if not is_chain_command_set:
1573
+ approval_id = _find_pending_in_db(session_id or "", command)
1574
+ if approval_id:
1575
+ logger.info(
1576
+ "Reusing pending approval_id=%s for retry: %s",
1577
+ approval_id, command[:80],
1578
+ )
1579
+ reason = build_t3_blocked_denial_message(
1580
+ approval_id=approval_id,
1581
+ command=command,
1582
+ verb=verb,
1583
+ category=category,
1584
+ )
1585
+ hook_deny = build_hook_permission_response("deny", reason)
1586
+ return BashValidationResult(
1587
+ allowed=False,
1588
+ tier=SecurityTier.T3_BLOCKED,
1589
+ reason=f"T3 {category.lower()} command: {command[:60]}",
1590
+ block_response=hook_deny,
1591
+ )
1447
1592
 
1448
1593
  # No existing pending -- insert via DB (D16: exclusive path).
1449
1594
  sealed_payload = _build_sealed_payload(
@@ -1451,13 +1596,25 @@ def decide_t3_outcome(
1451
1596
  verb=verb,
1452
1597
  category=category,
1453
1598
  agent_type=agent_type,
1599
+ command_set=_normalized_set if is_chain_command_set else None,
1454
1600
  )
1455
1601
  try:
1456
1602
  from gaia.approvals.store import insert_requested
1603
+ # COMMAND_SET chains use a CONTENT-derived id (deterministic over the
1604
+ # sub-command list) so a retry of the same chain reproduces the same
1605
+ # id and reuses the pending via fingerprint dedup -- identical to the
1606
+ # plan-first intake in handoff_persister. Singular T3 keeps uuid4.
1607
+ supplied_id = None
1608
+ if is_chain_command_set:
1609
+ from gaia.approvals.store import derive_command_set_id
1610
+ supplied_id = derive_command_set_id(
1611
+ [it["command"] for it in _normalized_set]
1612
+ )
1457
1613
  approval_id = insert_requested(
1458
1614
  sealed_payload,
1459
1615
  agent_id=agent_type or None,
1460
1616
  session_id=session_id or None,
1617
+ approval_id=supplied_id,
1461
1618
  )
1462
1619
  except Exception as _store_err:
1463
1620
  logger.warning(
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jaguilar87/gaia",
3
- "version": "5.0.9",
3
+ "version": "5.0.10",
4
4
  "description": "Multi-agent orchestration system for Claude Code - DevOps automation toolkit",
5
5
  "main": "index.js",
6
6
  "type": "module",
package/pyproject.toml CHANGED
@@ -1,6 +1,6 @@
1
1
  [project]
2
2
  name = "gaia"
3
- version = "5.0.9"
3
+ version = "5.0.10"
4
4
  description = "Multi-agent orchestration system for Claude Code - DevOps automation toolkit"
5
5
  requires-python = ">=3.11"
6
6
  license = {text = "MIT"}
@@ -12,7 +12,9 @@ readme = "README.md"
12
12
  [project.optional-dependencies]
13
13
  dev = [
14
14
  "pytest==8.3.5",
15
+ "pytest-cov>=5.0.0",
15
16
  "ruff>=0.4.0",
17
+ "pyyaml>=6.0",
16
18
  ]
17
19
 
18
20
  [tool.ruff]
@@ -32,4 +34,21 @@ include = ["gaia*"]
32
34
  testpaths = ["tests", "tools/scan/tests"]
33
35
  markers = [
34
36
  "parity: JS-Python CLI parity comparison tests",
37
+ "ci_subset: budget-bounded subset of L2/L3 (LLM) tests run in CI under a controlled token budget (brief #89 AC-6)",
38
+ ]
39
+
40
+ # Branch coverage (brief #89 AC-4): coverage is a DIAGNOSTIC to locate unexercised
41
+ # wiring in the security layer + entry points, NOT a metric-target / vanity gate.
42
+ # No fail_under threshold is set on purpose.
43
+ [tool.coverage.run]
44
+ branch = true
45
+ source = ["hooks/modules/security", "hooks"]
46
+
47
+ [tool.coverage.report]
48
+ show_missing = true
49
+ skip_covered = false
50
+
51
+ [dependency-groups]
52
+ dev = [
53
+ "cosmic-ray>=8.4.6",
35
54
  ]
@@ -42,7 +42,7 @@ The runtime, not this skill, enforces tiers. Three modules layer the decision:
42
42
 
43
43
  - `tiers.py` -- the `SecurityTier` enum (`T0_READ_ONLY`, `T1_VALIDATION`, `T2_DRY_RUN`, `T3_BLOCKED`) and `_classify_command_tier_cached` assign every command a tier.
44
44
  - `blocked_commands.py` -- pattern-matches irreversible commands and permanently denies them (exit 2, never approvable).
45
- - `mutative_verbs.py` -- CLI-agnostic detection of mutative verbs; drives the nonce / approval flow for T3.
45
+ - `mutative_verbs.py` -- CLI-agnostic detection of mutative verbs; drives the nonce / approval flow for T3. Includes script-file detection (Step 1d, `_check_script_file`): when a command is `<interpreter> <script-file>` (`python3 deploy.py`, `bash setup.sh`, `node migrate.js`) or `./script.ext`, the file is read and classified by its real invocations -- AST analysis for Python, the blocked/mutative regex layer for shells and other interpreters. A script that is missing, unreadable, or whose interpreter is unrecognized defaults to T3 (conservative). This prevents the evasion path where `<interp> <file>` bypasses the verb scanner because the filename token has no recognizable subcommand.
46
46
  - `composition_rules.py` -- `check_composition` / `classify_stage` classify pipe compositions (FILE_READ→EXEC_SINK, network→exec, decode→exec); triggers T3 on dangerous pipelines such as `file_to_exec`.
47
47
  - `flag_classifiers.py` -- `_classify_curl` / `classify_by_flags` detect flag-dependent mutations; triggers T3 on commands whose flags make them mutative (e.g., `curl -X POST`).
48
48