…tion

Stacks on top of PR #64 (engine_parallel absorption) — engine-parallel no
longer depends on shipper-execution-core externally.

Move ~2100 LOC (92 LOC of impl + ~2000 LOC of tests/proptests/snapshots)
into crates/shipper/src/runtime/execution/mod.rs as the sole submodule of
the new runtime/ layer directory. No in-tree duplicate or _micro.rs shim
existed — pure relocation. Update all `use shipper_execution_core::X` to
`use crate::runtime::execution::X` across shipper (engine/mod.rs,
engine/parallel/publish.rs, engine/parallel/mod.rs, engine/parallel/tests.rs).

Fuzz target `fuzz/fuzz_targets/execution_core.rs` now imports from
`shipper::runtime::execution::*` (fuzz crate already depends on shipper).
Remove the `shipper-execution-core` entry from `fuzz/Cargo.toml`.

Move the two BDD tests from `crates/shipper-execution-core/tests/execution_core_bdd.rs`
into `crates/shipper/tests/execution_bdd.rs`. Rename snapshot files from
`shipper_execution_core__tests__snapshots__*` to
`shipper__runtime__execution__tests__snapshots__*` and update their
`source:` metadata. Enable the `yaml` feature on shipper's insta dev-dep.

Items are exposed as `pub` (rather than `pub(crate)`) because the external
fuzz target exercises them directly; this exception is documented in
`runtime/execution/CLAUDE.md` and will be tightened in a later pass.

Delete crates/shipper-execution-core, drop it from the workspace members,
remove the dep from shipper's Cargo.toml, and purge it from
docs/architecture.md and RELEASE_CHECKLIST_v0.3.0.md.

Per docs/decrating-plan.md §6 Phase 2.

Post-rebase of PR #64 on top of main's policy absorption and registry
split, the engine::parallel submodule needed API updates that were not
included in the merged PR:

- shipper_policy -> crate::runtime::policy (policy was absorbed in main)
- shipper_registry::RegistryClient -> HttpRegistryClient alias
  (the parallel path operates on base-URL, not Registry struct; the full
  Registry-aware client is named RegistryClient and takes a different
  constructor after the registry lib split)

Fixes compilation of shipper crate on main after PR #64 merge.

…tmerge

fix(engine/parallel): restore imports after PR #64 absorption drift

After rebasing PR #70 (plan+levels+chunking absorption replay) onto
current main (which has PR #64's engine_parallel absorption), three
drift corrections are needed:

- engine::parallel::{mod,publish,tests}.rs: `shipper_plan::PlannedWorkspace`
  -> `crate::plan::PlannedWorkspace`; `shipper_chunking::chunk_by_max_concurrent`
  -> `crate::plan::chunking::chunk_by_max_concurrent`. The parallel engine
  was absorbed into shipper itself (PR #64), so it references sibling modules
  directly instead of the former microcrates.
- engine::parallel::run_publish_parallel: drop the shipper_plan reconstruction
  dance (both sides use the same shipper_types::PlannedWorkspace) and forward
  the host ws directly to run_publish_parallel_inner.
- plan::mod.rs: `crate::state::CURRENT_PLAN_VERSION` -> `crate::state::execution_state::CURRENT_PLAN_VERSION`
  (the const is re-exported from shipper-state via state::execution_state).
- plan::chunking::chunk_by_max_concurrent: promote `pub(crate)` to `pub` so
  the integration BDD test (`tests/engine_parallel_chunking_bdd.rs`) and the
  engine::parallel re-export can reach it.
- engine::parallel::mod.rs: `pub use crate::plan::chunking::chunk_by_max_concurrent`
  preserves the former `shipper::engine::parallel::chunk_by_max_concurrent`
  public surface for consumers.

…tion

Stacks on top of PR #64 (engine_parallel absorption) — engine-parallel no
longer depends on shipper-execution-core externally.

Move ~2100 LOC (92 LOC of impl + ~2000 LOC of tests/proptests/snapshots)
into crates/shipper/src/runtime/execution/mod.rs as the sole submodule of
the new runtime/ layer directory. No in-tree duplicate or _micro.rs shim
existed — pure relocation. Update all `use shipper_execution_core::X` to
`use crate::runtime::execution::X` across shipper (engine/mod.rs,
engine/parallel/publish.rs, engine/parallel/mod.rs, engine/parallel/tests.rs).

Fuzz target `fuzz/fuzz_targets/execution_core.rs` now imports from
`shipper::runtime::execution::*` (fuzz crate already depends on shipper).
Remove the `shipper-execution-core` entry from `fuzz/Cargo.toml`.

Move the two BDD tests from `crates/shipper-execution-core/tests/execution_core_bdd.rs`
into `crates/shipper/tests/execution_bdd.rs`. Rename snapshot files from
`shipper_execution_core__tests__snapshots__*` to
`shipper__runtime__execution__tests__snapshots__*` and update their
`source:` metadata. Enable the `yaml` feature on shipper's insta dev-dep.

Items are exposed as `pub` (rather than `pub(crate)`) because the external
fuzz target exercises them directly; this exception is documented in
`runtime/execution/CLAUDE.md` and will be tightened in a later pass.

Delete crates/shipper-execution-core, drop it from the workspace members,
remove the dep from shipper's Cargo.toml, and purge it from
docs/architecture.md and RELEASE_CHECKLIST_v0.3.0.md.

Per docs/decrating-plan.md §6 Phase 2.

PR #60 landed shim absorption (re-exports from crate::state::events and
crate::state::execution_state pointing at standalone crates) because
shipper-store (PR #57) and shipper-engine-parallel (PR #64) had trait-
signature deps on them. Both blockers landed via merge train round 2,
unblocking this physical removal.

Move 2821 LOC (events) + 2725 LOC (state) from standalone crates into
crates/shipper/src/state/events/ and crates/shipper/src/state/execution_state/
as absorbed modules.

Events split into three files:
 - mod.rs (production: EventLog, EVENTS_FILE, events_path)
 - tests.rs (unit + insta snapshot tests)
 - proptests.rs (property-based tests)

Execution-state split into two files:
 - mod.rs (production: atomic write, migration, encrypted I/O)
 - tests.rs (unit + snapshot tests; nested proptests + proptests_extended
   submodules preserved)

Snapshots relocated and renamed for the new module path
(shipper__state__events__tests__* and
shipper__state__execution_state__tests__*).  Integration test moved to
crates/shipper/tests/state_integration.rs (was
crates/shipper-state/tests/state_integration.rs) with imports rewritten to
use shipper::state::execution_state::*.

shipper-events fuzz target (fuzz/fuzz_targets/event_log_roundtrip.rs)
repointed to shipper::state::events::EventLog; its shipper-events dep
removed from fuzz/Cargo.toml.

Internal shipper imports rewritten:
 - shipper_events → crate::state::events
 - shipper_state → crate::state::execution_state
 - shipper_environment::collect_environment_fingerprint →
   crate::runtime::environment::collect_environment_fingerprint
   (also already absorbed; execution_state no longer needs the external dep)

Delete crates/shipper-events and crates/shipper-state. Remove from workspace
members and shipper's deps. CLAUDE.md files updated to reflect the now-
physically-absorbed state. docs/architecture.md updated to remove dangling
standalone-crate edges.

Per docs/decrating-plan.md §6 Phase 2 follow-up + §6.A R-PR-1..R-PR-5.

Validation: cargo check --workspace, cargo test -p shipper (1640 lib +
integration tests), cargo test -p shipper-cli, cargo clippy --workspace
--all-targets --all-features -- -D warnings, cargo fmt --all -- --check —
all green.