{"version":"2.1.280","anchor":"working-directory-registration-failures-now-carry-a-machine","canonical_anchor":"working-directory-registration-failures-now-carry-a-machine","heading":"Working-directory registration failures now carry a machine-readable error code","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/working-directory-registration-failures-now-carry-a-machine","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Working-directory registration failures now carry a machine-readable error code\n\nWorking-directory registration failures now include a machine-readable error code alongside the human-readable reason\n\n**What**\n\nWhen registering a working directory fails (for example, for multi-repo or worktree features), the check now returns a `code` field, either `is_cwd` or `already_registered`, in addition to the existing human-readable `reason` text. Similarly, the helper that verifies a path is actually a directory now returns a `code` field (such as `not_directory`) alongside its human-readable reason when the check fails.\n\n**Why**\n\nA machine-readable code lets calling code branch on the specific failure reason programmatically, instead of having to parse or match against the human-readable text.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}