Repair inherited CommunityAI CI baseline on Factory stack

[flujo-app]

PR32 and its PR35 sibling inherited CI failures that obscured source checks. This draft makes the style jobs and broad test matrices green, repairs a same-size source-rewrite packaging check, and moves both desktop packaging jobs through protocol tests and self-tests. Packaging now stops only when the bundle builder verifies the expired signed Qwen catalog.

• Run the complete desktop pytest suite in its own packaging step so PowerShell cannot mask a test failure with the following self-test. Add the pinned pytest dependency and shared test-document path.
• Install the desktop package and Linux Qt libraries in the broad test matrix. Canonicalize the macOS temporary-path fixture and use shorter, full-UUID Qt socket names within the Unix socket limit.
• Correct the catalog-withdrawal and historical cost test assumptions while retaining checks for stored model assets and live price expiry.
• Preserve Windows 8.3 path spelling through volunteer lifecycle argument construction; the fixed-profile sidecar still rejects outside-root paths, symlinks, and junctions. A real short-path regression covers the bug.
• Rehash runtime package sources and temporary hardlinks before replacing a destination. The regression mutates source bytes to the same length and restores its metadata, so size/mtime identity cannot hide the change.
• Apply pinned Black/isort formatting to the inherited failing paths; their non-import Python AST is unchanged.

Hosted validation on current head 8061f249: Black, isort, Ubuntu broad tests, and macOS broad tests pass. Linux and Windows packaging protocol tests, installed desktop self-tests, archive checks, and qualified-runtime checks pass. A local focused runtime packaging test passes 7/7. The branch is stacked on PR32 head 364959e.

Both package jobs then fail in Build and smoke unsigned public-alpha bundle: public-alpha/catalog-qwen-v2 contains a validly signed sequence-2 catalog that expired on 2026-09-28. A reviewed sequence-3 publication bundle with a current validity window is required. This PR neither renews it nor bypasses verification, and remains draft while that release gate is unresolved.