A key-value backend for task storage is wired in but every caller still uses per-task JSON files.
What
Task read, list, claim, update, delete and max-id helpers accept an optional store handle that replaces the per-task JSON files, but nothing in this build passes one.
Details
- With a store present, tasks are enumerated via listEntries under a
tasknamespace and read via readText, and deletion goes through the store using a keyed task path. - Locking switches to a separate
.v5-lock-anchorpath with an explicit lockfilePath. - Delete failures log the store's error code.
- Plumbing only: every caller observed in this build supplies no store, so the file-based path remains in use.
Evidence
namespace: "task", [Tasks] Failed to delete task
Strings lifted out of the shipped bundle, so the claim above can be checked against them.