[migmartri]

Summary

Enable Pi session tracing in this repository: add the managed Pi extension (.pi/extensions/chainloop-trace.ts) and regenerate the Claude Code, Cursor and OpenCode hook/plugin configurations, with the Claude Code and Cursor hook commands guarded so they no-op when the chainloop CLI is not on PATH and the OpenCode plugin taught the OpenCode 2.x tool-result shape.

Refs PFM-8009 (Trace: normalize Pi cache token totals) and parent PFM-7995 (define cache accounting and prevent token overcounting across providers). Builds on #3704 (Pi provider support).

[chainloop-platform]

PR validation — ✅ 3 passing

Status	Policy	Material	Messages
✅ Passed	pr-min-approvals	pr-info	-
✅ Passed	pr-description-required	pr-info	-
✅ Passed	pr-user-story-linked	pr-info	-

_{View attestation ↗}

AI Session Checks — ⏭️ bypassed by label

AI Coding Session Check Bypassed

This PR carries the skip-ai-session label, so the AI coding session check was bypassed.

Learn more about Chainloop Trace.

Security Checks — ✅ 6 passing

✅ secret-scan

Status	Policy	Messages
✅ Passed	secrets-detection	-

✅ sast-scan

Status	Policy	Messages
✅ Passed	owasp-top10-2025	-
✅ Passed	sast	-
✅ Passed	cwe-top25	-
✅ Passed	cwe-top26-40-cusp	-

✅ iac-scan

Status	Policy	Messages
✅ Passed	iac-misconfiguration	-

Scans not applied (2)

Scan	Reason
vulnerability-scan	no manifest/lockfile changed
github-actions-scan	no workflow files changed

_{View attestation ↗}

Security context

✅ Nothing this change touches has a recorded security-fix history.

_{View in Chainloop ↗ · How this works ↗}

---

Powered by Chainloop and Chainloop Trace

[cubic-dev-ai]

No issues found across 4 files

_{View guided diff | Re-trigger cubic}

[waveywaves]

Thanks for adding Pi tracing here. I reviewed the changes and didn’t find a code issue. The Pi extension matches the CLI template, the OpenCode plugin matches its tested fixture, and the focused hook tests pass. I wasn’t able to test the full Pi edit, commit, and push flow in this review.

When you have a chance, could you add a short PR description and link the relevant issue or user story? That would help reviewers understand the change. A formal approval will still be needed before merge.