chore: initial scaffold — workspace, docs, blueprint

Sets up the PiCloud monorepo as a Cargo workspace organised around the
three-service architecture (manager / orchestrator / executor), each
backed by a *-core library crate so the same logic powers both the MVP
all-in-one `picloud` binary and the future split-process cluster mode.

  * crates/shared, executor-core, orchestrator-core, manager-core
    define the library surface and trait seams between the three
    services (`ExecutorClient`, `ScriptResolver`, `ScriptRepository`).
  * crates/picloud is the MVP entrypoint; serves /healthz on 8080
    (override via PICLOUD_BIND).
  * crates/picloud-{manager,orchestrator,executor} are skeleton
    binaries that keep the crate boundaries honest until cluster
    mode is built out in v1.3+.
  * docs/git-workflow.md defines the trunk-based workflow:
    short-lived branches, Conventional Commits, separate hotfix
    flow with mandatory reproduction tests.
  * CLAUDE.md captures the working rules for future Claude sessions.

Workspace passes `cargo fmt`, `cargo clippy -D warnings` (with
pedantic enabled), and `cargo test --workspace`. The all-in-one
binary responds on `/healthz` and `/`.

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

crates/orchestrator-core/src/lib.rs

@@ -0,0 +1,15 @@
+//! Per-node event ingress and dispatch.
+//!
+//! Owns the data-plane request path:
+//!   inbound event → resolve script → call `ExecutorClient::execute`
+//!
+//! Does not import `executor-core` types in its public surface beyond the
+//! transport DTOs (`ExecRequest`/`ExecResponse`). The `ExecutorClient`
+//! trait is the seam that lets the orchestrator call executor logic
+//! in-process (single-node) or over HTTP (cluster).
+
+pub mod client;
+pub mod resolver;
+
+pub use client::{ExecutorClient, LocalExecutorClient, RemoteExecutorClient};
+pub use resolver::{ResolverError, ScriptResolver};