viqueue v0.5.3 prerelease

viqueue v0.5.3 prerelease

Controlled private evaluation; not production-ready.

Repairs the native Pi 0.83 settlement/terminal race: retired ticket reads and settlement-triggered heartbeats cannot dereference cleared state, act on replacement claims, rotate a later session, or invalidate replacement credentials. Active failures and current credential revocation remain visible.

No kernel/backend change or deployment. No new retry engine, scheduler, durable supervisor, expiry/takeover, or automatic recovery.

Provenance and validation

• PR: #69
• Source commit: e62997aae618f1d442d2afef93be2f5f43a73de2
• Reviewed and merged tree: b5fbec844c865aecd00fb58925e0cc9b04288e08
• Fresh independent review passed after repairing the retired-401 finding.
• Local macOS full suite: 255 tests, 248 passed, 7 skips; two skips require Linux deployment tooling.
• Exact merged-commit Linux CI: 255 tests, 250 passed, 5 existing skips, zero failures: https://github.com/makscee/viqueue/actions/runs/34268782792/job/102204795163
• Two local archive builds matched; isolated local installation matched the canonical installed projection. These are the locally verified assets, not the CI archive.
• CI's two builds also matched each other, with different archive SHA-256 1c3b1cdd2e6f28fa60ff5090d06c9ff2dec1c9eb7251b738645dc602817f3444. Cross-platform archive identity is not established; the cause of the digest difference is not asserted.
• Archive SHA-256: 6d5e65716dd42b936462ec91b6375c1a3edcfb7629625d1cbe5b24b05b8fd5ad
• Installed projection SHA-256: 3bfdbdd4e2c2653db1165a16309459d3d56ca0289c950c9e0ad242e31474313c

Post-release fleet installation, live native replay, and full daily-work acceptance remain separate gates. This release is not a production-verification claim.

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.

viqueue v0.5.1

viqueue v0.5.1 prerelease

Prerelease for controlled private evaluation; not production-ready.

v0.5.1 fixes local install and rollback release-pointer rotation on BSD/macOS while preserving the existing behavior on GNU/Linux. The prior shell implementation used GNU mv -Tf; the BSD mv shipped by macOS rejects -T, and omitting that option can follow an existing destination symlink instead of replacing the pointer itself. This reproduced failure prevented the packaged local scripts from reliably switching current and previous on those systems.

Fix

The install and rollback scripts now use Node's renameSync to replace each prepared temporary symlink. The rename stays within the same pointer directory, atomically replaces the directory entry, and avoids platform-specific mv flags and destination-symlink-following behavior.

Compatibility and security

This is a compatible patch: CLI, HTTP, storage, archive, authentication, claim-fencing, and rollback contracts are unchanged. Atomic pointer replacement retains the fail-closed local release transition and avoids an intermediate missing-pointer state. Using the project's required Node.js runtime instead of divergent system mv implementations reduces cross-platform ambiguity; it does not broaden filesystem permissions or trust boundaries.

Validation

The focused packaged-script test installs two synthetic releases, verifies current and previous, rolls back, verifies both pointers again, and checks that temporary pointer paths are removed. The release candidate is also expected to pass the full unit/integration suite, build, tracked-source and history secret scan, full local end-to-end suite, and whitespace-error check.

This candidate does not publish, deploy, install into a user environment, activate a gateway, make a live request, or claim production or live-environment validation. Any tag, package publication, deployment, installation, or externally verified live operation remains a separate authorized action.

viqueue v0.5.0

viqueue v0.5.0 prerelease

Prerelease for controlled private evaluation; not production-ready.

v0.5.0 makes the supported worker lifecycle CLI-first. Workers can redeem one-time pairing codes, open and close sessions, claim work, record fenced progress, list and ask questions, release a blocked claim to Waiting, reclaim after a coordinator answer reopens the ticket, and complete directly with outcome and evidence provenance.

Compatibility and security

Direct completion is atomic and idempotent. The legacy submit/accept path remains compatible and optional rather than becoming a prerequisite for direct completion. Existing worker mutation receipt tables are migrated additively so exact fenced completion retries retain their receipts. Claim and session fencing, one-time pairing behavior, private-environment trust boundaries, and the v0.4.1 phone-gateway upstream restrictions remain in force.

Release archive

The deterministic local archive now stages every built dist/bin and dist/src output. This includes every package.json command target together with the server and phone-gateway dependencies. The archive name is derived from the package version and its SHA-256 checksum must verify before installation.

Validation expectations

A release candidate is expected to pass the unit/integration test suite, build, tracked-source and history secret scan, full local end-to-end suite, two-build deterministic archive hash comparison, checksum verification, and archive-content checks for every declared command plus src/server.js and src/phone-gateway.js.

This candidate does not publish, deploy, activate a gateway, make a live request, or claim production or live-environment validation. Any production release, deployment, ingress, credentials, or externally verified live operation remains a separate authorized action.

viqueue v0.4.1 — Exact Tailscale HTTPS upstream repair

viqueue v0.4.1 — Exact Tailscale HTTPS upstream repair

Prerelease for controlled evaluation and a later separately authorized production cutover; not production-ready.

This bounded security successor preserves the loopback HTTP default and adds one exact fail-closed Tailscale HTTPS upstream policy for the phone gateway. Remote HTTP remains denied. Remote HTTPS requires the tailscale policy, an exact root-form DNS origin, exclusively Tailscale DNS answers, fresh DNS-to-socket address pinning, and standard CA/hostname verification. Redirects, ambient proxies, unsafe authority/forwarding/proof headers, malformed origins, mixed/outside address sets, and unbounded DNS/connect/request behavior fail closed.

Publication only: no Homelab, mcow, Caddy, DNS, firewall, Tailscale Serve/Funnel, production gateway, pairing state/material, or device was changed.

Canonical source commit: 87ddd68d9eb28582a9f4f28325049b4bd8eb7540
Canonical tree: e9684519e1bedefbe400a3551701e0f3904eba69
Protected PR: #3

Asset

• viqueue-v0.4.1-rc.tar.gz: deterministic install archive; embedded SOURCE_COMMIT is the canonical commit above.
• viqueue-v0.4.1-rc.tar.gz.sha256: SHA-256 checksum manifest.

This is an unsigned deterministic archive with a SHA-256 checksum. No signature, attestation, or cryptographic provenance claim is made. Verify with sha256sum -c viqueue-v0.4.1-rc.tar.gz.sha256.

Any production cutover remains separately gated on Eva's approval of the phone hostname/exact ingress and the production auth DB path/service wiring. Do not enable Funnel or create pairing material as part of publication.

viqueue v0.4.0 — Human queue repair and single-phone gateway

viqueue v0.4.0 — Human queue repair and single-phone gateway

Prerelease for controlled evaluation and a later deployment-owner handoff; not production-ready.

This release publishes the reviewed human-first desktop/mobile queue repairs and the isolated single-phone proof gateway. The gateway uses one-use pairing/challenges, one active device, a non-exportable browser key, exact method/raw-target/body signatures, local revocation, fixed loopback upstream, and fail-closed header/path handling.

Publication only: no Tower production, mcow, Caddy, Homelab, DNS, firewall, Tailscale/Funnel, pairing database/token, or phone state was deployed or changed.

Canonical source commit: e40bf5a6f4c3537a0917e0817262e9990025f021
Canonical tree: 2feeb58c90d92e06f6860ba9e38301da570fcfcc
Protected PR: #2

Assets

• viqueue-v0.4.0-rc.tar.gz: deterministic install archive; its SOURCE_COMMIT is the canonical commit above.
• viqueue-v0.4.0-source.tar.gz: source archive generated with git archive from the exact canonical commit.
• Each archive has a separate SHA-256 checksum asset.

Release signing is not configured for this repository, so this release is checksum-only; no signature is claimed or fabricated. Verify the downloaded assets with sha256sum -c. GitHub release immutability was enabled before publication, so the tag and uploaded assets are locked after publication.

Read docs/phone-auth-staging-runbook.md and docs/phone-auth-threat-model.md before any later gateway deployment. Do not expose the upstream application directly or enable Funnel.

viqueue v0.3.0 — Daily Alpha

viqueue v0.3.0 — Daily Alpha core

Prerelease for private-alpha dogfood; not production-ready.

• One SQLite file with transactional in-place migration for actors, roles, typed assignment, and questions.
• Durable fenced authority claims with explicit release, submission, or takeover only.
• Stable actors with machine metadata and multi-valued roles; active eligibility for actor/role assignments.
• Multiple non-blocking text questions plus actor/role inboxes; first answer wins atomically.
• Submit creates one explicitly targeted approval; accept/request_changes alone drives review lifecycle.
• Append-only global/per-ticket event cursor and progress observations.
• HTTP-backed CLI, MCP stdio adapter, and responsive Ready/Working/Review/Done board.
• Explicit fail-closed one-shot import from v0.2 JSON.

A claim persists until an explicit release, submission, or takeover. Silence changes nothing.

Progress events are observations, not proof of liveness.

Agents pull work; viqueue never starts workers.

Workflow identity is not adversarial authentication. Bind the app to loopback and require a trusted private Tailscale boundary; never enable Funnel/public ingress.

viqueue v0.2.0

viqueue v0.2.0

Early prerelease for local evaluation. Not production-ready.

v0.2.0 is the first public-source release candidate for viqueue, a local pull-based ticket dispatcher for agents and humans.

Included

• Durable local JSON storage and HTTP application API
• viq command-line client with stable JSON output and exit codes
• MCP stdio adapter using the same HTTP application contract
• Responsive human Kanban board with explicit stale/uncertain handling
• Claim renewal, explicit authorized takeover, monotonically increasing fencing generations, and evidence submission
• Deterministic local install/uninstall archive

Important limitations

• Single server process and local JSON storage
• Local bearer takeover gate, not production authentication
• No worker launching, cloud deployment, or package-registry publication
• Trademark/name clearance is incomplete
• Pre-1.0 APIs may change with documentation

Asset verification

Download viqueue-v0.2.0-rc.tar.gz and its .sha256 file, then run:

sha256sum -c viqueue-v0.2.0-rc.tar.gz.sha256

See README.md in the archive for installation and operation instructions.