procesio-cli-maintainer

Start with a failing contract-level test, then update the manifest and implementation together with typed arguments, stable output and error shapes, and reversibility classification. Regenerate the router and manuals from structural sources, run focused then full tests, and verify the real CLI invocation path.

procesio-cli operates a PROCESIO workspace, such as running processes and verifying outputs. procesio-cli-maintainer changes the repository source code itself, including manifests, MCP servers, generated routers, CI gates, and tests.

Use agent-skill-engineer when the primary deliverable is an Agent Skill package, SKILL.md authoring, routing boundaries, or behavioral evaluation. Return to procesio-cli-maintainer only for repository-specific integration, generation, translations, CI, and release controls.

No. Generated router and manual files must be reproducible from structural sources, so changes go into the manifest or generator and outputs are regenerated. CI runs build-router --check to fail on drift between sources and generated files.

Run the offline gates: pytest across tools, agents, dashboard, webplatform and skills, strict skill validation, catalog and routing evaluation, governance checks, secret scanning, and the generated-file check. Commit only a green unit and never claim CI is green without observing the actual run.

Prefer extending optional fields on existing operations over adding tools, keep existing tool names and required arguments, and confine resource access to an established root rejecting traversal and symlink escapes. Test protocol listing, old calls, new calls, and error paths without live credentials.