## Test coverage audit + expansion: pipeio package Audit test coverage for `pac

Test coverage audit + expansion: pipeio package

Audit test coverage for packages/pipeio/ and schedule batch tasks to fill gaps.

Step 1: Audit

Run PYTHONPATH=src python -m pytest tests/ -q in packages/pipeio/ to see current count. Then map coverage: for each source module in src/pipeio/, count tested vs untested functions. Key modules to audit: - mcp.py — 50+ MCP tool functions - cli.py — CLI command dispatch - docs.py — docs_collect, docs_nav - registry.py — PipelineRegistry scan/validate - contracts.py — I/O validation - config.py — FlowConfig model - notebook/ — lifecycle, backend protocol, analyze

Step 2: Create task notes

For each coverage gap found, create a worklog issue note in the projio project describing: - Which functions need tests - What to test (happy path, edge cases, error paths) - Approach (fixtures, mocks, tmp_path patterns)

Step 3: Schedule

Use schedule_queue with batch_mode=True to schedule all the created task notes for background execution.

Important

• Run existing tests first to establish baseline
• Focus on MCP functions and registry (highest value)
• Use the existing test patterns in packages/pipeio/tests/ as templates
• Each spawned task should be self-contained (can run independently)

Related Notes

• issue-arash-20260412-013432-321867.md — Direct coverage gap for mcp/pipeio module, which this audit orchestrates
• issue-arash-20260412-013422-048012.md — Direct coverage gap for cli module, one of the key audit targets
• issue-arash-20260412-013344-955432.md — Direct coverage gap for config module, listed as key audit target
• issue-arash-20260412-013402-247547.md — Direct coverage gap for sync module, part of the audit scope
• issue-arash-20260412-013412-040281.md — Direct coverage gap for render module, part of the audit scope

Batch Result

• status: done
• batch queue_id: f935e979b30d
• session: c618c2d5-782b-483b-948e-bdf70925267d
• batch duration: 962.1s