viqueue v0.5.2 prerelease

viqueue v0.5.2 prerelease

Prerelease for controlled private evaluation; not production-ready.

v0.5.2 repairs the adapter-only Pi bridge for immutable fleet evaluation. Typed viq_take now binds one-ticket admission to a minimal durable custom entry in the actual native Pi session, so a genuinely new session can take work after completion while cancellation or resumption cannot make a used session eligible again.

Runtime and credential fixes

An exact take that receives a definitive non-mutating HTTP 404 or 409 claim rejection now records stopped presence, closes its just-created worker session, and restores a stopped/no-claim runtime before returning the rejection. Transport failures and unusable claim results remain blocked with explicit external-reconciliation status and are not retried or treated as safe.

The pure worker runtime no longer consults ambient host credential selectors. The extension boundary resolves the environment/default credential once, while an explicit credential file selected for a lane remains selected on later unqualified starts. Focused suites isolate XDG_CONFIG_HOME, VIQ_CREDENTIAL_FILE, and VIQ_DEVICE_TOKEN from host configuration, and runtime fixtures supply credentials explicitly.

Compatibility and deployment boundary

This is a compatible adapter patch. The product kernel, HTTP claim predicate, storage schema, retry behavior, polling strength, and external durable-state model are unchanged. No backend server deployment is needed for this adapter-only bridge.

Validation

The focused adapter and CLI suites cover native-session identity across completion/new/cancellation/resume, active-claim denial, real HTTP 404/409 rejection cleanup followed by a successful exact take, ambiguous-result reconciliation blocking, credential-lane persistence, and isolated credential configuration. The candidate is also expected to pass the full unit/integration suite and build.

This candidate does not tag, publish, upload, install, deploy, make a live request, or claim production or live-environment validation. Immutable fleet installation and every external release action remain separate authorized operations.