Add agentic web research MVP harness to Workspine

[PatrickSys]

Motivation

• Add a deterministic, artifact-first agentic web research harness so developers and agents can run repeatable, evidence-driven research inside Workspine.
• Keep the initial integration template-first and lightweight to avoid adding a runtime orchestration dependency.
• Surface explicit artifacts and verification gates to preserve Workspine’s evidence/verification discipline for research outputs.

Description

• Add docs/AGENTIC-RESEARCH-MVP.md describing the end-to-end decomposition-driven architecture, artifact contract, tradeoffs, and definition-of-done for the MVP.
• Add distilled/templates/research/agentic-harness.md as a runnable template that defines the pipeline (decomposition → coverage matrix → width/depth passes → synthesis → critique → patch → verification) and an append-only scratchpad.md discipline.
• Link the new MVP doc from README.md under the proof/resources section for discoverability.
• Used the Workspine core guidance in distilled/SKILL.md to follow the repo-native, spec-first workflow while authoring the changes.

Testing

• Ran npm test -- --runInBand, which executed the test suites against the modified codebase and completed successfully.
• The automated test run reported all tests passing (no failures) with only non-fatal npm warnings about unknown config flags.

---

Codex Task

[gemini-code-assist]

Code Review

This pull request introduces an Agentic Research MVP for Workspine, establishing a structured, artifact-driven workflow for web-enabled research. It includes a new documentation file outlining the architecture and a template for the research harness. Review feedback focused on ensuring the template explicitly references the correct file paths and artifact names, such as 'scaffold.md', to align with the defined architectural specification.

[gemini-code-assist]

The AGENTIC-RESEARCH-MVP.md documentation (line 28) specifies scaffold.md as the artifact for run metadata and configuration. This template should explicitly instruct the operator to write the metadata to that file to ensure the artifact is created as expected by the architecture.

Suggested change

	Write scaffold.md with:

[gemini-code-assist]

To ensure consistency with the directory structure defined in the MVP documentation, the path for the decomposition artifact should be explicitly relative to the research root.

Suggested change

	Write `prompt-decomposition.json` with:
	Write .planning/research/agentic/prompt-decomposition.json with:

[gemini-code-assist]

Explicitly defining the path for the coverage matrix ensures it is correctly located within the .planning/research/agentic/ directory as required by the core artifact specification.

Suggested change

	Build `coverage-matrix.md` mapping each significant phrase in the query to decomposition items.
	Build .planning/research/agentic/coverage-matrix.md mapping each significant phrase in the query to decomposition items.

[gemini-code-assist]

Defining the explicit path for the width sweep log maintains alignment with the artifact organization specified in the MVP documentation.

Suggested change

	Log results in `width-sweep.md`.
	Log results in .planning/research/agentic/width-sweep.md.

[gemini-code-assist]

The depth-notes/ directory should be prefixed with the research root path to prevent the operator from creating it in the repository root, which would violate the artifact organization defined in the MVP spec.

Suggested change

	Create one note file per major sub-question under `depth-notes/`.
	Create one note file per major sub-question under .planning/research/agentic/depth-notes/.

[gemini-code-assist]

Explicitly defining the path for scratchpad.md ensures it is correctly located within the .planning/research/agentic/ directory as required by the core artifact specification.

Suggested change

	Maintain `scratchpad.md` as append-only notes for long jobs:
	Maintain .planning/research/agentic/scratchpad.md as append-only notes for long jobs: