Version: 1.0
Date: 2026-09-23
Status: Complete. TFP-077 landed 2026-09-23 (8be5dd7). Reconciled with git 2026-09-29.
TestForge’s own UI assumes the person using it already knows what “crawl”, “introspect”, a Playwright suite, or a coverage tab mean. That’s a reasonable assumption for the developers who’ve been building it, but not for someone non-technical who lands on the running app cold.
A repo-claim-audit-style pass on README.md (Cowork session, 2026-09-23)
surfaced that the README itself had drifted from what TestForge had grown
into — separately, that same conversation noted there’s no in-app
equivalent explanation at all, for any audience. The actual help copy has
already been written and staged at docs/help-content-draft.md (plain
language, no unexplained jargon, covers what TestForge is, the five-step
flow, what each report tab means, and a short FAQ) — this ticket is about
building the UI around that content, not writing it again.
ui, docs, accessibility? icon button to the header (src/app/page.tsx:228-250),
placed at the far right of the existing logo/title row (ml-auto),
styled consistently with the existing indigo/zinc header treatment.src/app/_components/RunProgressOverlay.tsx (a props-driven overlay)
rather than introducing a new modal pattern into the codebase.docs/help-content-draft.md, already written in
plain language for a non-technical reader — convert its five sections
(what TestForge is, the step-by-step flow, the report-tab glossary,
things worth knowing, FAQ) into the panel’s content.src/app/_components/HelpPanel.tsx) wired into
page.tsx.docs/help-content-draft.md deleted once its content is live in the
component — its purpose (staging for review) is done at that point,
same as this repo’s other staging docs once integrated.? icon is visible on first load with no app state required
(works before any base URL or description is entered).docs/help-content-draft.md no longer exists in the tree once done.