{"version":"2.1.223","anchor":"skills-and-jobs-load-through-the-storage-sidecar","canonical_anchor":"skills-and-jobs-load-through-the-storage-sidecar","heading":"Skills and jobs load through the storage sidecar","tier":"internal","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/skills-and-jobs-load-through-the-storage-sidecar","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Skills and jobs load through the storage sidecar\n\nSkill listing and job tracking now go through the storage layer instead of touching files directly.\n\n**What**\n\nUser skill enumeration and job bookkeeping now go through the storage layer instead of reading and writing files directly.\n\n**Details**\n\n- Skill directory enumeration uses the scoped `listEntries`\/`read` API, with cursors, an 8-bit size cap check, and plugin-disabled filtering by the `plugin.json` name.\n- Job order, state and group writes go through sidecar keys.\n- The sidecar path is used when a sidecar handle is present; otherwise the old file writes are used.\n\n**Evidence**\n\n`[jobs] v5 sidecar write failed: `\n\n- Area: Skills\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}