[1.0] Qualify the release candidate across API, dashboard and interruption paths

Feature-level checks alone do not establish that the packaged release delivers the supported single-process SQLite workflow through its actual API and dashboard.

Scope

• Run the maintained deterministic vertical scenario against the release candidate and its packaged frontend.
• Exercise reader isolation, protected errors, concurrent runs, cancellation/global pause, overload, reconnect and process interruption before/after run admission.
• Combine the candidate results with the scoped local quality, resource and real-application evidence from #276, #275 and #285; record version, environment, failures and support boundaries.

Acceptance criteria

• A clean installation completes the API/dashboard flow and native instruction/reference Skill checks with the published instructions.
• The candidate's configured resource limits hold, protected data stays protected, and interruption does not restart old work or external test effects automatically.
• Run states and UI/API results agree; the actual packaged assets are tested rather than only development sources.
• GA remains blocked by unresolved critical findings or missing predefined operational evidence. Later recovery features and optional deployment integrations are not silently added as gates.

Boundaries

This ticket records release qualification, not automatic publishing, full workflow recovery or cross-framework superiority.

References

• Implementation dependencies: #427, #430, #431, #432, #428, #383, #429, #433, #434, #446, #440, #441, #442, #448, #443, #444, #445, #447, #437, #436, #438, #449, #450, #435, #439, #451, #276, #275, #285.
• pyproject.toml
• src/flock/frontend/package.json

Read pyproject.toml and src/flock/frontend/package.json, then run the maintained deterministic vertical scenario against the release candidate and its packaged frontend. Review the evidence from #276, #275 and #285 alongside the referenced implementation issues. Done means recording version, environment, failures and support boundaries, with GA blocked by unresolved critical findings or missing operational evidence.