Skip to content

chore(release): v0.1.13 - #76

Merged
rennehan merged 1 commit into
mainfrom
chore/release-v0.1.13
Jul 28, 2026
Merged

chore(release): v0.1.13#76
rennehan merged 1 commit into
mainfrom
chore/release-v0.1.13

Conversation

@rennehan

Copy link
Copy Markdown
Contributor

Version bump for v0.1.13. Cargo.toml + Cargo.lock only — same shape as the v0.1.12 bump.

What's in this release

Coherence findings read in your paths, not the server's ids.

Before:

unsatisfied_input  ae97175b-ddf3-42c5-8ee6-e3d22caacd54
  input port ae97175b-ddf3-42c5-8ee6-e3d22caacd54 has no incoming edge

After:

unsatisfied_input  cachetools.func.rr_cache.capacity
  input port cachetools.func.rr_cache.capacity has no incoming edge

Resolved in both the locator and the message, in both output modes, from this working copy — committed, staged, and config ports alike. The dotted spelling matches status/diff/show/walk and is what the authoring verbs accept, so a path can be pasted straight into the next command.

--json gains located[] beside the verbatim findings[], with finding_index, path, path_complete, and a resolved message.

When a path can't be resolved the raw id is shown rather than guessed at, and stderr says why — a stale view (detected by comparing branch versions), an unreadable index, or an endpoint that no longer exists.

Shipped in #75, which also fixed a panic found in review: validate aborted with a backtrace on any finding message containing a multi-byte character in the wrong position — after the round trip, so the verdict was computed and discarded, and the exit code became 101 instead of the documented 0/5 an agent gates on.

After merge

Tag v0.1.13 to trigger the release build (five targets, archives + .sha256 + signed provenance).

Coherence findings from `hydrate validate` now read in the dotted paths you
author with (`Api.Rater.key`) instead of the server's internal ids, in both the
locator and the message, and in both output modes. Paths are resolved from this
working copy — committed, staged, and config ports alike — so a finding is
something you can act on directly rather than a lookup you have to perform.

`--json` gains `located[]` alongside the verbatim `findings[]`, carrying
`finding_index`, `path`, `path_complete`, and a resolved `message`.

When a path cannot be resolved the raw id is shown rather than guessed at, and
a note on stderr says why — a stale view, an unreadable index, or an endpoint
that no longer exists.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@rennehan rennehan added the enhancement New feature or request label Jul 28, 2026
@rennehan rennehan self-assigned this Jul 28, 2026
@rennehan
rennehan merged commit 8b71a05 into main Jul 28, 2026
3 checks passed
@rennehan
rennehan deleted the chore/release-v0.1.13 branch July 28, 2026 01:16
rennehan added a commit that referenced this pull request Jul 29, 2026
Coherence findings from `hydrate validate` now read in the dotted paths you
author with (`Api.Rater.key`) instead of the server's internal ids, in both the
locator and the message, and in both output modes. Paths are resolved from this
working copy — committed, staged, and config ports alike — so a finding is
something you can act on directly rather than a lookup you have to perform.

`--json` gains `located[]` alongside the verbatim `findings[]`, carrying
`finding_index`, `path`, `path_complete`, and a resolved `message`.

When a path cannot be resolved the raw id is shown rather than guessed at, and
a note on stderr says why — a stale view, an unreadable index, or an endpoint
that no longer exists.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant