2026-05-22
File-aware coordination
- - Agents can now declare a file working set during a guarded run, so Availsync can coordinate at repo, project, and file level.
- - MCP guarded runs can start with file paths and will clearly stop when requested edit/delete paths are already claimed by another agent.
- - Working-set claims let an agent keep the wider repo run alive while only holding the specific files it is actively editing.
- - Work claims are now explicit immediate-start guardrails with stricter start-time validation and a database safety net for one active claim per resource.
- - Node SDK updated to 0.1.8 with stronger types, default withClaim idempotency, auto-extend hooks, and stricter unavailable-mode handling.
- - MCP package updated to 0.1.5 with guard_work_run as the primary coding-agent entrypoint and legacy work-slot aliases removed.
- - Work APIs now make /v1/work/run/start the recommended path, with the raw /v1/work/claim endpoint marked as legacy.
- - Agent API-key verification now uses a short-lived safe cache, and work-claim status/schema cleanup removed unused blocked claim rows.
- - Setup docs now use run/start, run/extend, and run/finish for new automation examples.

