Todo list

## Purpose

This is the short operational list of current Pentect work. Detailed requirements remain in the linked focused issues. Reconcile this list whenever an issue is opened, closed, or reprioritized.

## P0 — immediate blockers

No open P0 issue. Promote an issue here only when it blocks safe use of a currently supported path or blocks a release.

## P1 — reliability before expansion

- [ ] #1338 Separate OpenAI Privacy Filter cold start from the live request budget without restoring long request stalls.
- [ ] #1339 Add installation-to-runtime E2E coverage for the plugin system across supported platforms and failure modes.
- [ ] #352 Stabilize desktop and app integrations across startup, shutdown, recovery, and verified protected traffic. Keep this umbrella open; implement concrete findings in focused issues.

## P2 — hardening and evidence

- [ ] #711 Consolidated secret-input masking boundary audit
- [ ] #349 Document and verify Pentect own trust and network boundaries
- [ ] #348 Publish reproducible precision and recall measurements for secret detection
- [ ] #250 Expose useful value-free privacy metrics without leaking sensitive data

## P3 — deferred expansion and presentation

- [ ] #985 Modernize the interactive TUI
- [ ] #362 Add first-class OpenClaw support through an isolated provider overlay
- [ ] #351 Expand client support only through verified model-traffic boundaries
- [ ] #235 Improve the UI after diagnostics are reliable

## Separate design and roadmap trackers

- [ ] #221 Shared approval-engine design; intentionally deferred
- [ ] #123 Signed team-policy distribution; design only, with no implementation commitment
- [ ] #114 Long-term researched roadmap and compatibility evidence

## Maintenance rule

Keep this issue concise and English-only. Put implementation details, reproduction steps, design discussion, and acceptance criteria in focused issues. Remove completed or rejected work instead of leaving stale checklist entries. Concrete regressions come before umbrella work and new client expansion.

Start by reviewing the focused issues linked from this checklist and compare their current states with the P0–P3 sections. Reconcile the entries when work is opened, closed, or reprioritized, keeping implementation details in the focused issues; done means the tracker accurately reflects current priorities.

Written by the indexing model from the issue text.