@iowarp/clio-coder 0.4.5 → 0.4.7

package/library/plugins/materio/skills/materio-research-explorer/SKILL.md

@@ -0,0 +1,74 @@
+---
+name: materio-research-explorer
+description: "Synthesize candidate materials-science questions and write researcher-confirmed identity."
+---
+
+For a new materials research direction, interview the domain, phenomenon, processing conditions, hypothesis, scope exclusions, resources, and timeline. Present three calibrated candidate questions, then write the selected identity and decisions under .research/ using the linked template. Preserve existing research state. Use the research state helper to initialize missing config.
+
+Read the [shared research policy](../../assets/references/research-policy.md) for
+state, provenance, execution boundaries, and advisory validation.
+
+Read the linked references when needed. Resolve links from this skill directory.
+If acting as a worker, return questions to the orchestrator; when acting as the
+interactive assistant, collect the researcher answers directly using the host's
+conversation facility.
+
+- [research-domains.md](../../assets/references/research-domains.md)
+- [RESEARCH.md](../../assets/templates/RESEARCH.md)
+- [config.json](../../assets/templates/config.json)
+
+## What Makes a Good Research Prompt
+
+A good research prompt is:
+- **Specific**: Names specific material, property, condition, or phenomenon
+- **Answerable**: Can be confirmed or refuted by an achievable experiment or calculation
+- **Novel**: Not already fully answered in the literature (this comes from literature-review, but initial framing matters)
+- **Scoped**: Has clear in/out boundaries so the researcher knows when they're done
+
+Bad: "Study high-entropy alloys"
+Better: "Characterize mechanical properties of HEAs"
+Good: "How does Cr content affect yield strength and ductility in CoCrFeMnNi alloys processed by arc melting?"
+
+## Socratic Narrowing Is the Orchestrator's Job
+
+The interview narrows in five moves: domain, then property or phenomenon, then conditions and processing route, then hypothesis, then explicit out-of-scope. The orchestrator runs those rounds. You read the transcript and judge whether the narrowing went far enough. If it did not, say exactly which move is missing and what to ask.
+
+Do not fill gaps with assumptions. Vague prompts lead to unfocused research.
+
+
+
+Generate three candidate research prompts at different levels of ambition. For each, propose a scope and keywords so the researcher can decide in one turn:
+
+**Option A (Focused):** Narrowest, most achievable for the stated timeline and resources
+**Option B (Standard):** Moderate scope, typical for a journal article
+**Option C (Ambitious):** Broader, suitable if timeline and resources allow
+
+For every option include:
+- The prompt as one specific, answerable question
+- In scope: 3 to 5 concrete items (materials, phenomena, conditions, methods)
+- Out of scope: 2 to 4 explicit exclusions
+- Keywords: 5 to 8 terms, marked primary or secondary
+- Feasibility note: one line on why it fits (or strains) the stated resources and timeline
+
+Return the three candidates for researcher selection; write identity files only after the selection is settled.
+
+
+
+## Complete action guides
+
+Read only the guide for the requested operation; it contains its interview and
+state transitions. Resolve these links from this skill directory.
+
+- [identify-research](../../assets/actions/identify-research.md)
+- [wtfp](../../assets/actions/wtfp.md)
+- [help](../../assets/actions/help.md)
+- [status](../../assets/actions/status.md)
+- [progress](../../assets/actions/progress.md)
+- [settings](../../assets/actions/settings.md)
+- [checkpoint](../../assets/actions/checkpoint.md)
+- [pause-research](../../assets/actions/pause-research.md)
+- [resume-research](../../assets/actions/resume-research.md)
+- [upload-data](../../assets/actions/upload-data.md)
+- [add-task](../../assets/actions/add-task.md)
+- [remove-task](../../assets/actions/remove-task.md)
+- [archive-task](../../assets/actions/archive-task.md)

package/library/plugins/materio/skills/materio-task-executor/SKILL.md

@@ -0,0 +1,214 @@
+---
+name: materio-task-executor
+description: "Produce type-specific artifacts for one approved materials-science task and verify the files."
+---
+
+Execute one researcher-approved task specification under its selected .research/tasks/task-NN/ directory. Read dependency outputs, lab constraints, and registered inputs. Write the type-specific artifacts and task-NN-SUMMARY.md; distinguish prepared artifacts from measured or computed results. Return complete, blocked, or needs_input with checkpoint kind decision/human-action/human-verify. The interactive caller reads files back, resolves findings, and updates workflow state.
+
+Read the [shared research policy](../../assets/references/research-policy.md) for
+state, provenance, execution boundaries, and advisory validation.
+
+Read the linked references when needed. Resolve links from this skill directory.
+If acting as a worker, return questions to the orchestrator; when acting as the
+interactive assistant, collect the researcher answers directly using the host's
+conversation facility.
+
+- [research-domains.md](../../assets/references/research-domains.md)
+- [traditional-workflows.md](../../assets/references/traditional-workflows.md)
+- [WORKFLOW.md](../../assets/templates/WORKFLOW.md)
+- [VIRTUAL-LAB.md](../../assets/templates/VIRTUAL-LAB.md)
+
+# Canonical task output contracts
+
+The five per-type file contracts and format blocks below are copied verbatim
+from the restored canonical executor. The literature retrieval steps use available host capabilities; the scientific output contracts are unchanged.
+
+
+<output_scope>
+Apply the output contracts below within the caller's explicit write grant.
+Update `.research/LITERATURE.md` only when that path is authorized; otherwise put
+proposed updates in the task summary for the orchestrator. Record actual supplied
+files and provided URLs inspected in Sources Reviewed. Never represent generated
+protocols, scripts or figure descriptions as performed experiments or measured
+results. The orchestrator handles writing tasks through the paper handoff workflow.
+</output_scope>
+
+When spawned, read the `<task>` block and identify its **type**. Execution behavior differs by type:
+
+---
+
+## Type: `literature`
+
+**What you do:** Read supplied materials and researcher-provided URLs, then synthesize papers on the task topic.
+
+**Execution:**
+1. Read `<data_files>` first: every registered paper, BibTeX file, or note relevant to this task is the primary corpus. Read each one before searching anything.
+2. If `<web_allowed>` is true, config permits fetching, and URL retrieval is available, fetch only the specific URLs the researcher provided in `<provided_urls>`. Use only retrieval capabilities actually provided by the host. If fetching is disabled/unavailable or no URLs were supplied, work from the supplied materials and record that coverage in Sources Reviewed. Request missing sources through a checkpoint rather than inventing papers or search results.
+3. Use URL retrieval to inspect the provided abstract/full-text URL and record the actual inspection depth and provenance. Supplied files come first; do not claim a PDF was read when only its filename or metadata was accessible.
+4. Synthesize findings into a structured summary
+5. Identify which papers are most relevant to the research gap
+6. Quote every paper title in the summary and put a DOI in the BibTeX entry when known. Never invent bibliographic details; mark uncertain entries `[unverified]`. The orchestrator runs a Crossref check and shows flags to the researcher.
+
+**Output files:**
+- `task-NN-literature-summary.md`; structured synthesis by sub-topic
+- `task-NN-references.bib`; BibTeX entries for key papers (formatted correctly)
+- Updates to `.research/LITERATURE.md` if new gaps found
+
+**Output format in summary:**
+```markdown
+# Literature Summary: [task name]
+
+## Key Findings by Sub-topic
+
+### [Sub-topic]
+[synthesis; what is known, what is debated]
+
+## Most Relevant Papers
+| Paper | Relevance | Key Finding |
+|-------|-----------|-------------|
+| [ref] | [HIGH/MED] | [1 line] |
+
+## New Gaps Identified
+[Any gaps found that weren't in the original LITERATURE.md]
+```
+
+---
+
+## Type: `experimental`
+
+**What you do:** Generate a detailed experimental protocol and data recording template.
+
+**Execution:**
+1. Read task description, assumptions, and expected outputs from WORKFLOW.md
+2. Generate a step-by-step experimental protocol appropriate to the material and measurement
+3. Include: safety considerations, equipment settings, sample preparation steps, measurement procedure, data recording format
+4. Generate a data recording template (spreadsheet structure or table)
+5. Flag any assumption that needs verification before lab work begins
+
+**Output files:**
+- `task-NN-protocol.md`; detailed experimental protocol
+- `task-NN-data-template.md`; data recording structure with column headers and units
+- `task-NN-checklist.md`; pre-experiment verification checklist
+
+**Protocol format:**
+```markdown
+# Experimental Protocol: [task name]
+
+## Safety Notes
+[relevant hazards; chemicals, high voltage, high temperature, etc.]
+
+## Materials and Equipment
+- [list with specifications]
+
+## Sample Preparation
+Step 1: [action]; [expected result]; [how to verify]
+Step 2: ...
+
+## Measurement Procedure
+Step 1: [action]; [parameters]; [what to record]
+
+## Data to Record
+[table with: measurement, units, conditions, notes column]
+
+## Expected Results
+[from task assumptions; what would confirm success]
+
+## Troubleshooting
+| Symptom | Likely Cause | Fix |
+|---------|--------------|-----|
+```
+
+---
+
+## Type: `computational`
+
+**What you do:** Generate simulation/calculation input files and analysis scripts.
+
+**Execution:**
+1. Read task assumptions for: method, software, system, parameters
+2. Generate appropriate input files or scripts for the specified software
+3. Include convergence testing guidance
+4. Generate post-processing analysis script
+
+**Supported methods and outputs:**
+- DFT (VASP): INCAR, POSCAR, KPOINTS, licensed POTCAR setup instructions, submission script
+- DFT (Quantum ESPRESSO): pw.x namelists/cards, pseudopotential setup instructions, submission script
+- MD (LAMMPS): input script, force field notes, analysis scripts (OVITO/MDAnalysis)
+- Phase-field: parameter file + solver notes
+- CALPHAD: Thermo-Calc/Pandat script outline
+- High-throughput: screening workflow script (Python + Materials Project API)
+
+**Output files:**
+- `task-NN-input/`; input files or templates
+- `task-NN-run.sh`; job submission script (SLURM or local)
+- `task-NN-analysis.py`; post-processing script
+- `task-NN-README.md`; how to run + expected outputs
+
+---
+
+## Type: `data-analysis`
+
+**What you do:** Analyze uploaded data files and produce figures and results summary.
+
+**Execution:**
+1. Read DATA-INDEX.md to find relevant data files for this task
+2. Inspect data structure (headers, units, data types)
+3. Write analysis code appropriate to the data type:
+   - Mechanical test data (stress-strain): Young's modulus, yield stress, UTS extraction
+   - XRD data: peak identification, lattice parameter extraction, Rietveld outline
+   - EIS data: equivalent circuit fitting outline
+   - Microstructure images: grain size analysis, phase fraction outline
+   - Computational output: energy, force, trajectory analysis
+4. Generate figures with proper labels, units, and scientific formatting
+
+**Output files:**
+- `task-NN-analysis.py` (or .m for MATLAB); analysis code
+- `task-NN-results-summary.md`; key numerical results with uncertainty estimates
+- `task-NN-figures/`; placeholder descriptions for each figure (actual generation requires running the code)
+
+**Results summary format:**
+```markdown
+# Results: [task name]
+
+## Key Numerical Results
+| Quantity | Value | Uncertainty | Units | Method |
+|----------|-------|-------------|-------|--------|
+| [e.g., Yield stress] | [X] | [±Y] | [MPa] | [0.2% offset] |
+
+## Comparison to Expectations
+[from task assumptions; did results match, exceed, fall short?]
+
+## Anomalies or Concerns
+[anything unexpected that needs investigation]
+```
+
+---
+
+## Type: `analytical`
+
+**What you do:** Develop mathematical models, derive equations, validate against theory or data.
+
+**Execution:**
+1. Identify the physical model appropriate to the task
+2. State assumptions and governing equations
+3. Derive/adapt the model for the specific material system
+4. Validate against known limits or available data
+5. Identify the parameter sensitivity (which inputs matter most)
+
+**Output files:**
+- `task-NN-model.md`; derivation, equations, assumptions, validity range
+- `task-NN-validation.md`; comparison to limiting cases or data
+- `task-NN-implementation.py`; numerical implementation if needed
+
+Read supplied files and the data index first. Fetch only researcher-provided URLs
+when project policy and the available host retrieval capability permit it. Record
+actual inspection depth, failed/unreadable sources, and coverage. Metadata alone
+is not full-text inspection, and a restricted corpus does not establish global
+absence. Ask for usable text if an unreadable paper blocks the research.
+
+## Complete action guides
+
+Read only the guide for the requested operation; it contains its interview and
+state transitions. Resolve these links from this skill directory.
+
+- [execute-task](../../assets/actions/execute-task.md)

package/library/plugins/materio/skills/materio-task-verifier/SKILL.md

@@ -0,0 +1,46 @@
+---
+name: materio-task-verifier
+description: "Independently inspect research task outputs against their approved assumptions, artifacts, and evidence."
+---
+
+Independently read one approved task specification, its actual output inventory, and summary. Check output completeness, assumptions, provenance, units, uncertainty, and scientific claims. Return checks performed, findings, and complete/blocked/needs_input with checkpoint kind. Keep files unchanged; expert sign-off remains a human-verify checkpoint.
+
+Read the [shared research policy](../../assets/references/research-policy.md) for
+state, provenance, execution boundaries, and advisory validation.
+
+Read the linked references when needed. Resolve links from this skill directory.
+If acting as a worker, return questions to the orchestrator; when acting as the
+interactive assistant, collect the researcher answers directly using the host's
+conversation facility.
+
+- [WORKFLOW.md](../../assets/templates/WORKFLOW.md)
+- [RESEARCH.md](../../assets/templates/RESEARCH.md)
+
+# Independent task verification
+
+Treat the workflow task as an output contract. Check every expected file against
+the actual task directory and read the summary; executor self-report is not
+evidence of existence or correctness. Preserve researcher-approved assumptions,
+resource constraints and dependency requirements. Distinguish generated protocols
+and unrun code from experiments or computed results. Inspect units, uncertainty,
+source/claim traceability and explicit limits of validity. A citation entry alone
+cannot establish a source supports a claim.
+
+Report missing files, unsupported results or contradictory state as failed
+validations. Advisory physics/citation/script warnings are findings for the
+researcher, not permission to remove or rewrite work. Record a researcher's
+accepted exception faithfully; do not invent consent. A passing file inspection
+is not proof of general physical correctness or successful execution.
+
+Describe read/ls checks as artifact inspection. They do not establish a
+command-backed scientific validation. Keep any host grounding limitation visible;
+do not invent command receipts or claim an ungrounded check passed. A rejected
+host validation remains incomplete and is returned to the caller.
+
+
+## Complete action guides
+
+Read only the guide for the requested operation; it contains its interview and
+state transitions. Resolve these links from this skill directory.
+
+- [execute-task](../../assets/actions/execute-task.md)

package/library/plugins/materio/skills/materio-workflow-planner/SKILL.md

@@ -0,0 +1,79 @@
+---
+name: materio-workflow-planner
+description: "Build a resource-aware dependency plan with researcher assumptions and tagged defaults."
+---
+
+Choose and customize one of the six research workflows with the researcher. Interview assumptions for each task type. Read .research/VIRTUAL-LAB.md and mark feasibility unchecked if absent. Write .research/WORKFLOW.md with stable task IDs, dependency ordering, researcher-origin assumptions and unconfirmed defaults, and all decision/human-action/human-verify checkpoints. Confirm defaults and alternatives before execution.
+
+Read the [shared research policy](../../assets/references/research-policy.md) for
+state, provenance, execution boundaries, and advisory validation.
+
+Read the linked references when needed. Resolve links from this skill directory.
+If acting as a worker, return questions to the orchestrator; when acting as the
+interactive assistant, collect the researcher answers directly using the host's
+conversation facility.
+
+- [traditional-workflows.md](../../assets/references/traditional-workflows.md)
+- [WORKFLOW.md](../../assets/templates/WORKFLOW.md)
+- [VIRTUAL-LAB.md](../../assets/templates/VIRTUAL-LAB.md)
+- [RESEARCH.md](../../assets/templates/RESEARCH.md)
+
+## Plans Are Prompts
+
+WORKFLOW.md is not a project management document. It IS the executable specification. Each task entry must contain everything the task-executor needs to run it without interpretation; specific inputs, expected outputs, and documented assumptions.
+
+## Assumptions Are Research Decisions
+
+Every assumption in a research workflow is a scientific decision. "We assume linear elastic behavior" is not just a simplification; it's a testable claim that could be wrong and should be documented. Good assumptions are:
+- **Explicit**: Written down, not implied
+- **Justified**: Why this assumption is reasonable
+- **Testable**: How you'd know if the assumption breaks
+
+Assumptions the researcher stated in the interview are theirs; record them verbatim with `[researcher]`. Assumptions you supplied are defaults; mark them `[planner default, confirmation pending]`.
+
+## Task Atomicity
+
+Each task should be completable in one focused work session (hours to days, not weeks). If a task is too large, split it. Signs of an oversized task:
+- Multiple distinct outputs
+- Multiple methods applied
+- Results from one part needed before another part can proceed
+
+## Traditional Workflows as Starting Points
+
+Traditional workflows encode decades of research practice. They are starting points, not constraints. Honor the researcher's customizations and document why standard steps were modified or skipped.
+
+
+
+If VIRTUAL-LAB.md is provided, check every task against its Resource-to-Task Mapping table:
+- Required resource available → feasible
+- Required resource has a gap → flag with ⚠ and the alternative from VIRTUAL-LAB.md
+- Required resource completely unavailable with no alternative → mark `BLOCKED` and propose removing or replacing the task
+
+Example flags:
+- "⚠ Task 05 (TEM characterization): No in-house TEM. External facility available (2–3 week lead time); add booking step."
+- "⚠ Task 07 (DFT with VASP): No VASP license. Alternative: Quantum ESPRESSO (free, installed on HPC)."
+
+Every flag goes into the return block for the researcher's decision. Apply the alternative provisionally so the workflow is complete either way.
+
+If VIRTUAL-LAB.md is missing, note in Workflow Decisions that feasibility was not checked.
+
+## Step 5: Attach Assumptions
+
+For each task, write the assumptions from `<assumptions>` verbatim, tagged `[researcher]`. Cover, per type, at least:
+
+- **experimental**: sample preparation route and contamination risks; characterization tools and resolution; test conditions and standards (ASTM/ISO); sample size and replicates; success criteria
+- **computational**: method and why; software; functional or force field; system size and timescale vs available resources; validation benchmark
+- **data-analysis**: data source; statistical approach; outlier handling; visualizations needed; software and libraries
+- **literature**: sub-topic scope; inclusion criteria; priority authors; output format
+- **analytical**: governing model; boundary conditions; validation limit cases
+
+Where the interview left a slot empty, supply a defensible default tagged `[planner default, confirmation pending]` and add it to the return block.
+
+
+
+## Complete action guides
+
+Read only the guide for the requested operation; it contains its interview and
+state transitions. Resolve these links from this skill directory.
+
+- [define-research-tasks](../../assets/actions/define-research-tasks.md)

package/library/plugins/materio/tests/test_check_physics.py

@@ -0,0 +1,139 @@
+#!/usr/bin/env python3
+"""
+Unit tests for the physical-sanity checker. Deterministic, no network.
+
+The most important tests are the *negative* ones: legitimately-negative or
+in-range materials-science values must produce ZERO findings, because a
+guardrail that cries wolf gets turned off.
+
+Run:  python3 tests/test_check_physics.py     (or: python3 -m unittest)
+"""
+import importlib.util
+import os
+import unittest
+
+_HERE = os.path.dirname(os.path.abspath(__file__))
+_MOD = os.path.join(_HERE, "..", "assets", "scripts",
+                    "check_physics.py")
+_spec = importlib.util.spec_from_file_location("check_physics", _MOD)
+cp = importlib.util.module_from_spec(_spec)
+_spec.loader.exec_module(cp)
+
+
+def run(text):
+    fnd = cp.Findings()
+    for check in cp.CHECKS:
+        check(text, "t.md", fnd)
+    return fnd
+
+
+class TestNoFalsePositives(unittest.TestCase):
+    """Valid MS values, including legitimately-negative ones, must be silent."""
+
+    CASES = [
+        "DFT total energy: -8.35 eV/atom",
+        "Formation enthalpy -45 kJ/mol at 0 K",
+        "Residual stress -250 MPa (compressive)",
+        "Ti-6Al-4V density 4.43 g/cm^3",
+        "Anneal at 1200 K then 850 °C; cryogenic 77 K",
+        "Relative density 99.8%, porosity 0.2%",
+        "Scan window 250–300 W, hatch 5-10 µm",          # en-dash + hyphen range
+        "Composition: Ti 90 wt%, Al 6 wt%, V 4 wt%",       # sums to 100
+        "Volumetric energy density 105 J/mm^3",
+        "Thermal expansion coefficient -1.2e-6 /K",         # negative is fine
+    ]
+
+    def test_no_findings(self):
+        for text in self.CASES:
+            fnd = run(text)
+            self.assertEqual(fnd.errors, [], f"unexpected error for: {text}")
+            self.assertEqual(fnd.warnings, [], f"unexpected warn for: {text}")
+
+
+class TestTemperature(unittest.TestCase):
+    def test_negative_kelvin(self):
+        self.assertEqual(len(run("Cool to -5 K").errors), 1)
+
+    def test_below_abs_zero_celsius(self):
+        self.assertEqual(len(run("Bath at -300 °C").errors), 1)
+
+    def test_implausibly_high_kelvin_warns(self):
+        f = run("Furnace at 500000 K")
+        self.assertEqual(f.errors, [])
+        self.assertEqual(len(f.warnings), 1)
+
+    def test_negative_rate_and_delta_not_flagged(self):
+        # Temperature differences / rates / gradients are legitimately signed.
+        for text in ("Cooling rate: -50 K/s during quench",
+                     "Temperature change per pass: ΔT = -5 K",
+                     "Thermal gradient -12 K/mm at the interface"):
+            self.assertEqual(run(text).errors, [], f"false positive: {text}")
+
+    def test_absolute_negative_kelvin_still_flagged(self):
+        # No delta/rate/gradient context -> a genuine below-absolute-zero error.
+        self.assertEqual(len(run("Cool the sample to -5 K").errors), 1)
+
+
+class TestDensity(unittest.TestCase):
+    def test_nonpositive_density(self):
+        self.assertEqual(len(run("density -2.1 g/cm^3").errors), 1)
+        self.assertEqual(len(run("density 0 g/cm^3").errors), 1)
+
+    def test_kg_per_m3_normalized(self):
+        # 4430 kg/m^3 == 4.43 g/cm^3 — valid, no finding.
+        self.assertEqual(run("density 4430 kg/m^3").errors, [])
+        self.assertEqual(run("density 4430 kg/m^3").warnings, [])
+
+    def test_implausibly_high_warns(self):
+        self.assertEqual(len(run("phase at 45 g/cm^3").warnings), 1)
+
+
+class TestFractions(unittest.TestCase):
+    def test_wt_percent_over_100(self):
+        self.assertEqual(len(run("Cr 105 wt%").errors), 1)
+
+    def test_bounded_bare_percent(self):
+        self.assertEqual(len(run("Porosity: 120%").errors), 1)
+        self.assertEqual(len(run("Impurity content -3%").errors), 1)
+
+    def test_unbounded_bare_percent_ignored(self):
+        # A bare % with no bounded-quantity keyword is not sign/range-checked.
+        self.assertEqual(run("improved by 250% over baseline").errors, [])
+
+    def test_relative_change_of_bounded_quantity_ignored(self):
+        # "efficiency" is a bounded keyword, but a relative change can exceed
+        # 100% and must not be flagged as impossible.
+        self.assertEqual(run("Efficiency improved by 250% over baseline").errors, [])
+        self.assertEqual(run("Yield increased 150% relative to control").errors, [])
+
+    def test_absolute_bounded_percent_still_flagged(self):
+        self.assertEqual(len(run("Measured porosity: 120%").errors), 1)
+
+
+class TestComposition(unittest.TestCase):
+    def test_inline_sums_off(self):
+        f = run("Fe 70 wt%, Cr 18 wt%, Ni 9 wt%")   # 97
+        self.assertEqual(len(f.warnings), 1)
+
+    def test_inline_sums_ok(self):
+        self.assertEqual(run("Ti 90 wt%, Al 6 wt%, V 4 wt%").warnings, [])
+
+    def test_vertical_block(self):
+        text = "| Fe | 70 wt% |\n| Cr | 18 wt% |\n| Ni | 9 wt% |\n"
+        self.assertEqual(len(run(text).warnings), 1)
+
+    def test_scattered_percentages_not_summed(self):
+        text = ("Yield improved 40 wt% in trial one.\n\n"
+                "Separately, additive was 30 wt% of the binder.\n")
+        # Non-contiguous single values -> no bogus composition sum.
+        self.assertEqual(run(text).warnings, [])
+
+
+class TestExitAndJson(unittest.TestCase):
+    def test_scan_and_counts(self):
+        fnd = cp.scan([_MOD])   # scanning the source file itself: no findings
+        self.assertEqual(fnd.errors, [])
+
+
+if __name__ == "__main__":
+    unittest.main(verbosity=2)