Fix workshop-rs-cli package isolation after the v0.2.0 partial release

[Teakowa]

Goal

Restore a publishable workshop-rs-cli package after the v0.2.0 release partially succeeded, without rewriting the existing v0.2.0 tag or published workshop-rs 0.2.0 crate.

Context

The v0.2.0 release published workshop-rs 0.2.0, then failed while verifying the workshop-rs-cli 0.2.0 package tarball. crates/workshop-rs-cli/src/census.rs compile-time includes localization fixtures from crates/workshop-rs/tests/fixtures/...; those sibling-crate files exist in the repository workspace but are absent from the isolated CLI package tarball.

This is a package-boundary regression introduced by #155. Workspace CI passed because it did not exercise the packaged crate in isolation.

Scope

• Remove workshop-rs-cli compile-time dependence on files outside its package boundary.
• Preserve the existing census behavior and localization probe content.
• Verify the CLI crate from the package artifact, not only from the workspace checkout.
• Recover through the next normal release line; do not rewrite or move the existing v0.2.0 tag/release.

Non-goals

• Changing Workshop semantics, census behavior, or the Replace standalone evidence domain with contract tests and acquisition tooling #152 ownership decision.
• Rewriting the existing v0.2.0 tag or republishing workshop-rs 0.2.0.
• Broad release-workflow redesign unrelated to this regression.

Acceptance criteria

• workshop-rs-cli has no compile-time source/data dependency on sibling-crate test fixtures.
• An isolated package verification for workshop-rs-cli succeeds.
• Existing workspace tests and census behavior remain unchanged.
• The recovery release uses the normal release-plz flow and advances the grouped release line rather than mutating v0.2.0.