3 Commits

Author	SHA1	Message	Date
Paul Payne	fd562f7468	docs: clean up pre-existing staleness across the guides ... Sweep of accumulated drift unrelated to the CLI reorg: - Source paths: ~/.castle/code/<name> → /data/repos/<name> (REPOS_DIR), and source: code/X → absolute /data/repos/X. registry.md source-resolution table and 'how programs get in' section rewritten for the /data/repos layout. - Old field name component: → program: in all YAML examples. - Old term 'component' → 'program' throughout design.md and the stack guides. - Frontend serving: corrected the copy-to-artifacts/content model to serve-in- place from the repo (<source>/<dist>), matching Phase 2b; dropped the dead _copy_app_static reference and the 'runtime never references the source tree' claim (frontends are the deliberate exception). - Stale endpoints/commands: /components → /deployments; castle create/add → castle program create/add in the create.py/add.py docstrings. CLAUDE.md was already current. cli 24 green; ruff clean.	2026-06-14 16:32:13 -07:00
Paul Payne	5c6d8ec6f1	refactor(cli): resource-first command surface ... Names collide across resource types (a program and a service can share a name), so the CLI no longer resolves bare names. Operations live under the resource they act on; platform lifecycle and the cross-resource overview stay top-level. castle program list|info|create|add|clone|delete|run|install|uninstall| build|test|lint|format|type-check|check castle service list|info|create|delete|deploy|enable|disable|start|stop|restart|logs castle job <same verbs> (create takes --schedule) castle gateway start|stop|reload|status castle list | status | deploy [name] # cross-cutting castle start | stop | restart # whole platform (systemd verbs) Key changes: - info/delete/list/run are resource-scoped (no more cross-section name match). - delete only removes the named resource's entry; program delete still blocks when a deployment references it. - per-resource start/stop/restart (systemctl on the unit/timer); top-level start/stop/restart act on the whole platform. - expose → 'service create' (more general: --program ref, --runner); gained 'job create' (the CLI never had one). - dropped up/down — bringing things online is the honest 'deploy && start'. Docs (CLAUDE.md, registry.md, stack guides) and user-facing messages updated. core 94 / cli 24 / api 52 green; ruff clean. Verified live: program/service/job list+info scope correctly, service create+scoped-delete round-trips.	2026-06-14 16:25:34 -07:00
Paul Payne	3f3b88f17b	refactor: Align vocabulary — component → program / deployment ... Canonical terms (see docs/registry.md glossary): - program: any catalog entry (tool/daemon/frontend) — the software - service / job: how a program is deployed (systemd .service / .timer) - deployment: umbrella for the unified service+job+program view Changes: - core: ServiceSpec/JobSpec component: → program: (component accepted as back-compat validation_alias); DeployedComponent → Deployment. - api: ComponentSummary/Detail → DeploymentSummary/Detail; GET /components → /deployments; GatewayRoute.component → program; GatewayInfo .component_count → deployment_count; ServiceActionResponse/action keys component → program. - app: matching type renames, /components → /deployments hook, route /component/:name → /deployment/:name, GatewayRoute.program. - docs: component-registry.md → registry.md (+ canonical glossary); CLAUDE.md endpoint list refreshed (drop removed /tools, add typed program/service/job + config routes). Tests: core 92, cli 24, api 52 green; app build clean; ruff clean.	2026-06-14 11:05:22 -07:00