Ambiguous Artifact ID

The artifact hash prefix bf8d6 is ambiguous and might mean any of the following:

1. bf8d6346eb78956162a0b048478b9e4970f706d16adc337f4c54f1bf0a30f785 -

   • File internal/sync/xdelete.go — part of check-in [6273a0750d] at 2026-07-22 23:03:24 on branch trunk — fix: correct go.mod module path to go-libfossil (#76) (#117)

     * fix: correct go.mod module path to go-libfossil (#76)

     The module directive still declared github.com/danmestas/libfossil after the repository was renamed to go-libfossil. pkg.go.dev/godoc scraping matches the declared module path against its hosting path, so the stale path broke SDK doc generation.

     Rename the module path across all four in-repo modules (root, the two db/driver submodules, observer/otel, and docs/site) and every internal import, plus the release workflow, the doc-generation script, and the docs.

     No tag has been published under the go-libfossil path yet, so the cross-module requires cannot resolve from the proxy. Add replace directives pointing the in-repo requires at their local directories so GOWORK=off builds and the CI matrix resolve without a published version. These replaces are ignored by downstream consumers and can be dropped once new-path tags are cut.

     * Guard releases against replace directives; regenerate SDK docs

     The go-libfossil rename bridges the in-repo modules with `replace` directives. Go refuses a main module that carries them, so a tag cut while they are present breaks `go install .../cmd/libfossil@<tag>` and every `@version` fetch of the driver submodules. Add a Release workflow step that fails the job before anything is published if any tracked go.mod still contains a replace directive, so the bridge is a CI-enforced TODO rather than a silent landmine. The step comment records what unblocks a release: re-tag the submodules with the corrected module paths, bump the root requires, then drop the replace blocks.

     Regenerate the SDK reference docs. The previous pass only substituted URLs over the pre-existing generated files, leaving stale signatures (Repo.Timeline was still documented as taking LogOpts rather than TimelineOpts). Note that gomarkdoc must be run outside a git worktree — inside one it silently strips every source link.

     Also reword the README rename note, which read as though the import path had not changed, and re-sort the ncruces require block. (user: [email protected], size: 1901) [annotate] [blame] [check-ins using]

2. bf8d6d0ad2225b70682e5c247253a5fe2fe945f624fbe0a58179baf529e08fff -

   • File internal/blob/blob.go — part of check-in [c42a2b90c6] at 2026-10-13 05:59:46 on branch main — fix(manifest,hash): verify the R card at commit; reject an unrecognized hash-policy (#396)

     * fix(manifest,hash): verify the R card at commit; reject an unrecognized hash-policy

     A check-in reads its manifest back and requires the R card to equal the digest recomputed over the resolved tree, byte for byte (artifact-format-01 6.3.4, AF-6.3-5). A hash-policy setting outside the ordinals 0 through 4 is now an error instead of a fall back to the default (7.1, AF-7.1-2).

     Tracked in #387.

     * fix(manifest,repo): drive the commit R check from conformance; refuse a bad hash-policy on write (user: [email protected], size: 15486) [annotate] [blame] [check-ins using]