embedctl 0.2.2

Scope notes

• Track follow-up 0.2.x fixes after the 0.2.1 release here.
• Reframed the public repository as generic embedded-device tooling instead of app-specific hardware readiness work.
• Kept current 0.2.x scope focused on evidence, agent UX, profiling, replay-oriented workflows, and modular embedded Linux/flutter-pi control surfaces.

Public cleanup and project framing

• Removed app-specific public profile fixtures, adapter workflow fixtures, readiness guidance, and AI command examples from the public repository.
• Renamed the app-specific session evidence artifact to app_session.json with schema embedctl.app_session.v0.
• Updated public documentation to describe embedctl as multi-device by design and multi-OS-ready by architecture.
• Added docs/supported-environments.md so tested, example, supported, and experimental environments can be accumulated with explicit confidence and recommended settings.
• Clarified that example profiles are fixtures for exercising CLI behavior, not broad support claims.

Evidence and release readiness

• Added release-check --target <id> --json [--evidence-dir <path>] so agents can evaluate release-build evidence without treating missing proof, fatal logs, QA bridge timeouts, or unknown .err files as a passing release result.
• Added bugreport --evidence-dir <path> import support that preserves collected evidence under evidence/<relativePath> instead of flattening files into logs/<basename>.
• Added recursive, path-preserving evidence inspection across evidence/ and logs/, including proof-sufficiency output that honors verdict.json, fatal log signals, bridge error evidence, and missing verdict fields.
• Added hierarchical evidence layout support with canonical build/, deploy/, runtime/, release/, and bridge/ paths while keeping legacy flat evidence directories as a compatibility fallback.

Bridge and workflow automation

• Preserved flow-step assertions and expect blocks in bridge batch planned JSON so workflow templates can keep human-readable acceptance checks even before live bridge execution exists.
• Clarified CLI help and plan/apply documentation so implemented bounded/read-only surfaces are separated from future live bridge, unbounded log streaming, provider mutation, power, measurement, and OTA integration scope.

Verification

• bash scripts/verify.sh passed locally before release.
• GitHub Actions CI passed for this release commit.