Date: 2026-08-26
Scope: Establish TestForge as a local-only tool — remove the FastAPI/proxy backend, scope execution to Chromium, and decompose the three oversized source files
Status: Complete. Every Phase 16 ticket landed 2026-08-28 to 2026-09-17; see phase-16-implementation-backlog.md for commits. Reconciled with git 2026-09-29.
Phases 1–15 consolidated TestForge from two UIs onto the Next.js app. That work
left the repository asserting two incompatible things at once: that TestForge is
a local development tool run against a Dockerised Plane instance, and that it is
“ready for production cutover”. The execution model — POST /api/run accepts
arbitrary code, writes it to disk, and executes it with no authentication or
sandbox — is correct for the first reading and unacceptable under the second.
This phase resolves that contradiction in favour of local-only, and removes the structure that existed to support the other answer.
/api/run is accepted as intended behaviour under
this model and is documented as such..env.production, .env.staging, and DEPLOYMENT_CHECKLIST.md are removed.Amended 2026-10-27 (Emil; Phase 47 Decision 3,
phase-47-ci-integration-decision-record.md): “local-only” means TestForge
runs on the tester’s own machine or on their own team’s CI runner, for that
team alone — never as a shared service. In CI it starts no HTTP server, runs
only code it generated in that job or the team’s own restored site suite, and
takes credentials only from the pipeline’s secrets. Decision 2 (SaaS
deferred) is unchanged.
app.py, requirements.txt, and templates/index.html are removed.src/lib/backend-proxy.ts is removed.TESTFORGE_BACKEND_BASE_URL proxy branch is removed from
src/app/api/generate, /run, /crawl, /introspect, and /save-suite.TESTFORGE_BACKEND_BASE_URL and TESTFORGE_NEXT_UI_URL are removed from all
environment files and documentation.firefox and webkit projects are removed from playwright.config.ts.src/app/page.tsx and
src/app/api/run/route.ts into a shared src/lib/report/ module.src/app/page.tsx is split into section components under src/app/_components/.src/app/api/generate/route.ts and src/app/api/run/route.ts are split into
modules under src/lib/.src/lib/introspect/dom-snapshot.ts (673 lines), the function passed by
reference to Playwright’s page.evaluate. Playwright serializes only that
function’s own source text and runs it inside the browser’s isolated JS
context, with no access to this module’s scope — its ~18 nested helpers
cannot be extracted into importable files without throwing ReferenceError
at runtime. This is the only file in the repository under this exception.artifacts/ are untracked via git rm --cached.artifacts/ remains gitignored and is regenerated on demand.README.md states in its opening section that TestForge runs locally and
executes arbitrary code by design..env.example contains only variables the local tool actually reads.grep -r "TESTFORGE_BACKEND_BASE_URL" . returns no matches outside git history.npm run build and npm run lint pass.playwright.config.ts declares exactly one project.README.md start to finish produces a working
generate → run → report cycle with no browser-not-installed error.README.md describes TypeScript .spec.ts generation and Playwright CLI
execution, with no reference to Python, pytest, or pytest runs/ -v.README.md from clone to first run requires no undocumented step.README.md exists in package.json.wc -l reports no file over 500 lines under src/, with the one named
exception in Decision 5 (src/lib/introspect/dom-snapshot.ts).git ls-files artifacts | wc -l returns 0..gitattributes file normalises line endings.TEST_PLAN.md does not yet exist for this project and is created as part of
this phase, covering the generate, crawl, introspect, run, report, and export
flows currently exercised only by the automated suites.TEST_PLAN.md for: single-browser run
completion after the Chromium scoping; in-process execution after proxy
removal; and report rendering parity before and after decomposition.