You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prospect research needs stateful full-stack regression coverage without turning every case into a rigorous end-to-end campaign.
What
Add an exploratory prospect mission and a frozen execution-only React, Node.js, TypeScript, and SQLite case. Its deterministic oracle covers browser, HTTP, SQLite, export, restart, provider-failure, and runtime-network behavior while reusing the shared packet and attempt contracts.
The case does not add a prospect-specific 2x2 study, requirement ledger, scored-provider gate, or comparative claim.
Medium Risk
Touches shared execution-comparison contracts, oracle dispatch, and Brunch seeding paths used by other cases; mistakes could break case registration or brownfield/greenfield parsing, though coverage is heavy on parsers and oracle tests.
Overview FE-1253 reframes prospect research as a deterministic full-stack execution regression case, not a second end-to-end 2×2 campaign. Docs and D139-L record that the exploratory mission stays for specification work while study profiles, requirement ledgers, scored provider gates, and campaign claims are retired for this case.
A new frozen prospect-research-workspace-v1 packet fixes React/Node/TypeScript/SQLite, npm test / build / start, env-driven fixtures, forbidden runtime network, and accessible UI/API contracts. The compiled oracle (prospect-research-workspace-oracles-v1) runs npm test/build, then seven independent browser/HTTP/SQLite/export journeys against a controller known-good app and rival behavior modules (PR1–PR9).
Execution plumbing grows to four compiled oracles: strict public-contract parsing, closed oracle-pack hashing, operator CLI case resolution, Brunch workspace seeding via an opaque full-stack seed (not Petri section parsing), and dispatch/retain wiring in execution-comparison-operator. Tests lock registry membership, claim coverage, and rival sensitivity.
Reviewed by Cursor Bugbot for commit c0c3e47. Bugbot is set up for automated code reviews on this repo. Configure here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Prospect research needs stateful full-stack regression coverage without turning every case into a rigorous end-to-end campaign.
What
Add an exploratory prospect mission and a frozen execution-only React, Node.js, TypeScript, and SQLite case. Its deterministic oracle covers browser, HTTP, SQLite, export, restart, provider-failure, and runtime-network behavior while reusing the shared packet and attempt contracts.
The case does not add a prospect-specific 2x2 study, requirement ledger, scored-provider gate, or comparative claim.
How to test
npm run checknpm run buildnpx vitest --run --maxWorkers=1 src/dev/execution-comparison/__tests__/prospect-research-workspace-oracle.test.ts