Tighten community smoke coverage for workflow-preset assets

[bigsmartben]

Summary

The community bundle smoke should validate the exact wheel artifact built from the PR checkout before running specify init, and should assert the installed workflow-preset manifest and registry versions match the intended bundled version.

Why

A mismatch can occur when the local checkout has workflow-preset updates but CI installs or validates through a path that does not prove the built wheel contains the same bundled preset metadata. This can allow specify init to install an older workflow preset, such as 1.3.0, even when the target bundled version is 1.3.1.

Proposed validation

• Build a wheel from the current checkout in community smoke.
• Install the CLI from that built wheel.
• Run specify init and assert .specify/presets/workflow-preset/preset.yml and .specify/presets/.registry both report 1.3.1.
• Verify extension remove/re-add smoke checks do not pass from stale skill files.

[bigsmartben]

Closing this upstream tracking issue because the change belongs in the integration fork path first; upstream main no longer contains this community smoke/workflow-preset surface.