fix(deps): update dependency @ankhorage/utility to v1

[ankhorage-renovate-sync]

This PR contains the following updates:

Package	Change	Age	Confidence
@ankhorage/utility	^0.5.1 → ^1.4.0

---

Release Notes

ankhorage/utility (@​ankhorage/utility)

v1.4.0

Compare Source

Minor Changes

• 5cf2161: Add strict boolean and finite number readers to the public Node environment utility entrypoint.

v1.3.0

Compare Source

Minor Changes

• eba3d9b: Add a safe reusable Node.js browser launcher that opens only HTTP(S) URLs without invoking a command shell.

v1.2.1

Compare Source

Patch Changes

• 431aebe: Add reusable regular-expression escaping and symlink-aware rooted filesystem helpers.

v1.2.0

Compare Source

Minor Changes

• 82bb78d: Add reusable deep equality and immutable deep merge operations to the object utility API.

v1.1.0

Compare Source

Minor Changes

• 875d001: Add ensureTrailingSlash to the public URL utilities.

v1.0.0

Compare Source

Major Changes

• 15acc87: Remove the project detection implementation and the @​ankhorage/utility/project public subpath. Import detectProject from @​ankhorage/project-detector and its public types from @​ankhorage/project-detector/types instead. The standalone detector also provides bounded filesystem inspection through its /node subpath. Utility does not depend on the detector or retain a compatibility re-export.

v0.8.0

Compare Source

Minor Changes

• 96d80ff: Expose isOptionalString from @ankhorage/utility/string so consumers can reuse optional-string
  validation. The guard accepts undefined and all primitive strings, including empty and
  whitespace-only strings, and rejects null and other types. It has no Contracts dependency.

v0.7.0

Compare Source

Minor Changes

• 2c50c45: Remove the public @ankhorage/utility/image entrypoint and its Contracts, Sharp, OpenCV,
  Tesseract and Pixelmatch dependencies. The entire image-analysis capability belongs in a
  separate repository. Preserve its implementation and tests as commented source at the
  maintainer's request; exclude that source from the published build.

  This is a breaking API removal in the pre-1.0 package. Screenshot-analysis consumers such
  as the zora-designer skill must move to the future owning package before using this API
  again. The remaining Utility subpaths are unchanged, and Utility no longer depends on
  Contracts.

v0.6.0

Compare Source

Minor Changes

• 6405b51: Add a generic async generator that executes lazy input sequences and yields each completed result.

v0.5.5

Compare Source

Patch Changes

• 9ba2692: Exclude evidenced decorative glyphs from Tesseract line observations while preserving uncertain text.

v0.5.4

Compare Source

Patch Changes

• 526b9a9: Skip redundant region OCR for containers whose descendants already own text evidence.

v0.5.3

Compare Source

Patch Changes

• ba0fdea: Keep screenshot-derived component props limited to observed visual evidence, identity scaffolding, and explicit runtime state defaults.

v0.5.2

Compare Source

Patch Changes

• 7b5484f: Preserve OCR-only screenshot copy as grouped visual evidence and recover text from meaningful textless regions with targeted preprocessed OCR.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[artiphishle]

Blocked by #260.

@ankhorage/utility/image was intentionally removed in ankhorage/utility#75. Devtools still owns the managed ZORA Designer screenshot consumer against Utility 0.5.x, so upgrading the direct dependency to Utility v1 would break that released capability.

PR #241 now keeps the direct Utility range on 0.5.x and adds the Renovate guard while the screenshot-analysis owner migration is tracked in #260. Do not work around this by restoring the removed Utility API or adding a compatibility shim.