Add Print-OS agent surfaces

[simongonzalezdc]

Summary

• add Print-OS local CLI for manifests, job payloads, local API reads, and job creation
• add local stdio MCP server plus .mcp.json discovery
• add public skill metadata and update README, llms, runbook, and AGENTS docs
• add backend tests for the new agent surfaces

Verification

• python3 -m py_compile tools/print_os_cli.py tools/print_os_mcp.py
• python3 tools/print_os_cli.py manifest --format json
• python3 tools/print_os_cli.py job-payload --name "Test Bracket" --material PLA --width 40 --depth 20 --height 12
• python3 tools/print_os_mcp.py --self-test
• tools/list MCP smoke via stdin
• cd caedo-api && python3 -m pytest -q

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 98e52df93c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Point api-get resources at JSON endpoints

When users run api-get business or call MCP print_os_api_get with business, this maps to /api/v1/business/summary, but the checked business router only exposes GET /forecast plus POST-only endpoints, so the advertised read always 404s. The CLI also offers system, but /api/v1/system/backup returns a ZIP FileResponse while request_json always decodes and parses JSON, so that choice fails against a running backend too; remove these resource choices or map them to real JSON GET endpoints.

Useful? React with 👍 / 👎.