# Dirty Work Triage Plan — 2026-06-06

## Current Status

User will delete the scratch note; it no longer appears in `git status --short`.

Questionnaire extension work is complete and marked Done in:

- `tickets/active/2026-06-06-interactive-pi-questionnaire-extension.md`

Subagent reviewers inspected the major dirty-work groups to conserve main context.

## Proposed Commit / Review Groups

### Group 1 — Questionnaire extension

Status: ready for path-limited review/commit.

Files:
- `.pi/extensions/questionnaire.ts`
- `.pi/extensions/README.md`
- `tickets/active/2026-06-06-interactive-pi-questionnaire-extension.md`

Review findings:
- Scoped and coherent.
- Core requirements appear implemented.
- Smoke verification passed and user ran `/questionnaire-demo` successfully.
- Known follow-up: possible duplicated UI implementation inside extension; acceptable now but should be refactored later if it becomes maintenance burden.

Suggested commit message:

```text
Add interactive questionnaire Pi extension
```

### Group 2 — SearxNG deployment documentation

Status: logical group, but needs checklist cleanup before commit.

Files:
- `docs/server-change-log.md`
- `runbooks/searxng-homelab.md`
- `tickets/active/2026-06-06-add-searxng-service.md`
- `tickets/active/2026-05-17-safe-web-browsing-and-prompt-injection-guard.md`
- `tickets/artifacts/2026-06-06-add-searxng-service/`
- `tickets/artifacts/2026-05-17-safe-web-browsing-and-prompt-injection-guard/`

Review findings:
- Documents a real Proxmox LXC `103` SearxNG deployment.
- Runbook/change-log/rollback notes are present.
- DNS/Tailscale/TLS are incomplete follow-ups.
- Ticket checklist appears stale: some completed work remains unchecked.
- No live infra verification was performed during triage.

Suggested next action:
- Update/check the SearxNG ticket to match documented reality without pretending DNS/Tailscale/TLS are complete.
- Optionally verify live state before commit if desired.

Suggested commit message:

```text
Document SearxNG homelab deployment
```

### Group 3 — Nimrod process/framework improvements

Status: logical but broad; may be split into smaller commits.

Core files:
- `AGENTS.md`
- `docs/context-hygiene-and-handover.md`
- `docs/nimrod-memory-and-self-improvement.md`
- `docs/question-asking-policy.md`
- `docs/hybrid-task-routing.md`
- `docs/service-deployment-defaults.md`
- `docs/application-architecture-principles.md`
- `docs/devops-qrspi-framework.md`
- `docs/fresh-context-routing-test-plan.md`
- `docs/templates/handover-template.md`
- `docs/templates/terminated-agent-recovery-template.md`
- `infra/proxmox-registry.yaml`
- `state/locks/README.md`
- `systems/network-plan.md`
- related process tickets/artifacts

Review findings:
- Coherent process framework, but broad.
- `tickets/active/` now contains many Planned/Inbox tickets, conflicting with the 1–3 active execution rule.
- Some follow-up tickets may be backlog rather than truly active.
- Actual Proxmox registry remains scaffold-only.

Suggested split:
1. Startup/context/memory/question policy docs.
2. DevOps coordination scaffold and service defaults.
3. Fresh-context routing tests and artifacts.
4. Backlog/follow-up tickets.

Suggested commit messages:

```text
Refactor Nimrod startup and context hygiene docs
Add DevOps coordination and service deployment defaults
Add fresh-context routing test plan
```

## Policy Improvement Applied

Updated:
- `AGENTS.md`
- `docs/context-hygiene-and-handover.md`

New emphasis:
- conserve context aggressively;
- use subagents proactively for discovery/review;
- avoid large shell-output dumps in the main context;
- if unrelated dirty work exists, stop/triage or isolate new implementation work rather than adding to the same dirty tree.

## Immediate Recommended Order

1. Commit or otherwise isolate **Group 1: Questionnaire extension** first, since user confirmed complete.
2. Clean/check **Group 2: SearxNG ticket checklist**, then commit operational docs.
3. Split/review **Group 3: Nimrod framework** into smaller commits or one documented process commit if user prefers speed.
4. Address active-ticket overload by moving some Planned/Inbox tickets out of `tickets/active/` or revising the ticket directory convention.