[FLO-3.1] Bootstrap deterministic extension resolution and a hermetic execution seam

[szmyty]

Closes #23

Roadmap-Step: FLO-Q02

Summary

• bootstrap a Rust 2024 library with Rust 1.85 MSRV and closed models for all six extension-v1 contracts
• add deterministic manifest/lock/observation inspection, exact pin materialization, precedence/conflict/fallback evidence, and fail-closed trust handling
• add an opaque resolved-extension token plus a caller-injected in-process ExtensionPort and fallible, validated EventSink
• validate event/result identities, ordering, diagnostic flags, terminal/failure coherence, and bounded artifact-ID consistency
• add a no-effects, no-artifacts hermetic reference port, executable example, adversarial tests, CI, and updated FLO-Q02 documentation

Explicit boundary

This does not add a public CLI, discovery/dynamic loading, process execution, sandbox enforcement, real holon adapters, durable state, cancellation/resume, a logging backend, or an OpenTelemetry exporter. Declared limits are correlated metadata only; caller-issued configuration and authorization identities are not authenticated in this checkpoint. EventSink is the future observability attachment seam.

Verification

Validated on Rust 1.85.0 and stable Rust 1.98.1:

• cargo check --all-targets --locked
• cargo fmt --all -- --check
• cargo clippy --all-targets --all-features --locked -- -D warnings
• cargo test --all-targets --locked (48 integration tests)
• cargo test --doc --locked
• cargo run --example hermetic_extension --locked
• cargo package --locked
• all four repository validators
• git diff --check

The published head has the exact reviewed local tree 09383a502131eb080999577a1efd1a18203970c6.

[devactivity-app]

Pull Request Summary by devActivity

Metrics

Achievements

• @szmyty
  Earned XP: 10⭐
  Check Your Progress