Version: 1.0 Date: 2026-09-16 Status: Spike run, real findings — TFP-036 ran the comparison this doc asked for (see skills/INTROSPECT_CRAWL_SPIKE.md), and crawl-and-classify-pages was built directly from it. One genuine gap remains, honestly flagged in skills/ROADMAP.md rather than hidden: the skill has never been run against a real connected browser-automation tool, only verified by reading code and Playwright MCP’s documented tool list. This doc’s header was never updated to reflect any of that. Corrected 2026-09-23 (Cowork verification pass).
TFP-036 was ticketed in Phase 17 (docs/decisions/phase-17-skills-extraction-backlog.md)
and never actually run — it’s been referenced as “tracked as TFP-036, not
duplicated here” in skills/README.md and skills/ROADMAP.md ever since,
without anyone doing the spike itself. This phase finally scopes and runs
it, keeping the same ticket ID since it’s already cited by name in three
other documents — renumbering would just break those references for no
reason.
The original stated rationale is now partly stale, worth correcting
rather than copying forward unchanged. TFP-036 was framed as a
prerequisite for find-the-hidden-platform: “before any
find-the-hidden-platform-style skill gets built, confirm whether Playwright
MCP already provides equivalent capability.” That skill is now built
(TFP-045) and turned out not to need DOM-exploration logic at all — it
audits skipif guards, default-off flags, and monkeypatches, which is a
different problem entirely. So that specific blocking relationship never
materialized, and this phase isn’t gated on anything.
What’s still a real, open question: src/lib/introspect and
src/app/api/crawl/route.ts are roughly 1,200-1,300 lines of real DOM-
exploration logic, sitting unduplicated and unverified against Playwright
MCP’s own equivalent capability. docs/REIMAGINING.md flagged this as the
one genuine loss if TestForge’s app is ever trimmed. This is also, right
now, unusually well-timed: Phase 19’s TFP-040 is about to exercise this
exact code path for real — running TestForge’s actual crawl → generate →
run pipeline against test-assist. Running this spike first (or at least
before TFP-040 is called done) means its findings can actually inform how
TFP-040’s results get read, rather than sitting as a separate, disconnected
investigation.
src/lib/introspect and
crawl/route.ts already handle.src/lib/introspect or crawl/route.ts — spike only, no
production code changes.investigation, spikedocs/REIMAGINING.md already flagged this as the one loss worth
checking before anything gets built or trimmed around it.src/lib/introspect/crawl/route.ts
currently handle — ideally including at least one from
test-assist’s browser build, since that’s also Phase 19’s target
and gives this spike a real, shared reference point.skills/ROADMAP.md (or linked from it, same as
the original ticket specified) — supersedes the current placeholder
reference.find-the-hidden-platform prerequisite framing is corrected in
skills/ROADMAP.md’s reference to this ticket, since that
relationship turned out not to hold.Single ticket. Suggested: run before or alongside TFP-040 rather than after, so both pieces of evidence about the same code path land close together.