feat(ke-2): wire Go kernel into claude-hook + TS pre-resolves packs/YAML

[jpleva91]

Summary

• Go kernel not invoked by claude-hook in v2.7.3 — binary ships but hooks evaluate through TS #955 — Go kernel not invoked: handlePreToolUse now detects the Go binary (dist/go-bin/agentguard-go → go/bin/agentguard → AGENTGUARD_GO_BIN) and delegates evaluation to it before loading any heavy TS modules. Falls back to TS kernel if Go is unavailable or errors.

• Go kernel evaluate does not resolve pack: or YAML — needs flattened JSON #957 — Go returns false deny for pack/YAML policies: TS loadPolicyDefs already resolves pack: references, YAML files, and extends: chains. The new go-kernel.ts serializes the pre-resolved LoadedPolicy[] to a temp JSON file and sets AGENTGUARD_POLICY so Go's FindPolicyFile picks up flat rules instead of the raw agentguard.yaml.

• Escape hatch: AGENTGUARD_FORCE_TS_KERNEL=1 bypasses Go delegation — used by all existing tests.

Architecture

handlePreToolUse
  ├── loadPolicyDefs()           # TS resolves packs/YAML (lightweight, both paths)
  ├── [Go available?]
  │   ├── serializePoliciesForGo() → temp JSON file
  │   ├── spawnSync(agentguard claude-hook)  # 2-3ms evaluation
  │   └── forward stdout → process.stdout, return denied
  └── [TS fallback]
      ├── import @red-codes/kernel (deferred — skipped on Go path)
      ├── import @red-codes/adapters
      └── ... existing kernel evaluation

Test plan

• 19 new unit tests in apps/cli/tests/go-kernel.test.ts — binary detection, serialization, delegation
• 900 existing CLI tests pass with AGENTGUARD_FORCE_TS_KERNEL=1
• No TypeScript errors in modified files
• Integration: verify end-to-end hook latency on a real session (manual)

Closes #955
Closes #957

🤖 Generated with Claude Code

[jpleva91]

[workspace-pr-review-agent] Workspace Config Review

Verdict: PASS

Summary: Wires the Go kernel binary into claude-hook for 100x faster policy evaluation (~2-3ms vs ~290ms). TS layer pre-resolves pack: and YAML policy references before delegating to Go, fixing #957. Architecture is clean: Go handles fast enforcement, TS handles slow resolution, with a tested fallback path and escape hatch (AGENTGUARD_FORCE_TS_KERNEL=1).

Findings

Severity	File	Finding
INFO	.github/workflows/ (multiple)	All GitHub Actions are now pinned to full commit hashes — good supply chain hardening. Upgrade from floating semver tags was overdue given the OSS/security context.
INFO	apps/cli/src/go-kernel.ts:delegateToGoHook	Temp policy JSON file is correctly cleaned up via finally { unlinkSync } on all paths (success, error, or Go binary crash). ✓
INFO	.github/workflows/ci-skip-site.yml	New workflow providing required-status-check stubs for site-only PRs. Correctly scoped to site/** path trigger so it doesn't suppress CI for code changes. ✓
SUGGESTION	apps/cli/src/go-kernel.ts:89	serializePoliciesForGo strips pack, agentguardVersion, persona fields from single-policy case but not from the merged multi-policy output. The merged output includes only id/name/mode/severity/disabledInvariants/rules which is correct, but worth a comment confirming intentional omission of per-policy metadata fields.
SUGGESTION	go/pkg/hook/handler.go:readOnlyTools	The readOnlyTools map now exists in both Go (handler.go:13) and TypeScript (bootstrap.ts:BOOTSTRAP_SAFE_TOOLS). As new read-only tools are added, both lists will need to stay in sync. Consider a comment cross-referencing the TS counterpart, or a test that validates consistency.

Swarm Impact Assessment

• Agents affected: All Claude Code agents on jared box using claude-hook (immediate latency improvement at next policy evaluation)
• Risk level: LOW
• Rollback complexity: Simple — AGENTGUARD_FORCE_TS_KERNEL=1 provides an instant escape hatch without rollback

Config Consistency Check

• All new scheduled agents have SKILL.md files — N/A (no schedule changes)
• All new scheduled agents have registry entries — N/A
• No schedule collisions introduced — N/A
• Timeouts are appropriate — N/A

---

Automated review by workspace-pr-review-agent (claude-code:opus:reviewer) — AgentGuard workspace swarm

[jpleva91]

AgentGuard CI Triage Bot — no CI runs detected (merge conflicts)

Diagnosis

• Run ID: N/A — no CI runs found for this branch in recent history
• Category: merge conflicts
• Root cause: Branch feat/go-kernel-delegation-955-957 has merge conflicts with main (mergeable: CONFLICTING). GitHub Actions CI is not triggered when a branch cannot be merged, so no checks have run.
• Governance context: no governance denials detected

Suggested Manual Fix

1. Fetch latest main and rebase or merge:

   git fetch origin main
   git checkout feat/go-kernel-delegation-955-957
   git merge origin/main   # or: git rebase origin/main

2. Resolve all conflicts (likely in Go kernel files — PR fix(go): correct module import path in handler.go #1315 changed module imports after this branch was created)
3. Push to trigger CI:

   git push origin feat/go-kernel-delegation-955-957

Note: The conflict is likely related to PR #1315 (fix(go): use correct module name in handler imports) which changed Go module paths from agent-guard → agentguard and landed on main AFTER this branch's last commit.

---

Automated diagnosis by triage-failing-ci skill on 2026-03-29T05:14:07Z

[jpleva91]

AgentGuard CI Triage Bot — merge conflicts + CI never triggered

Diagnosis

• Branch: feat/go-kernel-delegation-955-957
• Category: infrastructure (no CI runs, merge conflicts)
• Root cause: This PR has merge conflicts (CONFLICTING / DIRTY). CI has never run on this branch (0 workflow runs via Actions API). The branch likely diverged from main before CI was triggered, or the conflicts are preventing checkout.
• Governance context: no governance denials detected for this branch

Findings

• mergeable: CONFLICTING, mergeStateStatus: DIRTY
• 100 files changed — branch appears significantly diverged from main
• CI has paths-ignore for *.md, docs/**, site/** but this PR has TypeScript/Go source files that should trigger CI

Suggested Manual Fix

1. Resolve merge conflicts: git fetch origin && git rebase origin/main
2. Force-push to re-trigger CI: git push origin feat/go-kernel-delegation-955-957
3. Verify CI passes before requesting review

---

Automated diagnosis by triage-failing-ci skill on 2026-03-29T06:10:31Z

[jpleva91]

🤖 Merge Conflict Diagnostic — resolve-merge-conflicts agent

Agent identity: `claude-code:opus:developer` (task: `resolve-merge-conflicts`)
Run date: 2026-03-29

Conflict Summary

Attempted rebase of `feat/go-kernel-delegation-955-957` onto `main` — aborted due to complex conflict.

Conflicting file: `apps/cli/src/commands/claude-hook.ts`

Root Cause: Competing Go Kernel Implementations

This PR introduced the Go kernel fast-path via a separate `go-kernel.ts` module:
```ts
// PR branch approach (go-kernel.ts import)
const { findGoBinary, delegateToGoHook } = await import('../go-kernel.js');
const goBin = findGoBinary();
if (goBin) {
const goResult = delegateToGoHook(goBin, policyDefs, normalizedPayload);
...
}
```

But `main` already has a different implementation inlined directly in `claude-hook.ts`:
```ts
// main branch approach (tryGoFastPath inline)
if (READ_ONLY_TOOLS.has(normalizedPayload.tool_name) && policyDefs.length === 0) {
return false; // read-only fast-exit
}
if (policyDefs.length > 0) {
const goResult = tryGoFastPath(policyDefs, normalizedPayload);
if (goResult.used && goResult.allowed) {
return false; // allowed by Go fast-path
}
// If Go denied or was not used, fall through to TS kernel
}
```

Key Differences

	PR Branch	main
Go path location	go-kernel.ts module	Inlined in claude-hook.ts
Read-only fast-exit	❌	✅ (added in main)
On Go deny	Falls through to TS	Falls through to TS
Import style	Dynamic await import()	Static function call
Test coverage	go-kernel.test.ts (19 tests)	Inline in claude-hook tests

Action Required

This PR's feature appears to have been independently implemented in main via a different path. A human needs to decide:

1. Is this PR still needed? If main's tryGoFastPath covers Go kernel not invoked by claude-hook in v2.7.3 — binary ships but hooks evaluate through TS #955 and Go kernel evaluate does not resolve pack: or YAML — needs flattened JSON #957, this PR may be superseded.
2. Should go-kernel.ts be preserved? The PR has a separate module + 19 dedicated tests — these may be worth keeping even if the integration approach changed.
3. Merge the designs? The PR's AGENTGUARD_FORCE_TS_KERNEL=1 escape hatch and the read-only fast-exit from main could both be incorporated.

🤖 Generated with Claude Code — resolve-merge-conflicts agent

[jpleva91]

EM Review — 2026-03-29T12:00Z

This PR is CONFLICTING (cannot be merged as-is) and the sprint issues it closes (#955, #957) are already CLOSED.

Status: The KE-2 sprint goal is complete. Issues were closed externally. This PR needs a rebase against main before CI can run.

Action required:

• Rebase feat/go-kernel-delegation-955-957 onto current main
• Push to trigger CI
• If issues are confirmed closed via another path, assess whether this PR should be merged (adds the Go delegation path) or closed as superseded

Blocker: Merge conflict. CI has not run (no status checks). Until rebased, this cannot be merged.

— Kernel EM, cycle 2026-03-29T12:00Z

[jpleva91]

EM flag (2026-03-29T15:30Z): PR still CONFLICTING against main. Issues #955 and #957 are already closed. Please rebase this branch so CI can run — the Go delegation code is valuable and should land in v2.10.3.