@researai/deepscientist 1.5.12 → 1.5.14

package/src/skills/baseline/references/artifact-payload-examples.md

@@ -0,0 +1,39 @@
+# Artifact Payload Examples
+
+Use this reference when the `baseline` stage needs a stable payload shape without re-expanding the main skill body.
+
+## Route or blocked decision
+
+Keep these fields when route choice or blocking status matters:
+
+- `kind`
+- `action`
+- `reason`
+- `baseline_id`
+- `baseline_variant_id` when relevant
+- `evidence_paths`
+- `next_direction`
+
+## Accepted baseline
+
+Keep these fields when writing the accepted baseline artifact:
+
+- `kind`
+- `baseline_id`
+- `baseline_kind`
+- `path`
+- `task`
+- `dataset`
+- `primary_metric`
+- `metrics_summary`
+- `default_variant_id` when relevant
+- `baseline_variants` when relevant
+- `environment`
+- `source`
+- `summary`
+
+## Rules
+
+- keep payloads compact but audit-friendly
+- do not omit the trusted comparison surface just because one headline metric exists
+- do not publish a blocked or verification-incomplete baseline payload as if it were accepted

package/src/skills/baseline/references/baseline-checklist-template.md

@@ -1,7 +1,7 @@
 # Baseline Checklist Template
 
 Use this as a living checklist.
-Update it during reading, setup, smoke testing, real execution, verification, and route changes.
+Keep it short by default. For a fast path, complete the core checklist first and expand only if the route becomes complex or unstable.
 
 ## Identity
 
@@ -9,49 +9,38 @@ Update it during reading, setup, smoke testing, real execution, verification, an
 - route:
 - owner stage:
 
-## Analysis
+## Core
+
+- [ ] baseline object and route are explicit
+- [ ] dataset / split and metric contract are explicit enough to judge comparability
+- [ ] `PLAN.md` captures the command path, expected outputs, acceptance condition, and fallback
+- [ ] smoke decision is explicit:
+  - skipped for a justified reason, or run once with outputs checked
+- [ ] real validation/run decision is explicit:
+  - skipped for a justified reason, or launched/read with durable evidence
+- [ ] expected result files and required metrics are checked
+- [ ] baseline is accepted, blocked, or waived with a durable note
+
+## Closeout
+
+- [ ] concise `1-2` sentence baseline summary written
+- [ ] next stage named explicitly
+
+## Optional Expansion
+
+Fill this only when the route becomes full-audit, repair-heavy, or publication-oriented.
 
 - [ ] paper source identified
 - [ ] repo source identified
 - [ ] paper read enough to restate the core method faithfully
 - [ ] repo read enough to identify the real entrypoints
-- [ ] dataset / split contract confirmed
-- [ ] metric contract confirmed
 - [ ] main files to inspect or modify listed
-- [ ] risks and fallbacks written into `PLAN.md`
-
-## Setup
-
 - [ ] working directory confirmed
 - [ ] environment route chosen
 - [ ] key dependencies checked
 - [ ] model / data download path confirmed
 - [ ] fallback source recorded for critical downloads
-
-## Smoke Test
-
-- [ ] smoke command written in `PLAN.md`
-- [ ] smoke command executed
-- [ ] smoke outputs verified
-- [ ] smoke failure handled or route revised
-
-## Main Run
-
-- [ ] real command written in `PLAN.md`
-- [ ] real run launched with durable logging
 - [ ] monitoring cadence started
 - [ ] health signals confirmed
 - [ ] any execution deviation reflected back into `PLAN.md`
-
-## Verification
-
-- [ ] expected result files exist
-- [ ] metric keys are complete
-- [ ] baseline is comparable to the intended contract
 - [ ] verification note written
-- [ ] baseline accepted or explicitly blocked / waived
-
-## Closeout
-
-- [ ] concise `1-2` sentence baseline summary written
-- [ ] next stage named explicitly

package/src/skills/baseline/references/baseline-plan-template.md

@@ -1,9 +1,10 @@
 # Baseline Plan Template
 
 Use this when the `baseline` stage becomes concrete enough to act.
-Keep it short when the route is simple, but do not skip the sections that affect reproducibility, code touchpoints, or fallback handling.
+Keep it short when the route is simple. For fast-path attach/import/prebound validation, a one-screen plan is enough if it preserves the route, command path, outputs, acceptance condition, and fallback.
+Expand the optional sections only when the route is ambiguous, code-touching, broken, multi-variant, or intended for reuse beyond the current quest.
 
-## 1. Objective
+## 1. Core Contract
 
 - quest goal:
 - user's core requirements:
@@ -12,80 +13,63 @@ Keep it short when the route is simple, but do not skip the sections that affect
   - attach / import / reproduce / repair
 - baseline id:
 - variant id:
-
-## 2. Source Package
-
 - source paper:
 - source repo:
-- fallback repo or mirror:
 - source commit / version / tag:
 - task:
 - dataset / split:
 - metric contract:
+- expected command path:
+- expected outputs:
+- acceptance condition:
+- cheapest fallback:
 
-## 3. Paper And Repo Reading Notes
-
-- paper summary in `1-3` bullets:
-- repo summary in `1-3` bullets:
-- what the baseline actually does:
-- what the likely bottlenecks or brittle points are:
-- what still needs verification:
-
-## 4. Code Touchpoints
-
-List the main files or modules that matter before you change anything substantial.
-
-| Path | Role | Why it matters now | Expected action | Notes |
-|---|---|---|---|---|
-| | | | inspect / modify / leave alone | |
-
-## 5. Environment And Asset Plan
+## 2. Execution Path
 
 - working directory:
 - environment plan:
 - required downloads:
-- checkpoints / models:
 - hardware assumptions:
-- likely external blockers:
-
-Fallbacks and contingency options:
-
-- if Hugging Face is slow, blocked, or rate-limited:
-  - try ModelScope, official mirrors, quest-local caches, or manually staged files
-- if the official repo is unavailable:
-  - use a verified mirror and record the exact provenance
-- if the full run is too expensive:
-  - define the smoke-test path and the cheapest comparable reduced pilot
+- smoke test needed:
+  - yes / no
+- smoke command:
+- main validation or run command:
+- expected runtime / budget:
+- durable log path:
+- verification targets:
+- fastest failure signal:
 
-## 6. Execution Strategy
+## 3. Risks And Revision
 
-### Smoke Test
+- main risks:
+- when to escalate from fast path to full audit:
+- revision note:
 
-- command:
-- purpose:
-- expected outputs:
-- fastest failure signal:
+## 4. Optional Expansion
 
-### Main Run
+Fill this only when the route is no longer simple.
 
-- command:
-- expected outputs:
-- expected runtime / budget:
-- durable log path:
+- fallback repo or mirror:
+- checkpoints / models:
+- likely external blockers:
 - safe efficiency levers to try first:
-
-### Monitoring And Sleep Rules
-
-- first checks:
-  - `60s`
-  - `120s`
-  - `300s`
-  - `600s`
-  - `1800s`
 - health signals that justify continued monitoring rather than intervention:
 - conditions that require plan revision or kill-and-relaunch:
+- paper summary in `1-3` bullets:
+- repo summary in `1-3` bullets:
+- what the baseline actually does:
+- what the likely bottlenecks or brittle points are:
+- what still needs verification:
+
+## 5. Optional Code Touchpoints
+
+List the main files or modules only when you expect real inspection or edits.
+
+| Path | Role | Why it matters now | Expected action | Notes |
+|---|---|---|---|---|
+| | | | inspect / modify / leave alone | |
 
-## 7. Verification Plan
+## 6. Optional Verification Plan
 
 - required result files:
 - required metric keys:
@@ -93,12 +77,12 @@ Fallbacks and contingency options:
 - acceptance condition:
 - downgrade / blocked condition:
 
-## 8. Checklist Link
+## 7. Checklist Link
 
 - checklist path:
 - which item should move next:
 
-## 9. Revision Log
+## 8. Revision Log
 
 | Time | What changed | Why it changed | Impact on execution |
 |---|---|---|---|