General Audit and Improvements #1
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/pi-harness-remediation"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR applies the findings from a full audit of the Pi harness configuration and brings the repository in line with Pi 0.80.7. The changes focus on security boundaries, extension correctness, reproducible tooling, and regression coverage.
Security and trust boundaries
chrome-devtools-mcp@1.6.0package and configured it to run offline from Pi-managed dependencies. This removes floatingnpx @latestexecution from startup.npm/andgit/) so credentials and generated machine state cannot be committed accidentally.pi-mcp-adapter's intended lazy connection behavior without modifying the upstream package.Rate-limit coordination
smart-rate-limitpersistence so parent sessions, subagents, and sibling processes coordinate through serialized, fail-closed file updates instead of racing on shared JSON state.Goal loop reliability
goal_verdictinactive while no goal is running and removed only that tool when the loop ends, avoiding accidental changes to unrelated tools.goal:requestintegration.Pantheon and Plannotator safety
/dev/fddoes not resolve to the underlying file path.Extension behavior and UI fixes
Skill and helper hardening
.gitfile support and regression coverage.Reproducible repository tooling
package.jsonand lockfile.scripts/check-tooling.mjsto verify runtime versions, exact Pi package sources, Chrome MCP configuration, lockfile integrity coverage, and the absence of tracked files under Pi-managednpm/orgit/backends.extensions/*/index.tsauto-discovery.Validation
npm ci --ignore-scriptsnpm auditwith zero vulnerabilities28b3d5f00etoc4706ac08f