@researai/deepscientist 1.5.17 → 1.6.0

package/src/skills/science/references/packages/brian2.md

@@ -0,0 +1,73 @@
+# Brian2 Spiking Neural Network Simulator
+
+## Catalog
+
+- Package id: `brian2`
+- Domains: `computational_neuroscience`
+- Tags: `computational-neuroscience`, `spiking-networks`, `neural-simulation`, `dynamical-systems`
+- Knowledge URL: https://github.com/skilled-scipkg/brian2
+- Source archive URL: https://github.com/skilled-scipkg/brian2/archive/refs/heads/master.zip
+- Upstream project URL: https://github.com/brian-team/brian2
+- Homepage: http://briansimulator.org
+- Catalog source: FermiLink skilled-scipkg, commit `93f089a333a43089fb1a08a73c37d05fd6683214`
+
+## When To Consider
+
+Brian2 is an open source Python simulator for building and running flexible spiking neural network models in computational neuroscience research and education.
+
+## DeepScientist Runtime Rule
+
+This card is package knowledge and routing context only. It does not mean the
+solver, Python module, CLI binary, compiled backend, license server, dataset, or
+HPC module is installed in the active environment. Before computed work, use
+`bash_exec(...)` to perform an import, executable, version, and smoke-test check
+appropriate for `brian2`.
+
+## Package Check
+
+Use a package-specific import, executable, or module check and save the result
+under `validation/environment/brian2_doctor.json` before treating the
+runtime as usable.
+
+Record the result with `artifact.science(...)` as `science.package_check`. Use
+`status="passed"` only when the environment can run at least a minimal smoke
+path. Use `status="failed"` or `status="blocked"` when the check explains why
+execution cannot proceed.
+
+Generated import or executable names are starting points. If `brian2` uses
+a different Python module, CLI binary, environment module, container, or wrapper
+script, adjust the check before concluding the solver is unavailable.
+
+## Expected Science Nodes
+
+- `science.package_check` for import/executable/version/smoke-test evidence
+- `science.computational_run` for solver execution, simulation, fitting, or numerical computation
+- `science.dataset_analysis` when the task primarily analyzes existing data
+- `science.parameter_sweep` when varying parameters, inputs, models, or solver settings
+- `science.validation_result` for convergence, units, schema, controls, or correctness checks
+- `science.claim` only after evidence paths or related nodes support the claim
+
+## Evidence Path Conventions
+
+- `simulations/inputs/` for generated or selected solver inputs
+- `simulations/logs/` for stdout, stderr, scheduler logs, or solver logs
+- `simulations/outputs/` for structured run outputs
+- `analyses/scripts/`, `analyses/logs/`, and `analyses/outputs/` for dataset analysis
+- `validation/environment/` for package checks
+- `validation/runs/` for convergence, unit, schema, or correctness sidecars
+- `figures/` for derived visualizations
+
+## Validation Checklist
+
+- Record package version, executable path, backend, module state, or container image when relevant.
+- Preserve input files and parameters that define the scientific state.
+- Capture units, coordinate conventions, timestep/mesh/basis/model settings, seeds, and convergence criteria when applicable.
+- Validate output schema and important physical or statistical invariants before recording a computed claim.
+- Link claims to run, analysis, sweep, and validation nodes rather than relying on prose.
+
+## Common Pitfalls
+
+- Do not treat the package card or knowledge URL as runtime availability.
+- Do not weaken solver tolerances, physical models, dataset filters, or convergence criteria to make a run pass unless the change is explicitly part of the scientific question.
+- Do not call a value `computed` unless the corresponding run or analysis happened in the current quest and evidence paths are recorded.
+- Do not copy package knowledge-base material into the quest without preserving its source and license context.

package/src/skills/science/references/packages/bullet3.md

@@ -0,0 +1,73 @@
+# Bullet Physics SDK (bullet3)
+
+## Catalog
+
+- Package id: `bullet3`
+- Domains: `workflow_provenance`, `robotics_physics`
+- Tags: `physics`, `simulation`, `collision`, `rigidbody`, `robotics`, `pybullet`
+- Knowledge URL: https://github.com/skilled-scipkg/bullet3
+- Source archive URL: https://github.com/skilled-scipkg/bullet3/archive/refs/heads/master.zip
+- Upstream project URL: https://github.com/bulletphysics/bullet3
+- Homepage: http://bulletphysics.org
+- Catalog source: FermiLink skilled-scipkg, commit `93f089a333a43089fb1a08a73c37d05fd6683214`
+
+## When To Consider
+
+Bullet3 is a real time physics simulation library for rigid body dynamics and collision detection, with strong PyBullet workflows for robotics and reinforcement learning research.
+
+## DeepScientist Runtime Rule
+
+This card is package knowledge and routing context only. It does not mean the
+solver, Python module, CLI binary, compiled backend, license server, dataset, or
+HPC module is installed in the active environment. Before computed work, use
+`bash_exec(...)` to perform an import, executable, version, and smoke-test check
+appropriate for `bullet3`.
+
+## Package Check
+
+Use a package-specific import, executable, or module check and save the result
+under `validation/environment/bullet3_doctor.json` before treating the
+runtime as usable.
+
+Record the result with `artifact.science(...)` as `science.package_check`. Use
+`status="passed"` only when the environment can run at least a minimal smoke
+path. Use `status="failed"` or `status="blocked"` when the check explains why
+execution cannot proceed.
+
+Generated import or executable names are starting points. If `bullet3` uses
+a different Python module, CLI binary, environment module, container, or wrapper
+script, adjust the check before concluding the solver is unavailable.
+
+## Expected Science Nodes
+
+- `science.package_check` for import/executable/version/smoke-test evidence
+- `science.computational_run` for solver execution, simulation, fitting, or numerical computation
+- `science.dataset_analysis` when the task primarily analyzes existing data
+- `science.parameter_sweep` when varying parameters, inputs, models, or solver settings
+- `science.validation_result` for convergence, units, schema, controls, or correctness checks
+- `science.claim` only after evidence paths or related nodes support the claim
+
+## Evidence Path Conventions
+
+- `simulations/inputs/` for generated or selected solver inputs
+- `simulations/logs/` for stdout, stderr, scheduler logs, or solver logs
+- `simulations/outputs/` for structured run outputs
+- `analyses/scripts/`, `analyses/logs/`, and `analyses/outputs/` for dataset analysis
+- `validation/environment/` for package checks
+- `validation/runs/` for convergence, unit, schema, or correctness sidecars
+- `figures/` for derived visualizations
+
+## Validation Checklist
+
+- Record package version, executable path, backend, module state, or container image when relevant.
+- Preserve input files and parameters that define the scientific state.
+- Capture units, coordinate conventions, timestep/mesh/basis/model settings, seeds, and convergence criteria when applicable.
+- Validate output schema and important physical or statistical invariants before recording a computed claim.
+- Link claims to run, analysis, sweep, and validation nodes rather than relying on prose.
+
+## Common Pitfalls
+
+- Do not treat the package card or knowledge URL as runtime availability.
+- Do not weaken solver tolerances, physical models, dataset filters, or convergence criteria to make a run pass unless the change is explicitly part of the scientific question.
+- Do not call a value `computed` unless the corresponding run or analysis happened in the current quest and evidence paths are recorded.
+- Do not copy package knowledge-base material into the quest without preserving its source and license context.

package/src/skills/science/references/packages/calculix.md

@@ -0,0 +1,80 @@
+# CalculiX Finite Element Program
+
+## Catalog
+
+- Package id: `calculix`
+- Domains: `finite_element_engineering`, `workflow_provenance`
+- Tags: `finite-element`, `fea`, `structural-mechanics`, `thermomechanics`, `mechanical-simulation`
+- Knowledge URL: https://github.com/skilled-scipkg/CalculiX
+- Source archive URL: https://github.com/skilled-scipkg/CalculiX/archive/refs/heads/master.zip
+- Upstream project URL: https://github.com/Dhondtguido/CalculiX
+- Homepage: https://github.com/Dhondtguido/CalculiX
+- Catalog source: FermiLink skilled-scipkg, commit `93f089a333a43089fb1a08a73c37d05fd6683214`
+
+## When To Consider
+
+CalculiX is an open-source three-dimensional finite element package for structural and thermomechanical simulation, with ABAQUS-style input decks and engineering stress analysis workflows.
+
+## DeepScientist Runtime Rule
+
+This card is package knowledge and routing context only. It does not mean the
+solver, Python module, CLI binary, compiled backend, license server, dataset, or
+HPC module is installed in the active environment. Before computed work, use
+`bash_exec(...)` to perform an import, executable, version, and smoke-test check
+appropriate for `calculix`.
+
+## Package Check
+
+For CLI/HPC-oriented environments, check the executable or loaded module before
+running any expensive job:
+
+```bash
+command -v calculix || true
+calculix --version || true
+```
+
+If the package is available only through environment modules, record the module
+state and the exact executable path in `validation/environment/calculix_doctor.json`.
+
+Record the result with `artifact.science(...)` as `science.package_check`. Use
+`status="passed"` only when the environment can run at least a minimal smoke
+path. Use `status="failed"` or `status="blocked"` when the check explains why
+execution cannot proceed.
+
+Generated import or executable names are starting points. If `calculix` uses
+a different Python module, CLI binary, environment module, container, or wrapper
+script, adjust the check before concluding the solver is unavailable.
+
+## Expected Science Nodes
+
+- `science.package_check` for import/executable/version/smoke-test evidence
+- `science.computational_run` for solver execution, simulation, fitting, or numerical computation
+- `science.dataset_analysis` when the task primarily analyzes existing data
+- `science.parameter_sweep` when varying parameters, inputs, models, or solver settings
+- `science.validation_result` for convergence, units, schema, controls, or correctness checks
+- `science.claim` only after evidence paths or related nodes support the claim
+
+## Evidence Path Conventions
+
+- `simulations/inputs/` for generated or selected solver inputs
+- `simulations/logs/` for stdout, stderr, scheduler logs, or solver logs
+- `simulations/outputs/` for structured run outputs
+- `analyses/scripts/`, `analyses/logs/`, and `analyses/outputs/` for dataset analysis
+- `validation/environment/` for package checks
+- `validation/runs/` for convergence, unit, schema, or correctness sidecars
+- `figures/` for derived visualizations
+
+## Validation Checklist
+
+- Record package version, executable path, backend, module state, or container image when relevant.
+- Preserve input files and parameters that define the scientific state.
+- Capture units, coordinate conventions, timestep/mesh/basis/model settings, seeds, and convergence criteria when applicable.
+- Validate output schema and important physical or statistical invariants before recording a computed claim.
+- Link claims to run, analysis, sweep, and validation nodes rather than relying on prose.
+
+## Common Pitfalls
+
+- Do not treat the package card or knowledge URL as runtime availability.
+- Do not weaken solver tolerances, physical models, dataset filters, or convergence criteria to make a run pass unless the change is explicitly part of the scientific question.
+- Do not call a value `computed` unless the corresponding run or analysis happened in the current quest and evidence paths are recorded.
+- Do not copy package knowledge-base material into the quest without preserving its source and license context.

package/src/skills/science/references/packages/cantera.md

@@ -0,0 +1,73 @@
+# Cantera Chemical Kinetics and Combustion
+
+## Catalog
+
+- Package id: `cantera`
+- Domains: `computational_science`
+- Tags: `chemical-kinetics`, `combustion`, `thermodynamics`, `transport`, `reactor-modeling`, `flame-simulation`
+- Knowledge URL: https://github.com/skilled-scipkg/cantera
+- Source archive URL: https://github.com/skilled-scipkg/cantera/archive/refs/heads/main.zip
+- Upstream project URL: https://github.com/Cantera/cantera
+- Homepage: https://cantera.org
+- Catalog source: FermiLink skilled-scipkg, commit `93f089a333a43089fb1a08a73c37d05fd6683214`
+
+## When To Consider
+
+Cantera is an open-source scientific toolkit for modeling chemical kinetics, thermodynamics, and transport, supporting equilibrium calculations, reactor-network simulations, and one-dimensional flame analyses across multiple programming interfaces.
+
+## DeepScientist Runtime Rule
+
+This card is package knowledge and routing context only. It does not mean the
+solver, Python module, CLI binary, compiled backend, license server, dataset, or
+HPC module is installed in the active environment. Before computed work, use
+`bash_exec(...)` to perform an import, executable, version, and smoke-test check
+appropriate for `cantera`.
+
+## Package Check
+
+Use a package-specific import, executable, or module check and save the result
+under `validation/environment/cantera_doctor.json` before treating the
+runtime as usable.
+
+Record the result with `artifact.science(...)` as `science.package_check`. Use
+`status="passed"` only when the environment can run at least a minimal smoke
+path. Use `status="failed"` or `status="blocked"` when the check explains why
+execution cannot proceed.
+
+Generated import or executable names are starting points. If `cantera` uses
+a different Python module, CLI binary, environment module, container, or wrapper
+script, adjust the check before concluding the solver is unavailable.
+
+## Expected Science Nodes
+
+- `science.package_check` for import/executable/version/smoke-test evidence
+- `science.computational_run` for solver execution, simulation, fitting, or numerical computation
+- `science.dataset_analysis` when the task primarily analyzes existing data
+- `science.parameter_sweep` when varying parameters, inputs, models, or solver settings
+- `science.validation_result` for convergence, units, schema, controls, or correctness checks
+- `science.claim` only after evidence paths or related nodes support the claim
+
+## Evidence Path Conventions
+
+- `simulations/inputs/` for generated or selected solver inputs
+- `simulations/logs/` for stdout, stderr, scheduler logs, or solver logs
+- `simulations/outputs/` for structured run outputs
+- `analyses/scripts/`, `analyses/logs/`, and `analyses/outputs/` for dataset analysis
+- `validation/environment/` for package checks
+- `validation/runs/` for convergence, unit, schema, or correctness sidecars
+- `figures/` for derived visualizations
+
+## Validation Checklist
+
+- Record package version, executable path, backend, module state, or container image when relevant.
+- Preserve input files and parameters that define the scientific state.
+- Capture units, coordinate conventions, timestep/mesh/basis/model settings, seeds, and convergence criteria when applicable.
+- Validate output schema and important physical or statistical invariants before recording a computed claim.
+- Link claims to run, analysis, sweep, and validation nodes rather than relying on prose.
+
+## Common Pitfalls
+
+- Do not treat the package card or knowledge URL as runtime availability.
+- Do not weaken solver tolerances, physical models, dataset filters, or convergence criteria to make a run pass unless the change is explicitly part of the scientific question.
+- Do not call a value `computed` unless the corresponding run or analysis happened in the current quest and evidence paths are recorded.
+- Do not copy package knowledge-base material into the quest without preserving its source and license context.

package/src/skills/science/references/packages/cavity-md-ipi.md

@@ -0,0 +1,80 @@
+# CavMD: Cavity Molecular Dynamics
+
+## Catalog
+
+- Package id: `cavity-md-ipi`
+- Domains: `molecular_dynamics`, `workflow_provenance`
+- Tags: `molecular-dynamics`, `cavity-qed`, `vibrational-coupling`, `chemical-physics`, `path-integral`, `qmmm`
+- Knowledge URL: https://github.com/skilled-scipkg/cavity-md-ipi
+- Source archive URL: https://github.com/skilled-scipkg/cavity-md-ipi/archive/refs/heads/master.zip
+- Upstream project URL: https://github.com/TaoELi/cavity-md-ipi
+- Homepage: https://github.com/TaoELi/cavity-md-ipi
+- Catalog source: FermiLink skilled-scipkg, commit `93f089a333a43089fb1a08a73c37d05fd6683214`
+
+## When To Consider
+
+CavMD simulates cavity-coupled molecular dynamics for vibrational strong and ultrastrong coupling, spanning classical and path-integral regimes with workflows for setup, job submission, post-processing, and plotting.
+
+## DeepScientist Runtime Rule
+
+This card is package knowledge and routing context only. It does not mean the
+solver, Python module, CLI binary, compiled backend, license server, dataset, or
+HPC module is installed in the active environment. Before computed work, use
+`bash_exec(...)` to perform an import, executable, version, and smoke-test check
+appropriate for `cavity-md-ipi`.
+
+## Package Check
+
+For CLI/HPC-oriented environments, check the executable or loaded module before
+running any expensive job:
+
+```bash
+command -v cavity-md-ipi || true
+cavity-md-ipi --version || true
+```
+
+If the package is available only through environment modules, record the module
+state and the exact executable path in `validation/environment/cavity-md-ipi_doctor.json`.
+
+Record the result with `artifact.science(...)` as `science.package_check`. Use
+`status="passed"` only when the environment can run at least a minimal smoke
+path. Use `status="failed"` or `status="blocked"` when the check explains why
+execution cannot proceed.
+
+Generated import or executable names are starting points. If `cavity-md-ipi` uses
+a different Python module, CLI binary, environment module, container, or wrapper
+script, adjust the check before concluding the solver is unavailable.
+
+## Expected Science Nodes
+
+- `science.package_check` for import/executable/version/smoke-test evidence
+- `science.computational_run` for solver execution, simulation, fitting, or numerical computation
+- `science.dataset_analysis` when the task primarily analyzes existing data
+- `science.parameter_sweep` when varying parameters, inputs, models, or solver settings
+- `science.validation_result` for convergence, units, schema, controls, or correctness checks
+- `science.claim` only after evidence paths or related nodes support the claim
+
+## Evidence Path Conventions
+
+- `simulations/inputs/` for generated or selected solver inputs
+- `simulations/logs/` for stdout, stderr, scheduler logs, or solver logs
+- `simulations/outputs/` for structured run outputs
+- `analyses/scripts/`, `analyses/logs/`, and `analyses/outputs/` for dataset analysis
+- `validation/environment/` for package checks
+- `validation/runs/` for convergence, unit, schema, or correctness sidecars
+- `figures/` for derived visualizations
+
+## Validation Checklist
+
+- Record package version, executable path, backend, module state, or container image when relevant.
+- Preserve input files and parameters that define the scientific state.
+- Capture units, coordinate conventions, timestep/mesh/basis/model settings, seeds, and convergence criteria when applicable.
+- Validate output schema and important physical or statistical invariants before recording a computed claim.
+- Link claims to run, analysis, sweep, and validation nodes rather than relying on prose.
+
+## Common Pitfalls
+
+- Do not treat the package card or knowledge URL as runtime availability.
+- Do not weaken solver tolerances, physical models, dataset filters, or convergence criteria to make a run pass unless the change is explicitly part of the scientific question.
+- Do not call a value `computed` unless the corresponding run or analysis happened in the current quest and evidence paths are recorded.
+- Do not copy package knowledge-base material into the quest without preserving its source and license context.

package/src/skills/science/references/packages/ccdproc.md

@@ -0,0 +1,88 @@
+# CCDProc CCD Image Reduction
+
+## Catalog
+
+- Package id: `ccdproc`
+- Domains: `astronomy_astrophysics`
+- Tags: `astronomy`, `ccd`, `image-reduction`, `optical-ir`, `calibration`
+- Knowledge URL: https://github.com/skilled-scipkg/ccdproc
+- Source archive URL: https://github.com/skilled-scipkg/ccdproc/archive/refs/heads/main.zip
+- Upstream project URL: https://github.com/astropy/ccdproc
+- Homepage: https://ccdproc.readthedocs.io
+- Catalog source: FermiLink skilled-scipkg, commit `93f089a333a43089fb1a08a73c37d05fd6683214`
+
+## When To Consider
+
+Astropy-affiliated toolkit for calibrating and reducing optical and infrared CCD observations with overscan, bias, dark, flat, bad-pixel masking, cosmic-ray cleaning, and uncertainty-aware processing.
+
+## DeepScientist Runtime Rule
+
+This card is package knowledge and routing context only. It does not mean the
+solver, Python module, CLI binary, compiled backend, license server, dataset, or
+HPC module is installed in the active environment. Before computed work, use
+`bash_exec(...)` to perform an import, executable, version, and smoke-test check
+appropriate for `ccdproc`.
+
+## Package Check
+
+For Python-facing environments, start with an import/version check and then a
+minimal package-specific smoke test:
+
+```bash
+python - <<'PY'
+import importlib, json, pathlib
+package_id = 'ccdproc'
+result = {"package_id": package_id, "import": "failed", "version": None, "smoke": "not_run"}
+try:
+    module = importlib.import_module(package_id.replace('-', '_').split('_jl')[0])
+    result["import"] = "passed"
+    result["version"] = getattr(module, "__version__", None)
+except Exception as exc:
+    result["error"] = repr(exc)
+pathlib.Path("validation/environment").mkdir(parents=True, exist_ok=True)
+pathlib.Path(f"validation/environment/{package_id}_doctor.json").write_text(json.dumps(result, indent=2), encoding="utf-8")
+PY
+```
+
+Record the result with `artifact.science(...)` as `science.package_check`. Use
+`status="passed"` only when the environment can run at least a minimal smoke
+path. Use `status="failed"` or `status="blocked"` when the check explains why
+execution cannot proceed.
+
+Generated import or executable names are starting points. If `ccdproc` uses
+a different Python module, CLI binary, environment module, container, or wrapper
+script, adjust the check before concluding the solver is unavailable.
+
+## Expected Science Nodes
+
+- `science.package_check` for import/executable/version/smoke-test evidence
+- `science.computational_run` for solver execution, simulation, fitting, or numerical computation
+- `science.dataset_analysis` when the task primarily analyzes existing data
+- `science.parameter_sweep` when varying parameters, inputs, models, or solver settings
+- `science.validation_result` for convergence, units, schema, controls, or correctness checks
+- `science.claim` only after evidence paths or related nodes support the claim
+
+## Evidence Path Conventions
+
+- `simulations/inputs/` for generated or selected solver inputs
+- `simulations/logs/` for stdout, stderr, scheduler logs, or solver logs
+- `simulations/outputs/` for structured run outputs
+- `analyses/scripts/`, `analyses/logs/`, and `analyses/outputs/` for dataset analysis
+- `validation/environment/` for package checks
+- `validation/runs/` for convergence, unit, schema, or correctness sidecars
+- `figures/` for derived visualizations
+
+## Validation Checklist
+
+- Record package version, executable path, backend, module state, or container image when relevant.
+- Preserve input files and parameters that define the scientific state.
+- Capture units, coordinate conventions, timestep/mesh/basis/model settings, seeds, and convergence criteria when applicable.
+- Validate output schema and important physical or statistical invariants before recording a computed claim.
+- Link claims to run, analysis, sweep, and validation nodes rather than relying on prose.
+
+## Common Pitfalls
+
+- Do not treat the package card or knowledge URL as runtime availability.
+- Do not weaken solver tolerances, physical models, dataset filters, or convergence criteria to make a run pass unless the change is explicitly part of the scientific question.
+- Do not call a value `computed` unless the corresponding run or analysis happened in the current quest and evidence paths are recorded.
+- Do not copy package knowledge-base material into the quest without preserving its source and license context.

package/src/skills/science/references/packages/celerite2.md

@@ -0,0 +1,88 @@
+# celerite2 Gaussian Process Toolkit
+
+## Catalog
+
+- Package id: `celerite2`
+- Domains: `astronomy_astrophysics`, `workflow_provenance`
+- Tags: `gaussian-processes`, `time-series`, `astronomy`, `probabilistic-modeling`, `celerite`
+- Knowledge URL: https://github.com/skilled-scipkg/celerite2
+- Source archive URL: https://github.com/skilled-scipkg/celerite2/archive/refs/heads/main.zip
+- Upstream project URL: https://github.com/exoplanet-dev/celerite2
+- Homepage: https://celerite2.readthedocs.io
+- Catalog source: FermiLink skilled-scipkg, commit `93f089a333a43089fb1a08a73c37d05fd6683214`
+
+## When To Consider
+
+celerite2 provides numerically stable, fast one-dimensional Gaussian process regression in Python and C++, optimized for scalable time-series inference with structured kernels and astronomy-focused probabilistic modeling workflows.
+
+## DeepScientist Runtime Rule
+
+This card is package knowledge and routing context only. It does not mean the
+solver, Python module, CLI binary, compiled backend, license server, dataset, or
+HPC module is installed in the active environment. Before computed work, use
+`bash_exec(...)` to perform an import, executable, version, and smoke-test check
+appropriate for `celerite2`.
+
+## Package Check
+
+For Python-facing environments, start with an import/version check and then a
+minimal package-specific smoke test:
+
+```bash
+python - <<'PY'
+import importlib, json, pathlib
+package_id = 'celerite2'
+result = {"package_id": package_id, "import": "failed", "version": None, "smoke": "not_run"}
+try:
+    module = importlib.import_module(package_id.replace('-', '_').split('_jl')[0])
+    result["import"] = "passed"
+    result["version"] = getattr(module, "__version__", None)
+except Exception as exc:
+    result["error"] = repr(exc)
+pathlib.Path("validation/environment").mkdir(parents=True, exist_ok=True)
+pathlib.Path(f"validation/environment/{package_id}_doctor.json").write_text(json.dumps(result, indent=2), encoding="utf-8")
+PY
+```
+
+Record the result with `artifact.science(...)` as `science.package_check`. Use
+`status="passed"` only when the environment can run at least a minimal smoke
+path. Use `status="failed"` or `status="blocked"` when the check explains why
+execution cannot proceed.
+
+Generated import or executable names are starting points. If `celerite2` uses
+a different Python module, CLI binary, environment module, container, or wrapper
+script, adjust the check before concluding the solver is unavailable.
+
+## Expected Science Nodes
+
+- `science.package_check` for import/executable/version/smoke-test evidence
+- `science.computational_run` for solver execution, simulation, fitting, or numerical computation
+- `science.dataset_analysis` when the task primarily analyzes existing data
+- `science.parameter_sweep` when varying parameters, inputs, models, or solver settings
+- `science.validation_result` for convergence, units, schema, controls, or correctness checks
+- `science.claim` only after evidence paths or related nodes support the claim
+
+## Evidence Path Conventions
+
+- `simulations/inputs/` for generated or selected solver inputs
+- `simulations/logs/` for stdout, stderr, scheduler logs, or solver logs
+- `simulations/outputs/` for structured run outputs
+- `analyses/scripts/`, `analyses/logs/`, and `analyses/outputs/` for dataset analysis
+- `validation/environment/` for package checks
+- `validation/runs/` for convergence, unit, schema, or correctness sidecars
+- `figures/` for derived visualizations
+
+## Validation Checklist
+
+- Record package version, executable path, backend, module state, or container image when relevant.
+- Preserve input files and parameters that define the scientific state.
+- Capture units, coordinate conventions, timestep/mesh/basis/model settings, seeds, and convergence criteria when applicable.
+- Validate output schema and important physical or statistical invariants before recording a computed claim.
+- Link claims to run, analysis, sweep, and validation nodes rather than relying on prose.
+
+## Common Pitfalls
+
+- Do not treat the package card or knowledge URL as runtime availability.
+- Do not weaken solver tolerances, physical models, dataset filters, or convergence criteria to make a run pass unless the change is explicitly part of the scientific question.
+- Do not call a value `computed` unless the corresponding run or analysis happened in the current quest and evidence paths are recorded.
+- Do not copy package knowledge-base material into the quest without preserving its source and license context.

package/src/skills/science/references/packages/cellrank.md

@@ -0,0 +1,73 @@
+# CellRank Single-Cell Fate Mapping
+
+## Catalog
+
+- Package id: `cellrank`
+- Domains: `computational_science`
+- Tags: `single-cell`, `fate-mapping`, `trajectory-inference`, `rna-velocity`, `markov-models`, `computational-biology`
+- Knowledge URL: https://github.com/skilled-scipkg/cellrank
+- Source archive URL: https://github.com/skilled-scipkg/cellrank/archive/refs/heads/main.zip
+- Upstream project URL: https://github.com/theislab/cellrank
+- Homepage: https://cellrank.readthedocs.io/en/latest/
+- Catalog source: FermiLink skilled-scipkg, commit `93f089a333a43089fb1a08a73c37d05fd6683214`
+
+## When To Consider
+
+CellRank is a single-cell analysis framework that models cellular dynamics with Markov state methods to infer lineage fates, macrostates, and driver genes from multiview data.
+
+## DeepScientist Runtime Rule
+
+This card is package knowledge and routing context only. It does not mean the
+solver, Python module, CLI binary, compiled backend, license server, dataset, or
+HPC module is installed in the active environment. Before computed work, use
+`bash_exec(...)` to perform an import, executable, version, and smoke-test check
+appropriate for `cellrank`.
+
+## Package Check
+
+Use a package-specific import, executable, or module check and save the result
+under `validation/environment/cellrank_doctor.json` before treating the
+runtime as usable.
+
+Record the result with `artifact.science(...)` as `science.package_check`. Use
+`status="passed"` only when the environment can run at least a minimal smoke
+path. Use `status="failed"` or `status="blocked"` when the check explains why
+execution cannot proceed.
+
+Generated import or executable names are starting points. If `cellrank` uses
+a different Python module, CLI binary, environment module, container, or wrapper
+script, adjust the check before concluding the solver is unavailable.
+
+## Expected Science Nodes
+
+- `science.package_check` for import/executable/version/smoke-test evidence
+- `science.computational_run` for solver execution, simulation, fitting, or numerical computation
+- `science.dataset_analysis` when the task primarily analyzes existing data
+- `science.parameter_sweep` when varying parameters, inputs, models, or solver settings
+- `science.validation_result` for convergence, units, schema, controls, or correctness checks
+- `science.claim` only after evidence paths or related nodes support the claim
+
+## Evidence Path Conventions
+
+- `simulations/inputs/` for generated or selected solver inputs
+- `simulations/logs/` for stdout, stderr, scheduler logs, or solver logs
+- `simulations/outputs/` for structured run outputs
+- `analyses/scripts/`, `analyses/logs/`, and `analyses/outputs/` for dataset analysis
+- `validation/environment/` for package checks
+- `validation/runs/` for convergence, unit, schema, or correctness sidecars
+- `figures/` for derived visualizations
+
+## Validation Checklist
+
+- Record package version, executable path, backend, module state, or container image when relevant.
+- Preserve input files and parameters that define the scientific state.
+- Capture units, coordinate conventions, timestep/mesh/basis/model settings, seeds, and convergence criteria when applicable.
+- Validate output schema and important physical or statistical invariants before recording a computed claim.
+- Link claims to run, analysis, sweep, and validation nodes rather than relying on prose.
+
+## Common Pitfalls
+
+- Do not treat the package card or knowledge URL as runtime availability.
+- Do not weaken solver tolerances, physical models, dataset filters, or convergence criteria to make a run pass unless the change is explicitly part of the scientific question.
+- Do not call a value `computed` unless the corresponding run or analysis happened in the current quest and evidence paths are recorded.
+- Do not copy package knowledge-base material into the quest without preserving its source and license context.