chore(pi): migrate agent setup

## Summary Migrate the repository's Kilo agent setup to Pi project resources while keeping the existing Kilo files for rollback. This adds Pi settings, Forgejo MCP wiring, Nix-backed pi-lens Rust LSP config, prompt templates, skills, subagent definitions, permission-system config, and a project guardrail extension that ports the RGR/Forgejo/toolchain gates. ## Type of change - [ ] feat — new capability - [ ] fix — bug fix - [ ] docs — documentation only - [ ] refactor — internal cleanup, no behaviour change - [ ] test — test-only addition - [x] chore — tooling, deps, CI ## Verification - [ ] `cargo test --workspace --all-targets` - [ ] `cargo clippy --workspace --all-targets -- -D warnings` - [ ] `cargo fmt --all -- --check` - [ ] `cargo deny check` (when bumping dependencies) - [ ] Manual smoke test against a dev gateway (when changing the review pipeline or webhook surface) - [x] Loaded Pi skills/prompts/extensions via Pi internals: 7 skills, 9 prompts, guardrail extension with 10 tools - [x] Validated JSON/frontmatter and project Pi resource discovery - [x] Ran `git diff --cached --check` - [x] Ran LSP diagnostics for `.pi/extensions/auto-review-guardrails.ts` Rust/product gates were skipped because this change only adds agent/tooling configuration and documentation; no Rust crates, Nix derivations, CI jobs, release artifacts, or product runtime behavior changed. ## Pre-merge checklist - [x] Commit titles follow conventional commits; the release PR generates changelog notes from conventional commits - [x] Public surface changes have rustdoc on the new items — not applicable (no Rust public API) - [x] If the change touches a documented threat (T#) in `docs/THREAT-MODEL.md`, the corresponding red-team test in `crates/ar-review/tests/red_team_*.rs` has been updated or extended — not applicable - [x] If the change touches a metric, the rules pack (`deploy/prometheus/auto_review.rules.yaml`) and dashboard (`deploy/grafana/auto_review.dashboard.json`) still pass their contract tests — not applicable ## Related Based on `docs/PI-MIGRATION-RESEARCH.md`.

jwilger commented

2026-05-14 07:13:55 -07:00

Owner

Summary

Migrate the repository's Kilo agent setup to Pi project resources while keeping the existing Kilo files for rollback. This adds Pi settings, Forgejo MCP wiring, Nix-backed pi-lens Rust LSP config, prompt templates, skills, subagent definitions, permission-system config, and a project guardrail extension that ports the RGR/Forgejo/toolchain gates.

Type of change

feat — new capability
fix — bug fix
docs — documentation only
refactor — internal cleanup, no behaviour change
test — test-only addition
chore — tooling, deps, CI

Verification

cargo test --workspace --all-targets
cargo clippy --workspace --all-targets -- -D warnings
cargo fmt --all -- --check
cargo deny check (when bumping dependencies)
Manual smoke test against a dev gateway (when changing the review pipeline or webhook surface)
Loaded Pi skills/prompts/extensions via Pi internals: 7 skills, 9 prompts, guardrail extension with 10 tools
Validated JSON/frontmatter and project Pi resource discovery
Ran git diff --cached --check
Ran LSP diagnostics for .pi/extensions/auto-review-guardrails.ts

Rust/product gates were skipped because this change only adds agent/tooling configuration and documentation; no Rust crates, Nix derivations, CI jobs, release artifacts, or product runtime behavior changed.

Pre-merge checklist

Commit titles follow conventional commits; the release PR generates changelog notes from conventional commits
Public surface changes have rustdoc on the new items — not applicable (no Rust public API)
If the change touches a documented threat (T#) in docs/THREAT-MODEL.md, the corresponding red-team test in crates/ar-review/tests/red_team_*.rs has been updated or extended — not applicable
If the change touches a metric, the rules pack (deploy/prometheus/auto_review.rules.yaml) and dashboard (deploy/grafana/auto_review.dashboard.json) still pass their contract tests — not applicable

Based on docs/PI-MIGRATION-RESEARCH.md.

jwilger added 1 commit

chore(pi): migrate agent setup

CI / Verify PR with nix flake check (pull_request) Successful in 3m34s

Details

CI / Request auto_review semantic review (pull_request) Successful in 2s

CI / Build PR artifacts (no token) (pull_request) Successful in 3s

CI / Publish PR artifact packages (pull_request) Successful in 1s

auto_review auto_review: no findings

ea6621e715

Add Pi project settings, prompts, skills, subagents, Forgejo MCP, Nix-backed pi-lens LSP configuration, and project guardrail extension parity for the previous Kilo setup.

Validation: loaded Pi skills/prompts/extensions via Pi internals, checked JSON/frontmatter, ran git diff --cached --check, and lsp diagnostics reported no TypeScript issues for the guardrail extension.

auto-review approved these changes

2026-05-14 07:18:03 -07:00

auto-review left a comment

This PR migrates the Kilo agent setup to Pi project resources, adding various configurations and extensions while retaining existing Kilo files for rollback. The changes appear to be well-structured and align with the project's goals, making it safe to merge.

jwilger merged commit 825c123442 into main

2026-05-14 07:22:24 -07:00

jwilger referenced this pull request from a commit

2026-05-14 07:22:26 -07:00

chore(pi): migrate agent setup (#195)

Rows
Columns

chore(pi): migrate agent setup #195

Summary

Type of change

Verification

Pre-merge checklist

Related