Files

T

kami b1c0f88dee docs(backlog): add BACKLOG + QA plan template

Synthesize the five 2026-06-13 design specs and session memory into a
single outstanding-work list. Header rules: resolved items move to
RETRO.md; every finished feature gets a live-QA plan before it counts as
resolved. Add docs/qa/TEMPLATE.md as the observable-evidence QA form.

2026-06-14 14:51:22 +04:00

1.9 KiB

Raw Permalink Blame History

QA Plan: —

Status: DRAFT | RUNNING | PASSED | FAILED Run date / operator: BACKLOG item: <link/quote the §F entry this closes>

Preconditions

server build/branch: <jar/branch> — rebuild only with the server stopped (lazy classloading breaks otherwise)
llama-server + model: — note model-dependent behavior (strict templates, prompt-block emission)
external deps: <SearXNG / network / real router model / none>
config synced: ~/.config/correx matches examples/* + docs/schemas/* — stale copies cause silent bugs
fixtures/seed: <workspace, .correx/project.toml, prior session to resume, etc.>

Acceptance gate (one sentence)

The feature is correct iff .

Checks

Every row must name a recorded, observable signal — an event in the log, a CLI/log line, a TUI render, a file on disk, or the absence of an event. "It worked" is not evidence.

#	Action	Expected observable evidence	Result
1
2
3

Evidence sources: correx events <id> / GET /sessions/{id}/events (the log is the truth), server logs (MDC sessionId), the TUI render, files under the workspace, and correx replay <id> for determinism.

Out of scope (explicitly NOT covered this pass)

Disposition

PASS → MOVE the BACKLOG entry into RETRO.md with this plan's run date + the evidence cited above. Set Status: PASSED.
FAIL → file each failure as a numbered finding back into BACKLOG.md (action + exact repro + the signal that was wrong/missing), fix, then re-run only the failed checks. Set Status: FAILED until green.

1.9 KiB Raw Permalink Blame History