feat: custom routing — bind scripts to your own URLs

Scripts can now answer at user-chosen paths (e.g. /greet, /greet/:name,
/webhooks/*), on user-chosen hosts (strict or *.example.com wildcards),
on user-chosen methods. The internal /api/v1/execute/{id} endpoint
stays as the always-available ID-based bypass.

Routing rules (decided in design with the user; see chat history):

  Path kinds:
    exact   /greet              literal
    prefix  /greet/*            strict-subtree; stored as "/greet/";
                                does NOT match bare /greet (add an
                                exact route for that case)
    param   /users/:id          :name captures one whole segment;
                                mid-segment colons are rejected;
                                {name} is reserved for a future SDK

  Host kinds:
    any                         no Host header constraint
    strict  sub.example.com     literal match (case-insensitive)
    wildcard *.example.com      suffix match; multi-level subdomains OK

  Within-kind uniqueness:
    two routes of the same kind that could match the same request
    conflict at config time. Algorithm (orchestrator_core::routing::
    conflict):
      exact:  literal equality
      prefix: literal equality (longer-prefix coexists; longer wins
              at request time)
      param:  same segment count + same literals at every
              literal-vs-literal position (the user's example:
              :id vs :userId at same shape is a conflict)

  Request-time precedence:
    exact > param > prefix
    among non-exact: more leading-literal segments wins
    tie: param > prefix (more constrained)
    within prefix: longest matching prefix wins
    host bucket: strict > wildcard (longer suffix) > any; fall through
    to less specific buckets when path doesn't match

  Reserved path prefixes: /api/, /admin/, /healthz, /version

  Routes that look invalid at config time return 422 with the precise
  parse error; conflicting routes return 409 with the conflicting route
  in the body (so the dashboard can render the conflict inline).

What landed:

  * 0003_routes.sql — routes table (host_kind, host, host_param_name,
    path_kind, path, method, script_id) with UNIQUE index on the
    literal binding tuple. Schema 2 → 3.

  * shared::Route / HostKind / PathKind — flat storage shape that
    crosses wire boundaries cleanly.

  * orchestrator_core::routing — four sub-modules, all unit-tested:
      pattern.rs (16 tests)  parse + validate + display
      conflict.rs (12 tests) within-kind overlap predicate
      matcher.rs (12 tests)  runtime dispatch (specificity-aware)
      table.rs               Arc<RwLock<Vec<CompiledRoute>>>
                             shared by manager (writes) and
                             orchestrator (reads); atomic replace
                             after each admin write

  * manager-core::route_admin — five new admin endpoints under
    /api/v1/admin:
      POST   /scripts/{id}/routes      create
      GET    /scripts/{id}/routes      list per script
      DELETE /routes/{route_id}        delete (refreshes table)
      POST   /routes:check             pre-flight conflict check
                                       (powers the dashboard's
                                       live conflict warning)
      POST   /routes:match             synthetic URL → matched
                                       route + extracted params
                                       (powers the dashboard's
                                       match-preview tool)
    Stored path strings stay raw (user-typed); normalization
    happens only in the in-memory CompiledRoute so re-parses are
    idempotent.

  * orchestrator_core::api::user_routes_router — fallback handler
    mounted in picloud after the system routes. Reads Host /
    method / path / query from the request, dispatches via the
    table, builds an ExecRequest with params/query/rest filled,
    calls the executor, writes to the log sink. 10 MiB body cap.

  * executor-core::ctx (SDK 1.0 → 1.1) — adds
      ctx.request.params  (map of named-param captures)
      ctx.request.query   (parsed query string)
      ctx.request.rest    (suffix for prefix routes; "" otherwise)
    All three are always present (empty when not applicable) so
    scripts can read them unconditionally.

  * picloud::build_app — now async; loads routes at startup,
    populates the shared table, mounts route_admin_router under
    /api/v1/admin alongside the script CRUD, and the user-routes
    fallback at the app root.

  * caddy/Caddyfile + Caddyfile.prod widened: anything not
    /healthz, /version, /api/v1/admin/*, /api/v1/execute/*,
    /api/* (404 sunset), or /admin/* (dashboard) → picloud.

  * Dashboard moves to /admin/* via SvelteKit paths.base. Its
    internal Caddy strips the prefix and serves with SPA fallback.
    All in-app links use $app/paths. The dashboard URL is now
    http://localhost:8000/admin/ — one-time break for the new
    URL freedom users gained.

  * PICLOUD_PUBLIC_BASE_URL env var, exposed via /version so the
    dashboard renders full URLs for routes regardless of the
    operator's external port / TLS setup.

  * memory_limit_mb stays in the schema, still v1.3+ advisory.

Verified live through Caddy:
  /version              → schema 3, sdk 1.1, public_base_url
  GET /admin/           → 200, dashboard HTML containing "PiCloud"
  POST /api/v1/admin/scripts → 201
  POST .../scripts/{id}/routes (path=/greet/:name) → 201
  GET /greet/alice?lang=en → 200 {"name":"alice","q":"en"}
  POST conflicting route → 409 with conflicting_route body
  POST /admin/foo route → 422 "reserved"
  POST /api/v1/admin/routes:match → matched + params extracted
  GET /unbound-path → 404 JSON

Tests:
  * 40 routing unit tests (pattern + conflict + matcher tables)
  * 14 executor-core unit tests (one new for ctx.request.params/
    query/rest exposure)
  * 32 integration tests (10 new for routing CRUD + dispatch +
    conflict + reserved + specificity tie-break + match preview +
    delete invalidation + /version returns public_base_url)
  * default cargo test --workspace stays green; opt-in via
    DATABASE_URL + --include-ignored for the integration suite

Bumps: schema 2 → 3; SDK 1.0 → 1.1; product 0.3.0 → 0.4.0.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

caddy/Caddyfile

@@ -1,13 +1,19 @@
 # PiCloud dev Caddyfile.
 #
-# Same routing shape as prod, with two differences:
-#   - bound to plain HTTP (no domain, no automatic TLS)
-#   - upstreams are the docker-compose service names
+# Routing topology:
+#   /healthz, /version        → picloud (liveness + version, k8s-friendly)
+#   /api/v1/admin/*           → picloud (manager control plane)
+#   /api/v1/execute/{id}      → picloud (orchestrator ID-based bypass)
+#   /api/*                    → 404      (unsupported / sunset API version)
+#   /admin/*                  → dashboard SPA  (mounted with paths.base=/admin)
+#   everything else           → picloud (orchestrator route table; user paths)
 #
-# Control plane (`/api/admin/*`) and data plane (`/api/execute/*`, `/exec/*`)
-# both terminate on the `picloud` all-in-one for now; in cluster mode the
-# data-plane handles will list multiple orchestrator upstreams here while
-# the admin handle still points at a single manager.
+# The "everything else → picloud" rule is what makes user-defined paths
+# like /greet possible. picloud's matcher answers them via the routes
+# table, or returns 404 with a precise JSON error.
+#
+# When v2 of the API ships, add `handle /api/v2/admin/* { ... }` etc.
+# alongside the v1 handles, before the catch-all `/api/*` 404.
 {
 	auto_https off
 	admin off
@@ -19,7 +25,6 @@
 
 :80 {
 	handle /healthz {
-	handle /healthz {
 		reverse_proxy picloud:8080
 	}
 	handle /version {
@@ -27,29 +32,13 @@
 	}
 
 	handle /api/v1/admin/* {
-	# second `handle /api/v2/...` block while keeping v1 live for at
-	# least one product-minor deprecation window.
-
-	# Control plane → manager (single-process: picloud).
-	handle /api/v1/admin/* {
 		reverse_proxy picloud:8080
 	}
 	handle /api/v1/execute/* {
-	# Data plane → orchestrator (single-process: picloud).
-	handle /api/v1/execute/* {
 		reverse_proxy picloud:8080
 	}
 
 	handle /api/* {
-	# "your script runs against this body", so no API versioning applies.
-	handle /exec/* {
-		reverse_proxy picloud:8080
-	}
-
-	# Anything else under /api/* — old major versions that have been
-	# fully sunset, or typos. Fail loudly rather than silently serving
-	# the dashboard SPA.
-	handle /api/* {
 		respond 404 {
 			body "{\"error\":\"no such API version — see /version for supported routes\"}"
 			close
@@ -57,12 +46,22 @@
 	}
 
 	# Dashboard SPA at /admin. Its internal Caddy serves files from /srv
-	# dashboard container that already runs file_server with index.html
-	# fallback for client-side routing).
-	handle {
-		reverse_proxy dashboard:80
+	# (root); we don't strip the prefix because SvelteKit was built with
+	# paths.base = '/admin' so the bundle's URLs already include it.
+	handle /admin/* {
+		reverse_proxy dashboard:80
 	}
 	handle /admin {
+		# Bare /admin (no trailing slash) — let SvelteKit's SPA handle it.
+		reverse_proxy dashboard:80
+	}
+
+	# Everything else → picloud's user-route fallback. If no route
+	# matches, picloud responds 404 with a JSON body.
+	handle {
+		reverse_proxy picloud:8080
+	}
+
 	log {
 		output stdout
 		format console