beads/internal/httpclient/encode/encode.go
Julian Knutsen 6d21d337ad
feat(httpclient): OSS HTTP client store and roles + a served http conformance leg (contributed from bd-enterprise under MIT) (#7247)
* feat(httpclient): lift the HTTP client store and roles from bd-enterprise (MIT contribution)

Contributed by gascity from bd-enterprise (github.com/gascity/bd-enterprise,
internal/enterprise/httpstore @ 49d1df2f6) to OSS beads under the MIT
license, with the owner's explicit approval. Every lifted file carries a
provenance header naming its source path.

Lifted into internal/httpclient: the Store (DoltStorage over the wire), the
dial/register glue, the read roles (reader, querier, counters, edges,
relations, graph, tree, cycles, stats, config, memories, journal), the write
roles (lifecycle, claimer, releaser, deleter, dependency editor, metadata
CAS, commenter, batch closer/creator/applier, ready claimer, sweeper), and
their tests. The store transport seam (WireClient/WireDialer) and the
store-dependent tests deferred from the S2 lift are restored here.

Not lifted: the hosted gateway (httpgw/gwauth), box-login, storage profiles
and gasworks. dial.go only mentions the gateway in comments.

This commit is the mechanical lift and does NOT build yet. It references
enterprise-only APIs absent from OSS: issueops.ReadyLister,
journalops.Watcher, storage.ServerEnforcedPolicy, the
NonCommitGraphBackend/RemoteWorkspaceBackend markers, DoltStorage
differences, and BatchCloseRequest.claim_next. The following commits
reconcile it with OSS (S3/S4/S5).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* fix(httpclient): reconcile the bd-enterprise lift's compile-time API surface against OSS

The mechanical lift (02a9dad17) carried several bd-enterprise-only shapes
that do not exist in OSS beads:

- ReadyLister, journalops.Watcher/StreamWire, and ServerEnforcedPolicy have
  no OSS wire counterpart; drop the role, its served/journal-watch tests,
  and the policy enforcement path entirely rather than leave dead code that
  cannot compile against OSS's apigen types.
- claim_hook_gate_test.go exercised a hook surface OSS does not publish.
- recordingWire/fakeWire no longer embed a StreamWire double now that no
  read role can reach a watch stream; testTarget's two conflicting
  package-scope declarations (store_test.go and helpers_test.go) are split
  apart as pinnedProjectTarget vs. the generic helper.
- unsupported_gen.go is regenerated from scratch against OSS's actual
  storage.DoltStorage via a new, from-scratch reflection-based generator
  (internal/storage/unsupportedgen) rather than hand-copied from
  bd-enterprise's generated output; completeness_test.go's
  legitimatelyUnsupported map grows the handful of OSS-only or
  previously-missed methods (AddRemoteWithRef, RenameLabel, etc.) this
  regeneration surfaces.
- write_ledger_test.go and the divergence ledger doc gain the
  force_notes_overwrite and claim pending rows OSS's apigen.UpdateRequest
  and SweepRequest actually carry, and drop the Remaining/LiveDependent
  assertions SweepResult/SweepSkips have no wire member to ever populate.

go build ./... and go vet ./... are clean after this change. No behavior
beyond the removed surfaces changes here; read-role and write-role
reconciliation land in follow-up commits.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(httpclient): stop sending listIssues a reverse/sort vocabulary OSS does not publish

The bd-enterprise lift's sortedPage pushdown assumed GET /v0/beads/issues
(listIssues) shared the same sort vocabulary and a reverse parameter with
GET /v0/beads/issues:query (handleQueryIssues) -- a different operation.
OSS's openapi.v0.yaml publishes listIssues a CLOSED two-value `sort` enum
(created, priority; deliberately smaller than the nine values :query
takes) and no `reverse` parameter at all. Sending either would earn an
unknown-parameter or invalid_value refusal from the real server, not a
silently-wrong answer -- which is why this only surfaces against a served
backend, not a Go-side unit test of the request builder.

Add listSortPushdownEligible to gate the pushdown fast path to the two
keyset orders listIssues can actually page, unconditionally refusing any
reversed request (listIssues has no parameter that names a reversed
direction, so a reversed request of any order walks and sorts
client-side). Drop the unconditional `reverse` send from sortedPage.

served_list_test.go's three affected cases encoded the wrong,
enterprise-only wire shape (expecting reverse=false on the fallback path,
expecting a reversed order to push down with sort+reverse, and expecting a
Go-side/SQL-side mix in listIssues' sort enum); corrected to match OSS's
actual, provable wire contract rather than left red. list_sort_test.go's
publishedParamEnum helper now reads the OpenAPI document via the
go:embed'd spec.OpenAPIV0() accessor instead of a relative os.ReadFile, so
it no longer depends on the test's working directory (this also fixes the
same test failing under Bazel's sandbox, which does not expose arbitrary
relative-path files).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(httpclient): reconcile write-role tests against OSS's BatchClose/Update shapes

OSS's apigen.BatchCloseRequest and BatchCloseResponse publish no
claim_next/claimed_next member at all (ledger row
W-CloseBatchRequest.ClaimNext) -- bd-enterprise's claim-folded-into-close
shape has no OSS wire counterpart. Replace the three tests that exercised
decoding a served claim (TestBatchCloseRefusesAServedClaimCarryingNoIssue,
TestBatchCloseRefusesAServedClaimTheRequestNeverEarned,
TestBatchCloseKeepsTheClaimItEarned) with
TestBatchCloseRefusesClaimNextUnconditionally, which pins the actual OSS
behavior: a CloseBatchRequest naming ClaimNext refuses before any dial, on
both the unserved and served legs, regardless of what a server would
otherwise answer. Drop the now-dead "claim-next" case and helper claim
variable from TestBatchCloseServesTheSingleItemShapeAndRefusesTheRest.

Also:
- Add the ForceNotesOverwrite case to
  TestUpdateRefusesEveryMemberTheWireExcludes's hand-maintained member
  map -- a ledgered-pending UpdateRequest member (see
  W-UpdateRequest.ForceNotesOverwrite) the lift's test left uncovered.
- Remove write_roles_test.go's duplicate `ptr[T]` generic helper, which
  redeclared the one already in helpers_test.go and never compiled.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* test(conformance): pin post-write RowVersion propagation across Update/Close/Reopen

types.Issue.RowVersion is json:"-", so an implementation that forgot to
populate it on the way back from storage would still compile and still
pass every existing content assertion in lifecycle_close_reopen_contract.go
-- none of them read RowVersion. Add
RunLifecycleResultsCarryThePostWriteRowVersion, which chains each write's
result token into the next write's ExpectedVersion (Update -> Close ->
Reopen) with no intervening read, so a dropped or stale token fails closed
on the next write's optimistic-concurrency guard rather than passing
silently.

Register it in role_bundle_cases.go's roleContractCases dispatch table at
its declaration-order position -- TestRoleContractCasesCoverEveryContractCase
was failing because the function existed with no dispatcher entry.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* chore(bazel): sync BUILD files via gazelle for the S3 reconciliation

bazel run //:gazelle after the compile/read-role/write-role reconciliation
commits:

- internal/httpclient/BUILD.bazel: regenerate srcs/deps for the files
  added, removed and newly imported above (drops the deleted
  policy/journal-watch/readylister files, adds the spec dep for
  list_sort_test.go's embedded OpenAPI read). Manually add
  `data = glob(["*.go"])` to the go_test rule, matching the idiom already
  used by //internal/httpclient/encode: completeness_test.go and
  divergence_citation_gate_test.go read their own package's .go sources at
  runtime (a regex scan of unsupported_gen.go and an AST walk of the
  package directory), and Bazel's go_test sandbox only copies in files a
  rule declares as `data` -- `srcs` are compiled away, not left readable.
  A `# keep` directive protects the attribute across future gazelle runs
  (confirmed gazelle does not manage `data` on this rule).
- internal/storage/BUILD.bazel,
  internal/storage/unsupportedgen/BUILD.bazel: pick up the new
  from-scratch unsupportedgen generator package.

bazel test //internal/httpclient/... //backend/conformance/... now passes
all 4 targets (previously 4 of the package's tests failed only under
Bazel's sandbox: TestInterfaceCompleteness,
TestTheCountGroupVocabularyMatchesTheSharedOne,
TestFlaglessListSortIsTheSameOrderNamed,
TestDivergenceParkCitationsResolveToLiveLedgerRows).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(conformance): close two pre-existing leg-wiring gaps found while registering http

- RunLifecycleResultsCarryThePostWriteRowVersion (added in 536561124) was
  never wired into dolt/embeddeddolt/uow's own lifecycle_close_reopen test
  tables, only into the http leg's. TestEveryLegWiresEveryRoleContract
  catches this once a fourth leg forces the test to actually run again;
  wire the missing t.Run into all three.
- The three StatsReporter "suppressed rows" cases (GateIssues/TemplateIssues
  breakdown) were never added to served_graph_aux_test.go even though the
  wire already carries both fields end-to-end (types.Statistics is shared
  verbatim by apigen.StatsResponse and the client's decode). Wire them; all
  three pass over HTTP with no server or client change needed.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* feat(conformance): register the http leg in the role-contract lock

Registers "http" (wiringRoot internal/httpclient) in contractLegRegistry.
The served-surface harness (served_harness_test.go + 16 served_*_test.go
files) already wired 495 of 576 role-contract entrypoints from the
bd-enterprise lift; this change:

- Waives the 3 RunCycleDetectorIncludeTracks* cases: issueops.
  DetectCyclesRequest.IncludeTracks has no plumbing on either side of the
  wire today (cycles.go always calls DetectCycles with a zero-value
  request; the client's DetectCycles ignores its request parameter). No
  slice through S13 adds one, so the waiver says a new slice is needed
  rather than pointing at an existing one.
- Sets adoptionCeiling: 75 for the remaining, not-yet-wired write-role and
  internal-plumbing entrypoints (lifecycle writes, DependencyEditor,
  MetadataCAS, Lease, Sweeper, VersionReconciler, Bootstrapper/
  InitVerifier, cross-record invariants) that S4 and later write slices
  pick up and ratchet down.
- Adds //internal/httpclient:go_srcs to storage_test's data: the leg's
  wiring root lives outside internal/storage, and the Bazel sandbox has no
  other reason to materialize those sources for a test that reads them at
  runtime.

TestEveryLegWiresEveryRoleContract, TestEveryRoleMethodHasAContractCase,
and RunUnsupportedContract (already wired pre-lift in
internal/httpclient/completeness_test.go) all pass for the http leg.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(httpclient): close review's HIGH 2-5 gaps and reconcile their test doubles

HIGH 2 (BatchCloser), HIGH 3 (created_by stamping, absent-parent 404/400,
force_notes_overwrite carriage) and HIGH 4 (CapabilityError now unwraps to a
typed *storage.ErrUnsupported with Capability) were implemented in prior
commits on this branch; this change finishes HIGH 5 and the verification the
review asked for:

- role_reader.go's Reader.Get and bridge.go's raw GetIssue both now stitch
  Revision back onto Issue.RowVersion via parseRevision, so a guarded write
  built off either read carries the row's real token instead of a decoded
  zero. Both are pinned by round-trip served tests that guard a write with
  the read's token and require a stale-token replay to refuse.
- Fixed create_test.go's stale assertion that created_by must stay empty
  (contradicted the HIGH 3 stamping fix it predated).
- Fixed recordingWire's canned IssueDetails{} response (roles_test.go): it
  omitted Revision, which is a required field on every getIssue response
  per the OpenAPI spec, and the HIGH 5 stitch now reads it unconditionally.
- Synced internal/httpclient/wire/BUILD.bazel via gazelle: handshake_test.go's
  new internal/storage import had no corresponding dep.
- gofmt'd write_roles_test.go's stubWire struct tags.

Verified: served HTTP conformance tier (BEADS_TEST_EMBEDDED_DOLT=1
BEADS_HTTP_TEST_REQUIRED=1 go test ./internal/httpclient/, -timeout=40m)
600 PASS / 0 FAIL / 72 SKIP (all ledgered known-divergence waivers). One
TLS-handshake-timing test failed in that run and passed 3/3 in isolation
(unrelated file, pre-existing flake under machine load, not reproducible).
Also green: default go test (minus the pre-existing, unrelated
TestEngdocsAndRootMarkdownLinks doc-link drift and the environmental
internal/storage/uow dolt-server-spawn hang), bazel build/test for the
touched packages, make api-check, and gofmt/vet.

Live-mutated and reverted 3 guards to confirm their tests are load-bearing:
role_reader.go's RowVersion stitch, bridge.go's RowVersion stitch, and
lifecycle.go's force_notes_overwrite wiring.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* feat(ci): add served HTTP conformance as Tier 3 of the conformance gate

The served tier (internal/httpclient's served_*_test.go corpus) never ran
in CI, so HIGH 2-5's regressions (and any future ones) would merge
undetected. Add it as Tier 3 of scripts/conformance.sh, the existing
required entrypoint conformance.yml already runs on every PR/push/merge_group
(not a new workflow, not wired through ci-gate.sh's aggregation -- this
repo's convention for this gate is a single standalone job):

  CGO_ENABLED=1 BEADS_TEST_EMBEDDED_DOLT=1 BEADS_HTTP_TEST_REQUIRED=1 \
    go test -timeout=40m ./internal/httpclient/

Left unsharded: Tier 1 and Tier 2 are themselves single unsharded
invocations, and Tier 3 is one Go package, not a multi-package corpus the
repo's existing package-sharding scripts apply to. No Bazel-lane addition:
bazel-coverage's embedded/dolt_server outputs only ever substitute for
main.yml/pr-risk.yml jobs, never for conformance.yml's own job, so there is
no existing Bazel-lane relationship for this gate to extend.

Bumped the job's timeout-minutes 45 -> 100 (30m + 10m + 40m budgeted
sub-timeouts plus checkout/setup-go overhead) and updated the three policy
tests that pin this script/workflow byte-for-byte
(TestConformanceScriptUsesExplicitTimeoutBudgets,
TestConformanceScriptPropagatesGoTestFailures,
TestConformanceWorkflowHasOuterTimeoutBudget), re-included
internal/httpclient/** in both path filters (push and pull_request, kept
identical) since served_*_test.go files are the suite itself and would
otherwise be excluded by the shared !**_test.go negation, and documented the
new filter entry in ci_f7c_advisory_test.go's own-entries map.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(httpclient): root-cause and fix the Happy-Eyeballs TLS flake in store_dependent_test.go

TestTransportForSucceedsWithEnvCAFile (and 3 Handshake-based siblings that
assert on a successful dial through a configured CA: SidecarCAFile,
CAFileEnvAgreeingWithSidecarSucceeds, DialWithNilTransportHTTPClientGetsCAInjectedOnACopy)
flaked once with "tls: first record does not look like a TLS handshake".

Root cause: our code, same class S2 already fixed for TransportFor's direct
callers (forceIPv4Loopback in ca_test.go/ca_wrong_ca_test.go). Every server
these tests dial is addressed by hostname "localhost" (ca.startServer
rewrites it there deliberately, so SNI is actually sent), which Go's
default dialer races a tcp6 dial to ::1:<port> against the real tcp4 dial to
127.0.0.1:<port> for (RFC 6555). An unrelated local process already bound to
a colliding ephemeral port on ::1 can occasionally win that race before the
real dial completes, and the client speaks TLS to that unrelated process
instead -- the misleading handshake error, not a real hang or a product bug.

These four tests go through Handshake with DialOptions{} (HTTPClient left
nil deliberately, since that is itself the nil-HTTPClient branch of DialWith
under test), so they never get a *http.Transport back to mutate the way
forceIPv4Loopback's existing callers do. Fixed via warmIPv4OnlyCATransport:
pre-build the target's CA-scoped transport through the same public
TransportFor the product code itself calls (so it lands in the exact
(path, content)-keyed cache transportForFile's cache hit returns), force
tcp4-only on that cached pointer, and let Handshake's own DialWith run
unchanged -- same branch under test, same cached transport, no sleeps, no
retries. Verified with -race -count=50 on all four: 200/200 pass.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(httpclient): refuse DetectCycles(IncludeTracks=true) instead of silently ignoring it

roles_graph.go's httpCycleDetector.DetectCycles took its request as `_`,
forwarding nothing: a caller asking for the widened (tracks-following) walk
silently got the narrower default walk back with no error. listDependencyCycles
has no include_tracks wire parameter at all, so there is no way to honor the
field — only to refuse it loudly or drop it silently. Switch to the typed,
ledger-cited refusal (encode.RefusedError via refuse(), citing new row
"L-cycles-tracks") that CountEdges' own wire bound already uses, add the
ledger row and its Op, regenerate the auto-generated ledger doc, and pin the
behavior with a unit test (no served-tier case needed: the refusal is
pre-dial by design, same reasoning as the existing edge-count bound pin).

Also fix leg_contract_wiring_test.go's cycleTracksWireGapWaiverReason, which
had gone stale: it described the http leg as silently forwarding nothing for
this field, which was true before this change and is not after. The waiver
itself (the three RunCycleDetectorIncludeTracks* contract cases stay unwired
for the http leg) is unaffected — they were never wired, and still are not —
only the reason text needed updating to describe a typed refusal instead of a
silent ignore.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(storage): name the http leg's permanent contract gaps instead of budgeting them

The http leg's role-contract adoption ceiling (internal/storage/contract_leg_registry_test.go)
sat at a flat 75, with a prose "adopting" note that bundled every skip into
one vague bucket — including MetadataCAS, which is in fact fully wired (0
missing cases), a false claim left over from an earlier wiring pass.

Twenty-six of the 75 skips are not S4-and-later work at all: they are
PERMANENT gaps that no future slice closes, because the contract itself has
no publicops role for an HTTP client to route through:

  - Importer (4 cases): uow is Importer's one accessor, same precedent the
    dolt and embeddeddolt legs already carry (importerOneAccessorWaiverReason).
  - RetentionFixture/EpochFixture (15 cases) and CrossRecordInvariantFixture
    (7 cases): both fixtures carry raw storage hooks (Resolve, Erase, Mint,
    CurrentEpoch, GuardedWrite, EnforceCrossRecordInvariant, ...) with no
    publicops field at all. dolt, embeddeddolt and uow wire these because
    they ARE the storage engine this address/epoch/retention and
    cross-record transaction bookkeeping belongs to; the http leg is a
    remote client with none of its own to report. There is no wire surface
    for this to ever route through short of a new role being designed from
    scratch — a new slice, not a missing test line.

These 26 are now named, reasoned waivers in unwiredContractEntrypoints
(two new reason constants: retentionEpochNoRoleWaiverReason and
crossRecordInvariantNoRoleWaiverReason), and the ceiling drops from 75 to 49
to match. The "adopting" note is rewritten to correctly name every remaining
category under budget (lifecycle writes, DependencyEditor, DualWrite,
Sweeper, VersionReconciler, Bootstrapper/InitVerifier, ExpectedRevision/
Refusal) and to drop the false MetadataCAS claim.

Also documents, at conformanceEntrypointsWiredBy, why a leg wiring a
conformance.RunX reference with every hook left nil would read as "adopted"
by this lock's static source grep while actually running as a skip —
matching the loophole internal/httpclient's divergence_citation_gate_test.go
already closes for skipKnownDivergence call sites. No leg currently does
this (verified by inspection); the note sets the review expectation for
future wiring rather than papering over the gap with no record of the policy.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(licensing): scrub internal program/org naming and a leaked private ID from OSS-visible text

MEDIUM 8 of the S3 ship review: remove licensing-hygiene leaks found by a
read-only repo-wide survey, while leaving every legitimate "Contributed by
gascity from bd-enterprise ... to OSS beads under the MIT license." provenance
header and every genuine public gascity/gastownhall self-reference (the real
OSS org, beads.gascity.com docs domain, RBE infra) untouched:

- Delete release-gates/ga-7psli2-3-1-baseline-cmd-bd-fix-gate.md: the only
  file in release-gates/ keyed by a private `ga-` tracker ID instead of the
  directory's established public `be-` convention (30 other files), and the
  only one leaking internal filesystem paths (/home/jaword/...,
  gc-management/.gc/artifacts) and internal routing terms (mayor/mpr,
  "deployer session"). Not referenced from anywhere else in the tree.
- .golangci.yml: drop two private `ga-2ltro.12`/`ga-26w10` history citations
  used as nolint-comment justifications; reworded to the same explanatory
  content without naming a private tracker ID.
- Reword 19 "gc native-program" occurrences (14 files, comments and one
  design doc) to drop the internal program name while keeping the "S3
  reconciliation (2026-10)" dating they were attached to.
- cmd/bd/if_revision.go, if_revision_test.go, update.go,
  update_proxied_server.go: drop literal citations of gascity's private
  bdstore_conditional.go classifier (including a test function name,
  TestIfRevisionEnvelopeGascityContract -> ...DownstreamContract) while
  keeping the substantive explanation of why this envelope's shape is
  load-bearing for a downstream consumer.
- internal/httpclient/lifecycle.go: drop a citation of gascity's private
  internal/beads/bdstore.go.
- internal/httpclient/dial.go: drop the internal/enterprise/httpgw package
  path, keeping "a gateway dialer outside this repo".
- internal/httpclient/register.go: reword away from naming "the enterprise
  distribution" while keeping the build-tag-opt-in behavior it documents.

Verified: go build ./..., go vet ./internal/httpclient/... ./cmd/bd/...,
go test ./internal/httpclient/... and ./cmd/bd/... -run TestIfRevision all
pass; TestDivergenceLedgerDocMatchesLedger still passes (ledger.go and its
doc were edited in lockstep). gofmt -l reports no diffs on any touched file.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(httpclient/wire): correct the CapExternalDependencies doc's implied false claim

MEDIUM 9 of the S3 ship review. The old comment on CapExternalDependencies
said this client "has no external-dependency policy layer to gate" and that
"OSS publishes no storage.ExternalDependencyQueryStore-backed client policy
... to compose" immediately after naming bd-enterprise's removed policy.go --
easily misread as "OSS has no external-dependency decorator at all." It does:
internal/storage/externaldeps's decorator is unconditional (no build tag) and
is wired into every local storage chain by cmd/bd/storage_chain.go.

Reworded to say precisely what is and is not true: the decorator exists and
runs for local backends; what this http client lacks is a client-side
composition of that decorator around a remote store, which is moot anyway
because a server advertising this capability already applies the policy
itself before answering. (Rolled in the same "gc native-program" wording
removal from the MEDIUM 8 commit, since both edits touch this comment block.)

A second claim from the same review item -- that OSS is said somewhere not to
serve events:watch -- could not be located despite an exhaustive repo-wide
search (this file, engdocs/, docs/reference/events-journal.md,
SERVE_RUNBOOK.md, the divergence ledger, CHANGELOG.md, and a dedicated
read-only research pass). internal/httpapi/events_watch.go,
routes.go's events.watch route entry, and internal/httpclient/wire/stream.go
all confirm OSS serves it unconditionally (gated only per-workspace by the
events journal setting, not by build/distribution). No corresponding false
claim exists in this worktree to fix; noting this rather than editing
something that already reads correctly.

Verified: go build ./internal/httpclient/..., go vet, go test
./internal/httpclient/wire/... pass. gofmt -l clean.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* test(unsupportedgen): add a freshness check for the generated shell

LOW item from the S3 ship review: internal/storage/unsupportedgen had no
tests of its own, so the generator could drift from the checked-in
internal/httpclient/unsupported_gen.go (a storage.DoltStorage interface
change, or a hand-written method added/removed on Store) with nothing to
catch it short of a human noticing the diff. TestInterfaceCompleteness
(completeness_test.go) already pins which methods belong in the shell by
name, but not whether the checked-in bytes match what the generator would
produce today.

TestGeneratedShellIsFresh runs the same scan-then-generate pipeline main()
runs for the registered DoltStorage/httpclient/Store consumer and diffs the
result against the checked-in file -- mirrors the existing
TestDivergenceLedgerDocMatchesLedger pattern in
internal/httpclient/encode/ledger_render_test.go. Added
TestScanHandWrittenMethodsExcludesOwnOutput alongside it to pin the
correctness property the freshness check depends on (scanning must not see
the generator's own prior output as hand-written).

BUILD.bazel: added the go_test rule by hand (gazelle cannot infer the
cross-package `data` dependency a relative-path os.ReadFile needs under the
Bazel sandbox) with data = ["//internal/httpclient:go_srcs"], following the
existing cross-package data pattern in
internal/httpclient/encode/BUILD.bazel. Placed go_test before the
go_srcs.py-managed filegroup block, which `make bazel-sync-check` requires.
Verified: `bazel run //:gazelle` leaves the rule untouched, `bazel test
//internal/storage/unsupportedgen:unsupportedgen_test` passes, `make
bazel-sync-check` is clean, go build/vet/test ./... all pass.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(httpclient/encode): scrub a private tracker-ID cluster from the shipped divergence-ledger doc

Follow-up to the MEDIUM 8 licensing scrub: internal/httpclient/encode's
ledger_render.go header and ledger.go's comments/pinnedElsewhere constant/two
Why strings cited "ga-b8ddd.12/.19/.23/.30" by name. These feed directly into
engdocs/design/http-divergence-ledger.md -- a shipped, generated OSS design
doc, the most visible surface this private ID cluster reached (Fork A's
MEDIUM 8 survey found ~40 occurrences of "ga-b8ddd" across the httpclient
package; this commit addresses the subset inside package encode that is
checked-in prose/doc text, not test-fixture or assertion values). Reworded to
keep the same substantive explanation (what closed, what's still deferred,
which dual run resolved L17) without naming the private ID.

The remaining ~30 occurrences of "ga-b8ddd" outside package encode
(offrole.go, metadata.go, store.go, roles_test.go, wire/*_test.go,
served_*_test.go) are left for a follow-up pass: scrubbing them individually
needs the same per-file verification this commit did, and is a larger,
separate blast radius than was practical in this pass.

Regenerated engdocs/design/http-divergence-ledger.md via
`go test ./internal/httpclient/encode -run TestDivergenceLedgerDocMatchesLedger
-update-ledger-doc`; diff confirmed only the ga-b8ddd text changed. go build
./..., go vet ./internal/httpclient/..., and go test ./internal/httpclient/...
all pass.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* docs(httpclient): drop a private host reference from a test comment

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* revert(licensing): keep the scrub to the contributed client code

The previous scrub also edited upstream files this PR doesn't otherwise
touch (.golangci.yml, cmd/bd --if-revision files from #7203) and deleted an
upstream release-gate record. Restore them; the provenance scrub applies only
to the code contributed from bd-enterprise.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* feat(httpclient): wire S8 count-scope fields on the client

Encode ParentID/NoParent/ExcludeTypes/ExcludeStatus onto countIssues
(table.go + encode.go), add issues.count.scope to the client capability
table (wire/handshake.go, wire/vocabulary_test.go), and refuse locally
before dialing when the server hasn't advertised the token and any scope
field is set (counter.go's refuseUnservedScope), returning a typed
*storage.ErrUnsupported{Capability:"issues.count.scope"} rather than
dropping fields or taking a guaranteed-400 round trip.

Adds encoding-parity coverage (counts_test.go), a masked-token skew test
proving the pre-dial refusal and zero dials (counts_test.go), roundtrip
and skew-table fixes for the newly-encoded fields (encode/roundtrip_test.go,
encode/skew.go), and wires S8's nine shared Counter conformance cases into
the served http leg (served_counter_test.go), including AddDependency so
the wisp/compose cases run instead of skipping. List stays nil on this
fixture since listTable() has pre-existing, unrelated permanent refusals
for ListRequest.NoParent/ExcludeTypes, so the three *MatchesListCardinality
cases skip here by design.

internal/storage's TestEveryLegWiresEveryRoleContract/http ceiling check
remains red (53 skipped vs ceiling 49) after this change, but strictly
improved: before this change the inherited baseline was 62 skipped (13
over ceiling), all nine of S8's new entrypoints unwired. This change wires
all nine, closing exactly that gap; the remaining 4-over are named
RunBootstrapper*/RunDependencyEditor* cases unrelated to count-scope,
pre-existing debt from other already-merged slices whose ceiling was
never bumped for them. Left the ceiling constant alone rather than
raising it to paper over debt this change doesn't own.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(storage): close the http leg's role-contract ceiling regression

TestEveryLegWiresEveryRoleContract/http went red after the rebase (62
skipped, 13 past its ceiling of 49) before any work in this session; the
prior commit closed 9 of those (S8's Counter cases). The remaining 4-over
were RunBootstrapper* (9 entries) and RunDependencyEditor* (2 entries),
both newly-merged contracts this leg had never classified.

RunBootstrapper*: internal/httpclient/accessors.go already names
Bootstrapper PERMANENTLY UNSERVABLE over http (bd init resolves its
substrate identity entirely client-side, before any server exists to
dial) — add a new named waiver, bootstrapperPermanentlyUnservableWaiverReason,
covering all nine entrypoints. VersionReconciler and InitVerifier are
named permanently unservable by the same accessors.go comment but are
left under the ceiling for their own reviewed change, out of scope here.

RunDependencyEditor*: the OSS server already serves add/remove and the
http leg already wires nearly all of DependencyEditor's contract. The two
missing cases (SameTypeReAddWithChangedMetadataMintsOneVersion,
SameTypeReAddWithIdenticalMetadataIsANoOp) only needed
SetVersionedHistoryEnabled wired onto the fixture, the same way
SetJournalEnabled already is — wired it for real; both pass served.

With Bootstrapper waived and DependencyEditor fully wired, the leg's
unwaived-missing count drops from 53 to 42, so adoptionCeiling moves
from 49 to 42 to keep the ratchet exact, with the adopting prose updated
to match.

TestEveryLegWiresEveryRoleContract is green. Served tier (real, CGO +
embedded dolt): 611 PASS, 0 FAIL, 72 SKIP (up from 609). bazel build/test
and make api-check pass for the touched targets.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* build(bazel): auto-sync BUILD files

Applied from the bazel-sync-patch artifact of https://github.com/gastownhall/beads/actions/runs/37307836753
(`make bazel-sync`: gazelle, tools/bazel/go_srcs.py, bazel mod tidy).
Only BUILD.bazel, MODULE.bazel and MODULE.bazel.lock are ever pushed; see
scripts/bazel-autofix-push.sh.

* fix(conformance): pass -tags gms_pure_go to Tier 3's served httpclient run

scripts/conformance.sh:61 ran a bare `go test -timeout=40m ./internal/httpclient/`
for Tier 3 (served HTTP client/role conformance), which `make ci-pr-policy`'s
build-tag policy check refuses ("bare go test without -tags=gms_pure_go").
Pass the same -tags Tier 1 already does, and update
TestConformanceScriptUsesExplicitTimeoutBudgets' pinned argv to match.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(bazel): give //internal/httpclient:httpclient_test room to run

The package takes ~350s under --config=ci (BEADS_TEST_SKIP=dolt, no
BEADS_TEST_EMBEDDED_DOLT) — mostly wall-clock wait on the CA tests'
dialer/keep-alive timeouts, not CPU — but the go_test had no size/timeout
override, so it inherited the medium default's 300s and timed out
intermittently under Bazel (and took "Go test equivalence" down with it).
Set size = "large", timeout = "long", matching
//internal/storage/embeddeddolt's go_test.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(httpclient): fix data race in caContextHandler test helper

TestTransportForRaisesMaxIdleConnsPerHostForBursts drives caContextHandler
with 8 concurrent requests; handler() wrote requestSeen/host/sni from every
server goroutine with no synchronization, and the other nine callers (all
single-request) never exercised the race. go test -race reproduced it as
3x DATA RACE across repeated runs.

Guard the fields with a mutex and expose them only through accessor methods
(sawRequest/seenHost/seenSNI), updating every call site in
store_dependent_test.go accordingly.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(unsupportedgen): canonicalize reflect-visible stdlib aliases

TestGeneratedShellIsFresh fails on Go >= 1.27: encoding/json.RawMessage
became an alias of encoding/json/jsontext.Value, and reflect only ever sees
an alias's underlying type, so formatType rendered
storage.DoltStorage.MergeMetadata's signature with the new, non-portable
name even though the signature itself did not change. A contributor on
1.27 following the freshness test's own advice ("go generate
./internal/httpclient") would commit a shell that does not compile on the
1.26.7 SDK this repo pins.

Add reflectAliasCanonical, a table mapping a reflect-visible alias target
back to the name a human wrote in source, consulted by namedType. Add an
entry here for any future stdlib alias this generator's output needs to
stay stable across.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(httpclient): claimOnlyUpdate propagates the claim's RowVersion

bridge.go's GetIssue already stitches details.Revision onto
hydrated.RowVersion when claimOnlyUpdate rehydrates labels/CreatedBy onto
the claim response, but the claim response itself (issueops.Claimer's
bare-row contract) carries no revision at all, and the copy-back only
touched Labels and CreatedBy. So Lifecycle.Update({Actor, IssueID, Claim:
true}) — `bd update X --claim` — handed back Issue.RowVersion == 0 over
http where the local leg returns the real token, and feeding that into the
next write's ExpectedVersion got a spurious mismatch instead of none.

Copy RowVersion back too. Extend
RunLifecycleResultsCarryThePostWriteRowVersion (shared lifecycle/close/reopen
conformance contract) with a claim-shaped first link in the chain: claim,
then guard the next write with the claim result's own token, proving the
claim-only path populates the real version rather than a nonzero constant.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(httpclient): stitch RowVersion on SearchIssues' exact-id fast path

resolve.go's getIssuesByExactID decodes the same IssueDetails shape
bridge.go's GetIssue does, but never parsed details.Revision the way
GetIssue's own stitch does, so SearchIssues(ctx, "<exact id>") answered
RowVersion 0 — a one-line gap: Issue.RowVersion is json:"-", so the decode
left it at zero, and only the explicit parseRevision stitch recovers it from
the response's own Revision string member.

Add TestSearchIssuesExactIDPopulatesRowVersionForAGuardedWrite, pinning the
same guarded-write round trip TestBridgeGetIssuePopulatesRowVersionForAGuardedWrite
already pins for the plain GetIssue path.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(httpclient): route every write role's refusals through inexpressible

Review finding 7: write-side refusals were not uniformly *ErrUnsupported.
Read roles already wrap encoder refusals through Store.inexpressible, which
reaches both encode.RefusedError and encode.CapabilityError; the write side's
refuse() returned a bare *encode.RefusedError instead, so a caller doing
errors.As(err, &unsupported) caught the count-scope refusal but missed
Sweeper.Sweep(Limit), DetectCycles(IncludeTracks), ReadyClaimer.ClaimNext,
BatchApplier.ApplyBatch, BatchCloser.CloseBatch, Deleter.Delete,
DependencyEditor.AddDependencies, and BatchCreator.CreateBatch.

Give InexpressibleError a detail field that preserves the original error's
composite text (an "items[%d]..." or "Issue.%s:" prefix a deeper encoder
helper already adds) instead of collapsing the message to the bare ledger
row text, and wrap every remaining write role's exported method in a single
named-return defer calling store.inexpressible, matching the pattern
lifecycle.go's Create/Update/Reopen already use.

Add TestWriteRoleRefusalsMatchTheReadShape, pinning three write-side
refusals (Sweeper.Sweep Limit, CycleDetector.DetectCycles IncludeTracks,
ReadyClaimer.ClaimNext) now classify via errors.As(*storage.ErrUnsupported)
the same way a read-side refusal does.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(cmd/bd): stop spelling out Status: StatusOpen on a markdown batch create

Review nit 8: batchcreator.go's refuseUnwirableIssue refuses a populated
Status (apigen.BatchCreateItem has no wire slot for it), and
buildMarkdownBatchRequest always set Status: types.StatusOpen explicitly, so
`bd create --file` refused on every call against an http-backed store.

PreparePublicCreateRequest already defaults an empty Status to StatusOpen on
every backend, including the http client store's own server, so the explicit
assignment here was never a different outcome - only a populated member the
wire can't carry. Leave it unset; the created issue is identical on every
backend, and the http leg's role-level accounting for why Status and
CreatedBy are excluded from its allowlists is documented on
batchCreateCarriedIssueMembers (internal/httpclient/batchcreator.go).

CreatedBy is left as-is: that member genuinely has no wire slot AND the
server does not yet stamp it from Actor (a gap already tracked in this PR's
Follow-ups), so its refusal is correct, not a bug to route around.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* docs(httpapi): correct create.go's CreatedBy comment to caller-asserted

Review nit 8: the comment claimed CreatedBy is stamped from the
"authenticated actor," but actor is parsed straight from the request body
(s.bodyActor) and never authenticated - exactly as this file's own doc
comment states a few lines above. Reword to "caller-asserted actor" and
cross-reference that doc comment so the two stay consistent. No behavior
change: the stamp itself and its test coverage were already correct.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(httpclient): raise MaxIdleConnsPerHost for a supplied client's nil Transport

Review nit 8: DialWith's doc comment promises the raised MaxIdleConnsPerHost
ceiling on every dial, "whether or not a CA is configured," but the
opts.HTTPClient.Transport == nil arm only injected a transport when the
target's CA was configured (resolved.configured()). A caller-supplied
*http.Client with a nil Transport and no CA fell through untouched, so it
defaulted to http.DefaultTransport's own ceiling of 2 at request time instead
- silently exempting this one shape from the doc's promise and forcing a
fresh TLS handshake on most of a concurrent burst even once the pool is warm.

Route this arm through the same dialTransport helper the opts.HTTPClient ==
nil arm above already uses (the CA-scoped transport when a CA is configured,
the shared baseline otherwise), injected onto a copy so the caller's own
*http.Client fields (Timeout, CheckRedirect, Jar) stay untouched.

Add TestDialWithSuppliedClientNilTransportNoCARaisesMaxIdleConnsPerHost: an
end-to-end burst through wire.Client.Do, traced with httptrace, asserting the
connection pool settles into reuse at a burst size the default ceiling of 2
cannot sustain.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* docs(httpclient): stop citing nonexistent design docs from new source files

Review nit 8: several comments added by this lift cited
engdocs/design/http-client-backend.md, "D8 row N", and beads-design/slices.json
- none of which exist in this repository (the design lived in the
bd-enterprise-internal source this code was lifted from).

Point each citation at what actually ships in-repo instead:
engdocs/design/http-divergence-ledger.md (the generated, human-readable
rendering of the divergence ledger in encode/ledger.go) for the D7/D8/D9
discipline citations in encode.go, ledger.go, bijection_test.go,
write_ledger_test.go, wire/credential.go and store.go's package doc; and a
direct description of the wire-gap it records, rather than a slices.json
scope reference, in leg_contract_wiring_test.go's cycle-tracks waiver
rationale. Regenerate http-divergence-ledger.md from ledger_render.go (which
had the same stale citation) via
`go test ./internal/httpclient/encode -run TestDivergenceLedgerDocMatchesLedger -update-ledger-doc`
so the shipped doc and its generator agree.

No behavior change; comment and generated-doc text only.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* feat(httpclient): implement issueops.BatchGetter for the HTTP client leg

The rebase onto origin/main (item 9 of PR #7247's review) brought in
upstream #7248's new issueops.BatchGetter role on storage.DoltStorage,
breaking the HTTP client leg's interface satisfaction. This wires it up
as a read role (no actor, no version guard, writes nothing — dialed as
a POST only because MaxGetManyIDs ids cannot ride a GET query string),
mirroring Counter/Querier rather than the WriteWire-wrapped roles.

- wire/paths.go: add PathIssuesBatchGet ("/v0/beads/issues:batchGet").
- batchgetter.go: httpBatchGetter.GetMany dials the server and stitches
  each resolved issue's RowVersion from apigen.BatchGetIssue.Revision
  (the role's only wire spelling of the row token, since RowVersion is
  json:"-"). checkGetManyIDs pre-validates the cap and blank-id rules,
  in the same order internal/storage/issueops.ValidateGetManyRequest
  applies them, because batch_get.go's failBatchGetErr collapses every
  validation failure into one generic, code-less InvalidArgument the
  client could never decode back into *issueops.TooManyIDsError.
- accessors.go: add the BatchGetter() accessor (26th wire-backed role).
- unsupported_gen.go: regenerated, dropping the now-implemented stub.
- completeness_test.go: move BatchGetter into wireBackedAccessors and
  bump the asserted accessor-matrix total from 28 to 29.
- served_test.go / served_harness_test.go: both package-local "by hand"
  httpapi.Config builders (serveRoles, serveConfig) now wire
  cfg.BatchGetter, fixing ~56 served-tier tests that broke once
  BatchGetter joined httpapi.Listen's required role set.
- served_batch_getter_test.go: wire the HTTP leg into all 14
  backend/conformance.RunBatchGetterXxx cases, following
  served_graph_counter_test.go's pattern. This surfaced a real bug:
  GetMany built Missing via append([]string(nil), body.Missing...),
  which stays nil when the server reports no misses, violating the
  role's "Missing is never nil on success" contract — fixed to build
  via make([]string, len(body.Missing)) + copy.

Verified: go build/vet clean; internal/httpclient suite green
(including the embedded-dolt served tier); TestEveryLegWiresEveryRoleContract
holds the http leg's adoption ceiling at exactly 42 with no change needed;
TestInterfaceCompleteness and TestAccessorMatrixMatchesDesign pass.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* build(bazel): auto-sync BUILD files

Applied from the bazel-sync-patch artifact of https://github.com/gastownhall/beads/actions/runs/37450731721
(`make bazel-sync`: gazelle, tools/bazel/go_srcs.py, bazel mod tidy).
Only BUILD.bazel, MODULE.bazel and MODULE.bazel.lock are ever pushed; see
scripts/bazel-autofix-push.sh.

* test(httpclient): lock contextServer.seen against concurrent handler goroutines

TestDialWithSuppliedClientNilTransportNoCARaisesMaxIdleConnsPerHost drives
the stub with bursts of 8 concurrent requests; the handler appended to
seen without a lock. Readers only look at seen after their requests return.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* build(bazel): sync go_srcs managed blocks for unsupportedgen after the main merge

The PR adds internal/storage/unsupportedgen on a base that predates #7320,
which gave every Bazel package a managed repo_files filegroup. On the merge,
`python3 tools/bazel/go_srcs.py --check` (TestBazelGoSrcsBlocksCurrent) found
3 stale blocks: the package's own repo_files block, its entry in the root
BUILD.bazel repo_files list, and its entry in tools/bazel/BUILD.bazel.
`make bazel-sync` regenerated exactly those; gazelle changed nothing else.

Agent-Signature: claude-code-claude-opus-5-5-max on behalf of Gas City Adopt-PR
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(httpclient): refuse DepAddItem.HasSpawner and ThreadID on applyBatch after the main merge

Main's #7209 gave issueops.DepAddItem two members, HasSpawner and
ThreadID, and a conformance case, RunBatchApplyStampsSpawnerIDOnlyWhenNamed.
ApplyDepAddItem on the v0 wire publishes source, target, type and
metadata only, so on the merge the http leg dropped both silently and
two of the PR's gates went red:

- TestEveryWireExcludedWriteMemberCarriesALedgerRow: the reflective
  census found two wire-excluded DepAddItem members with no ledger row.
- TestEveryLegWiresEveryRoleContract/http: the new case left the leg
  at 43 unwired cases against its exact ceiling of 42.

applyDepAddItemBody now refuses each member where the role would store
something the wire cannot say, under two new KindRefuse rows,
W-DepAddItem.HasSpawner and W-DepAddItem.ThreadID. The spawner flag
refuses only on a waits-for edge, because the role ignores it on every
other type and stores the same row either way. The ledger doc is
regenerated (264 rows).

The served tier wires the new case as a park on W-DepAddItem.HasSpawner,
owned by the family's existing bead, which brings the http leg back to
its ceiling. With the skip removed the case fails on the client's
refusal; with the refusal also removed it fails on the drop the row
names: spawner_id "" where the role stamps the resolved target.

Agent-Signature: claude-code-claude-opus-5-5-max on behalf of Gas City Adopt-PR
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(httpclient): address #7247 relaunch review iteration 1

Review iteration 1 of the relaunched adoption raised six majors. This
commit fixes all six. Five are the majors the first adoption's
iteration 1 raised. Its fixup, 696803f250 (tag
adopt-pr/bd-f5illd/stranded-fixup-696803f250), fixed them but never
reached the branch. That fix is ported here onto the contributor's
current head, with its reasoning unchanged; the sixth is new.

Creates refused what the CLI sends. Every `bd create` carries
CreatedBy, a workspace whose config.yaml names a prefix also carries
IDPrefix, and the client refused both.
- The server stamps created_by from the actor on all three create
  shapes: batch_create.go and batch_apply.go now match create.go.
- The client sends a CreatedBy that names the actor and refuses any
  other value, which the server's stamp would silently replace.
  createIssue and the apply create item share
  refuseUnwirableIssueMembers.
- IDPrefix refuses only where the role would act on it: an explicit,
  unforced id.
- `bd create --file` stays refused over http. Dropping its Status was
  safe but not enough: the batch create still refuses its Provenance
  and Owner. The markdown.go and batchcreator.go comments that called
  it servable now say so.

keysetFilter ignored AfterPriority. It now compares priority first,
mirroring sqlbuild's KeysetPriorityCreatedAtIDPredicate, and a new
served case resumes a priority keyset position. AfterID or AfterPriority
without AfterCreatedAt no longer reads as a zero-instant position that
discarded every row (the AfterID minor).

Claim with a patch was refused on a false ledger claim. `claim`,
`force_assignee_transfer` and `force_close_policy` now ride updateBody
like `force_notes_overwrite`, so a claim with a patch or a version guard
is one updateIssue call. A claim ALONE sent to a server that predates
the member (#6890) falls back to claimIssue. The three ledger rows are
retired, and the served cases parked on them now run.

OpenReadOnly returns a writable store. It stays writable, as a
documented exception: backends.Backend.OpenReadOnly also serves the
root pre-run's classified reads, and `bd ready --claim` writes through
that store. The exception is named in the backends.Backend contract,
the store_factory invariant and the store doc, and
TestReadOnlyOpenServesTheClaimBdReadyMakes pins it. An OpenNonMutating
backend hook is the follow-up.

Security surface.
- http_target.json is in the doctor gitignore template and its required
  patterns.
- BEADS_HTTP_TOKEN and BEADS_HTTP_TOKEN_COMMAND are host-scoped with
  BEADS_HTTP_CA_FILE's "host[:port]=value" syntax. A value scoped to
  another server falls through to the next rung, and a command scoped
  elsewhere never runs.
- LoadTarget and SaveTarget refuse a url that carries userinfo, and
  Target.String drops userinfo.

The served Tier 3 had no CI home. The new target
//internal/httpclient:httpclient_served_test is an `embedded`-tagged
sh_test. It reruns httpclient_test's binary through
tools/bazel/go_test_variant.sh with the script's
BEADS_TEST_EMBEDDED_DOLT=1 and BEADS_HTTP_TEST_REQUIRED=1, in 24 shards
on the embedded lane's race build. bazel.yml's bazel-embedded job
already runs `bazel test //... --config=embedded`, so no workflow
changes.
- -test.timeout=19m, not the script's 40m: Go's own timeout then fires,
  and dumps every goroutine, before the action's 1200s limit.
- TestBazelRetiredLanesCannotBeNarrowed pins its args and env. The new
  TestConformanceServedTierRunsUnderBazel ties the script's Tier 3
  switches to the rule.
- The new untagged TestServedTierIsLinkedWhenRequired fails a required
  run built without cgo, which drops every served file (the sentinel
  minor).
- A first 12-shard run found two test defects; both are fixed.
  TestServedBatchApplyBoundsTheItemCount's 1000-item apply outlasts the
  client's 60s per-request timeout under -race, so a
  race_detector_{on,off}_test.go pair scales its "at bound" half to 150
  there, as embeddeddolt's TestBatchApplyContract does. And
  TestTheCompositionCatchesAWrongParameter's dropped-filter case leaned
  on rows earlier tests had seeded: run alone, or first in its shard,
  it failed. It now seeds its own row outside the scope.
- conformance.sh, its script test and
  engdocs/CI_REQUIRED_CHECK_TOPOLOGY.md name the target.

Deviations from the review's suggested fixes:
- A bare BEADS_HTTP_TOKEN(_COMMAND) fails closed rather than falling
  back, and the error does not echo the value: a bare token split at an
  "=" would put token text into the pattern half. Dropping the bare
  syntax is safe today: the backend has no Register call site and no
  docs/ page names the variables.
- Target.String drops userinfo instead of using url.URL.Redacted, which
  masks only the password, so a token used as the username would print.
- The pre-#6890 claimIssue fallback leaves RowVersion unset instead of
  borrowing the follow-up read's token. That read is a second snapshot,
  so its token could postdate a write this claim never saw and arm a
  guard that should miss; a guard built from the unset token fails
  closed. Against a current server the claim rides updateIssue, whose
  `revision` is stitched as for any update.

Also fixed: the nit about the completeness failure message, which now
says to regenerate the shell, and the offrole.go tombstone comment that
named a skip list which no longer exists. Left for follow-up (all
latent, since httpclient.Register has no production caller): vocabOnce
latching a failed fetch, snapshot holding s.mu across the handshake
dial, unchunked graph anchors, private tracker IDs in park owners, and
the bounded journal limit above 10000.

Validation:
- git diff --check; gofmt -l; go vet over internal/httpclient/... and
  scripts
- go test -tags gms_pure_go over internal/httpapi/...,
  internal/httpclient/..., internal/storage/backends/... and
  backend/conformance/...; the doctor gitignore tests; the cmd/bd
  events-journal construction guard; ./scripts
- bazel test --config=embedded
  //internal/httpclient:httpclient_served_test on the lane's remote
  executors: 24 shards, 702 top-level tests, 632 pass, 70 skip (69
  ledgered KNOWN DIVERGENCE, plus
  TestCAFileHygieneRefusesGroupWritableFile, which finds no
  supplementary group on the executor), 0 fail, 0 data races; slowest
  shard 283s. tools/bazel/check_testcases.py --bep passes.
- each of the 702 tests run alone (go test -run '^Name$', without
  -race): 0 fail
- the whole tier under go test without -race, with the script's
  switches and -timeout=40m, before the two test fixes: 633 pass, 69
  skip, 0 fail
- removing BEADS_HTTP_TEST_REQUIRED from the rule fails both policy
  tests
- bazel test --config=ci over //internal/httpclient/...,
  //internal/httpapi/..., //scripts/..., //test/docsync/...,
  //internal/storage/backends/..., //backend/conformance/... and
  //cmd/bd/doctor/...: 32 tests pass
- make ci-pr-lint: nogo native plus windows/darwin, passes

Agent-Signature: claude-code-claude-opus-5-5-max on behalf of Gas City Adopt-PR
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Eddie the Engineer <adopt-pr@gascity.com>
2026-10-08 12:01:09 +00:00

796 lines
30 KiB
Go

// Contributed by gascity from bd-enterprise (internal/enterprise/httpstore/encode/encode.go@49d1df2f6)
// to OSS beads under the MIT license.
// Package encode turns the read requests bd's storage roles take into v0 query
// parameters, and refuses — never drops — everything the wire cannot carry.
//
// It is the client half of internal/httpapi's parameter decoding, and it is a
// separate package from the wire transport for one reason: the decision it
// makes is a POLICY decision, not a transport one. Dropping a filter widens a
// result set invisibly, and the server can only reject parameters it receives,
// so a filter the encoder silently forgets is a wrong answer no gate on either
// side can observe. Everything in here exists to make that impossible:
//
// - the encoder table (table.go) classifies every field of every request
// shape, and the bijection gate checks it against reflection over the
// structs, against the OpenAPI document, and against these encoders;
// - divergence ledger v1 (ledger.go, ledger_fields.go) carries the reason and
// the citation for every field that cannot make the crossing, and a refusal
// is raised BY ledger id so a refusal with no row cannot be written;
// - the refusal checks themselves are TABLE-DRIVEN rather than hand-rolled,
// so an encoder and its table cannot disagree about what refuses. What
// stays hand-written is the value rendering, which is exactly what the
// round-trip gate drives through the server's own decoder.
//
// The refusal taxonomy, the role dispositions and refuse-not-drop
// enumeration, id resolution and MaxRows all trace back to the original
// (bd-enterprise-internal) design's decision log; the divergence ledger
// itself (D9 there) is reproduced in-repo at
// engdocs/design/http-divergence-ledger.md, generated from ledger.go below.
package encode
import (
"errors"
"fmt"
"net/url"
"reflect"
"sort"
"strconv"
"time"
"github.com/steveyegge/beads/internal/types"
"github.com/steveyegge/beads/issueops"
)
// MaxExactIDs bounds the exact-ids fan-out of the SearchIssues bridge: an
// IssueFilter naming more ids than this refuses rather than issuing an
// unbounded burst of getIssue calls at one server (D11; the number itself is
// open question 6, to be measured against real call-site fan-out before GA).
const MaxExactIDs = 100
// ErrRefused matches every refusal this package raises, so a caller that only
// needs to know "the wire cannot express this" does not have to reach for the
// concrete type.
var ErrRefused = errors.New("not expressible on the v0 wire")
// RefusedError is the typed refusal: the operation being encoded for, and the
// divergence-ledger row that says what was refused, why, which decision it
// comes from and what pins it.
//
// It deliberately carries no server URL and no flag rendering. D7's three
// refusal texts are the CLI's to write — they speak the user's vocabulary and
// need the target and the server's version — and the row here is what supplies
// the flag name and the reason they read back.
type RefusedError struct {
Op Op
Shape string
Row Row
}
func (e *RefusedError) Error() string {
subject := e.Row.Flag
if subject == "" && e.Row.Type != nil {
subject = e.Row.Type.Name() + "." + e.Row.Field
}
if subject == "" {
// A row about a COMBINATION of fields has no single subject; its What
// is already the sentence.
return fmt.Sprintf("%s: %s (%s; %s)", e.Op, e.Row.What, e.Row.Why, e.Row.SpecRow)
}
return fmt.Sprintf("%s: %s is %s (%s; %s)", e.Op, subject, ErrRefused, e.Row.Why, e.Row.SpecRow)
}
func (e *RefusedError) Is(target error) bool { return target == ErrRefused }
// Encoded is what one request becomes.
type Encoded struct {
// Params is the query string, empty rather than nil for a request that
// names no parameter.
Params url.Values
// PathIDs are the ids a path-shaped encoding dials, one request each: the
// getIssue id, or the exact-ids fan-out of the SearchIssues bridge.
PathIDs []string
}
// Encode routes one source value to the encoder for an operation and shape.
//
// It exists so the gates can drive every table uniformly. Ordinary callers know
// which request they hold and use the typed functions below.
func Encode(op Op, shape string, source any) (Encoded, error) {
switch (opShape{op, shape}) {
case opShape{OpListReadyWork, ""}:
return encodeAs(op, shape, source, ReadyParams)
case opShape{OpCountReadyWork, ""}:
return encodeAs(op, shape, source, ReadyCountParams)
case opShape{OpListIssues, ""}:
return encodeAs(op, shape, source, ListParams)
case opShape{OpQueryIssues, ""}:
return encodeAs(op, shape, source, QueryParams)
case opShape{OpCountIssues, ""}:
return encodeAs(op, shape, source, CountParams)
case opShape{OpCountIssues, "byGroup"}:
return encodeAs(op, shape, source, CountByGroupParams)
case opShape{OpListReadyWork, "workFilterBridge"}:
return encodeAs(op, shape, source, ReadyBridgeParams)
case opShape{OpGetIssue, ""}:
return encodeGetIssue(op, shape, source)
case opShape{OpGetIssue, "searchExactIDs"}, opShape{OpListIssues, "searchParentWalk"}:
return encodeSearch(op, shape, source)
}
return Encoded{}, fmt.Errorf("encode: no encoder for operation %q shape %q", op, shape)
}
// opShape is the (operation, shape) pair Encode dispatches on.
type opShape struct {
op Op
shape string
}
// encodeGetIssue is Encode's arm for getIssue: GetTarget's id is the one path
// id the request dials.
func encodeGetIssue(op Op, shape string, source any) (Encoded, error) {
req, err := sourceAs[issueops.GetRequest](op, shape, source)
if err != nil {
return Encoded{}, err
}
id, v := GetTarget(req)
return Encoded{Params: v, PathIDs: []string{id}}, nil
}
// encodeSearch is Encode's arm for the two SearchIssues bridge shapes: it plans
// the filter and refuses one that plans to the other shape.
func encodeSearch(op Op, shape string, source any) (Encoded, error) {
filter, err := sourceAs[types.IssueFilter](op, shape, source)
if err != nil {
return Encoded{}, err
}
// The zero vocabulary, which is what a gate driving the table has: it
// falls back to the built-in statuses and the default infra types, the
// same reading BuildListFilter gives an unconfigured workspace.
plan, err := PlanSearch(filter, ZeroVocabulary)
if err != nil {
return Encoded{}, err
}
if string(plan.Shape) != shape {
return Encoded{}, fmt.Errorf("encode: the filter is the %q shape, not %q", plan.Shape, shape)
}
return Encoded{Params: plan.Params, PathIDs: plan.IDs}, nil
}
func encodeAs[T any](op Op, shape string, source any, encoder func(T) (url.Values, error)) (Encoded, error) {
req, err := sourceAs[T](op, shape, source)
if err != nil {
return Encoded{}, err
}
v, err := encoder(req)
if err != nil {
return Encoded{}, err
}
return Encoded{Params: v}, nil
}
func sourceAs[T any](op Op, shape string, source any) (T, error) {
req, ok := source.(T)
if !ok {
return req, fmt.Errorf("encode: operation %q shape %q takes a %T, got %T", op, shape, req, source)
}
return req, nil
}
// ReadyParams encodes a ready-work listing onto GET /v0/beads/ready.
func ReadyParams(req issueops.ReadyRequest) (url.Values, error) {
b := newBuilder(OpListReadyWork, "")
b.refuseInexpressible(req)
b.readyFilters(req)
b.boolean("brief", req.Brief)
b.str("sort", readySort(req.Sort))
b.intPtr("limit", req.Limit)
return b.done()
}
// ClaimNextParams encodes a ClaimNext ready request onto the QUERY STRING of
// POST /v0/beads/issues:claimNext.
//
// IT BUILDS AGAINST listReadyWork's TABLE, which is not laziness about a missing
// one: the claim's filter IS that listing's filter, decoded server-side by the
// same function, and giving this operation a table of its own would be a second
// declaration of one vocabulary — the exact drift the table gate exists to
// prevent. So the refusal walk, the fifteen filter parameters and the sort
// policy all come from readyTable, and what differs is what is NOT emitted.
//
// TWO PARAMETERS ARE WITHHELD and neither absence is one the server would
// forgive. `limit` is refused BY VALUE on this operation, with any value at all
// — the scan has to stay unbounded or a window of rows a racing agent already
// took would report nothing to claim while other ready work waits. `brief` has
// no spelling here, because the claim refetches its winner whole rather than
// reading it through the page's query, so the projection would have nothing to
// apply to and would answer a MUTATING request with a row saying it got
// everything. The ROLE refuses both before this encoder is reached
// (ValidateClaimNextRequest); this is the second line, and it is the one that
// holds if a caller ever reaches the encoder another way.
//
// The SORT is sent explicitly, always, exactly as the listing sends it — an
// absent `sort` is `priority` to the handler and `hybrid` to the storage layer,
// and here that difference decides WHICH ROW IS WRITTEN rather than what order
// rows are printed in.
func ClaimNextParams(req issueops.ReadyRequest) (url.Values, error) {
b := newBuilder(OpListReadyWork, "")
b.refuseInexpressible(req)
b.readyFilters(req)
b.str("sort", readySort(req.Sort))
return b.done()
}
// metadataFieldList renders the metadata equality filter as the wire's repeated
// `key=value` member, in key order — b.metadata's rule, so the object and the
// query produce the same set.
func metadataFieldList(fields map[string]string) []string {
if len(fields) == 0 {
return nil
}
keys := make([]string, 0, len(fields))
for key := range fields {
keys = append(keys, key)
}
sort.Strings(keys)
out := make([]string, 0, len(fields))
for _, key := range keys {
out = append(out, key+"="+fields[key])
}
return out
}
func boolPtr(b bool) *bool { return &b }
// strSlicePtr returns a pointer to a copy of values, or nil for an empty slice.
// An empty-but-non-nil slice constrains nothing, so it is sent as absent — the
// same reading populated() gives it on the refusal walk.
func strSlicePtr(values []string) *[]string {
if len(values) == 0 {
return nil
}
out := append([]string(nil), values...)
return &out
}
// ReadyCountParams encodes a ready-work COUNT onto GET /v0/beads/ready:count.
//
// It sends the listing's filters and nothing else: the operation publishes no
// order and no page, and the role refuses both itself.
func ReadyCountParams(req issueops.ReadyRequest) (url.Values, error) {
b := newBuilder(OpCountReadyWork, "")
b.refuseInexpressible(req)
b.readyFilters(req)
return b.done()
}
// readySort resolves the policy actually sent.
//
// An EMPTY policy is sent as the concrete `hybrid` it means, never omitted.
// Omitting it would adopt the server's own `priority` default while the caller
// meant the storage layer's hybrid fallback, and those two answer with
// different item SETS as soon as a limit truncates — the silent kind of
// divergence this package exists to make impossible.
func readySort(policy string) string {
if policy == "" {
return "hybrid"
}
return policy
}
// ListParams encodes an issue listing onto GET /v0/beads/issues.
//
// It emits no `cursor` and no `sort`: the cursor is the server's to mint and
// the pager's to echo, and the order is welded to created order on the wire —
// see the listIssues table for both.
func ListParams(req issueops.ListRequest) (url.Values, error) {
b := newBuilder(OpListIssues, "")
b.refuseInexpressible(req)
b.str("status", req.Status)
b.str("type", req.IssueType)
b.str("assignee", req.Assignee)
b.list("label", req.Labels)
b.list("label_any", req.LabelsAny)
b.list("exclude_label", req.ExcludeLabels)
b.str("parent", req.ParentID)
b.boolean("all", req.AllFlag)
b.boolean("include_templates", req.IncludeTemplates)
b.boolean("include_gates", req.IncludeGates)
b.boolean("include_infra", req.IncludeInfra)
b.boolean("include_ephemeral", req.IncludeEphemeral)
b.timestamp("created_before", req.CreatedBefore)
b.timestamp("created_after", req.CreatedAfter)
b.metadata(req.MetadataFields)
b.str("has_metadata_key", req.HasMetadataKey)
b.boolean("brief", req.Brief)
b.intPtr("limit", req.Limit)
return b.done()
}
// QueryParams encodes a boolean-expression query onto
// GET /v0/beads/issues:query.
func QueryParams(req issueops.QueryRequest) (url.Values, error) {
b := newBuilder(OpQueryIssues, "")
b.refuseInexpressible(req)
b.str("q", req.Expression)
b.boolean("all", req.IncludeClosed)
b.str("sort", req.SortBy)
b.boolean("reverse", req.Reverse)
b.intPtr("limit", req.Limit)
return b.done()
}
// CountParams encodes an issue count onto GET /v0/beads/issues:count.
//
// It sends the predicate and nothing else — there is no page, no order and no
// projection on this operation, because a cardinality has none — and it refuses
// nothing, because the operation publishes every member of the request. The
// refusal walk still runs: it is what turns a member added upstream tomorrow
// into a failure here rather than into a silently narrower predicate behind an
// unchanged-looking number.
func CountParams(req issueops.CountRequest) (url.Values, error) {
b := newBuilder(OpCountIssues, "")
b.refuseInexpressible(req)
b.countFilters(req)
return b.done()
}
// CountByGroupParams encodes a bucketed count onto the same operation.
//
// The predicate is the SCALAR encoder's, called rather than copied: the two
// methods must ask the same question of the same set, and two builders would be
// two chances to disagree about that.
//
// A dimension that is there travels VERBATIM, unrecognized ones included: the
// closed vocabulary is the ROLE's rule at every backend, refused by the role
// client before it ever reaches here — and the server refuses it too, naming
// the parameter. What this layer must not do is drop one: a group_by that went
// missing would earn a scalar answer with no `groups` member at all, which the
// caller reads as "no buckets" rather than as an error.
//
// An EMPTY dimension is the one value that does not travel, and it is not a
// drop — it is the absence itself, which no parameter can spell. Nothing
// reaches this function with one: the role client refuses an empty GroupBy with
// the unrecognized ones, for exactly the reason above. The emptiness check is
// what keeps `group_by=` off the query of a caller who came through some other
// door.
func CountByGroupParams(req issueops.CountByGroupRequest) (url.Values, error) {
v, err := CountParams(req.Filter)
if err != nil {
return nil, err
}
if req.GroupBy != "" {
v.Set("group_by", string(req.GroupBy))
}
return v, nil
}
// countFilters emits the count's whole vocabulary, which is every member of the
// request.
//
// It is spelled beside readyFilters and in the count table's order, so the
// three statements about this operation — the table, this emitter and the
// server's own countFilters decode — read as one list three times rather than
// as three lists.
func (b *builder) countFilters(req issueops.CountRequest) {
b.str("status", req.Status)
b.str("type", req.IssueType)
b.str("assignee", req.Assignee)
b.intPtr("priority", req.Priority)
b.intPtr("priority_min", req.PriorityMin)
b.intPtr("priority_max", req.PriorityMax)
b.list("label", req.Labels)
b.list("label_any", req.LabelsAny)
b.str("title", req.TitleSearch)
b.str("id", req.IDFilter)
b.str("title_contains", req.TitleContains)
b.str("desc_contains", req.DescContains)
b.str("notes_contains", req.NotesContains)
b.timestamp("created_after", req.CreatedAfter)
b.timestamp("created_before", req.CreatedBefore)
b.timestamp("updated_after", req.UpdatedAfter)
b.timestamp("updated_before", req.UpdatedBefore)
b.timestamp("closed_after", req.ClosedAfter)
b.timestamp("closed_before", req.ClosedBefore)
b.boolean("empty_description", req.EmptyDesc)
b.boolean("no_assignee", req.NoAssignee)
b.boolean("no_labels", req.NoLabels)
b.boolean("include_infra", req.IncludeInfra)
// Added alongside the table.go IncludeEphemeral/HasMetadataKey entries: the
// table declared these params but nothing here wrote them, so a populated
// field silently vanished before the request left the process.
b.boolean("include_ephemeral", req.IncludeEphemeral)
b.metadata(req.MetadataFields)
b.str("has_metadata_key", req.HasMetadataKey)
// The issues.count.scope members (upstream #7199), in the server's own
// countFilters order. Each is emitted only when populated, so a request that
// sets none of them stays byte-identical to what a pre-scope server accepts.
b.str("parent", req.ParentID)
b.boolean("no_parent", req.NoParent)
b.list("exclude_type", req.ExcludeTypes)
b.list("exclude_status", req.ExcludeStatus)
}
// GetTarget encodes a detail lookup onto GET /v0/beads/issues/{id}, returning
// the path id and the query.
//
// It cannot refuse: every member of a GetRequest is on the wire, which is what
// retired ledger row L4.
func GetTarget(req issueops.GetRequest) (string, url.Values) {
b := newBuilder(OpGetIssue, "")
b.boolean("include_dependents", req.IncludeDependents)
b.boolean("include_comments", req.IncludeComments)
b.boolean("brief_deps", req.BriefDeps)
return req.ID, b.v
}
// ReadyBridgeParams encodes the legacy types.WorkFilter onto the ready
// operation's parameters.
//
// It is the reverse mapper D8 calls deliberately throwaway: it lives until
// `bd ready`'s listing moves onto issueops.Reader upstream, and until then it
// refuses every field it cannot express rather than answering a wider question
// than was asked (L12).
func ReadyBridgeParams(f types.WorkFilter) (url.Values, error) {
b := newBuilder(OpListReadyWork, "workFilterBridge")
// The one derived default is recognized BEFORE the residual refusal sweep,
// matching the table's declaration order: Status is declared ahead of the
// plain refusals, so a filter that diverges in both refuses on the derived
// member (D4's parent-walk inversion, applied to the ready bridge's single
// derived default).
b.recognizeReadyStatus(f)
b.refuseInexpressible(f)
b.str("type", f.Type)
b.strPtr("assignee", f.Assignee)
b.boolean("unassigned", f.Unassigned)
b.list("label", f.Labels)
b.list("label_any", f.LabelsAny)
b.list("exclude_label", f.ExcludeLabels)
b.str("label_pattern", f.LabelPattern)
b.str("label_regex", f.LabelRegex)
b.intPtr("priority", f.Priority)
b.strPtr("parent", f.ParentID)
b.list("exclude_type", issueTypeNames(f.ExcludeTypes))
b.metadata(f.MetadataFields)
b.str("has_metadata_key", f.HasMetadataKey)
b.boolean("include_ephemeral", f.IncludeEphemeral)
b.boolean("include_deferred", f.IncludeDeferred)
b.boolean("brief", f.Lite)
b.str("sort", readySort(string(f.SortPolicy)))
b.intPositive("limit", f.Limit)
return b.done()
}
// ReadyBridgeCountParams encodes the same legacy types.WorkFilter onto
// countReadyWork's parameters: the size of the set ReadyBridgeParams lists a
// page of.
//
// It is ReadyBridgeParams with the page taken off, not a second mapper. The
// filter half goes through the bridge's own encoder — so every refusal it
// makes (ExcludeIDs, Offset, a non-default Status, ...) refuses here too, and a
// field the listing could not express can never be counted over a wider set —
// and then the three page-only parameters are removed: `limit` (countReadyWork
// refuses any value, and a cardinality has no page), `sort` (the count's order
// is server-fixed and its total order-independent) and `brief` (a count
// hydrates nothing). What remains is exactly readyFilterEntries, the parameter
// list the two operations share by construction.
func ReadyBridgeCountParams(f types.WorkFilter) (url.Values, error) {
f.Limit = 0
f.Lite = false
v, err := ReadyBridgeParams(f)
if err != nil {
return nil, err
}
v.Del("limit")
v.Del("sort")
v.Del("brief")
return v, nil
}
// recognizeReadyStatus inverts ready work's one derived default.
//
// listReadyWork publishes no status parameter: handleReady decodes a status-LESS
// request and the server's role re-derives the status through
// workapi.BuildReadyFilter, which is unconditionally StatusOpen — open work
// only, the set `bd list --ready` shows. So a WorkFilter carrying exactly that
// derived default is the server's own baseline: the encoder sends no `status`
// and the server reproduces the identical row set. This is what lets every real
// `bd ready` and `bd ready --json` cross the wire, because BuildReadyFilter is
// the one shape the CLI ever builds and it always stamps StatusOpen.
//
// Any OTHER status refuses (L12), which is what makes the drop match the real
// filter EXACTLY. A named status the wire cannot carry — in_progress, closed, a
// custom category — would answer over the query's own open-only default rather
// than the set named; and an EMPTY status is the storage layer's own
// open+in_progress default (types.WorkFilter.Status), which the ready operation
// cannot express either. A populated Statuses OR-set is left to the residual
// sweep, which refuses it as E-WorkFilter.Statuses.
func (b *builder) recognizeReadyStatus(f types.WorkFilter) {
if b.err != nil {
return
}
if f.Status != types.StatusOpen {
b.err = &RefusedError{Op: b.op, Shape: b.shape, Row: RowByID("E-WorkFilter.Status")}
}
}
// SearchShape names one of the two shapes the SearchIssues bridge serves.
type SearchShape string
const (
// SearchExactIDs is D11's fast path: one getIssue per named id.
SearchExactIDs SearchShape = "searchExactIDs"
// SearchParentWalk is D4's hierarchical descendant walk: paged
// listIssues?parent=<id> calls, one level at a time.
SearchParentWalk SearchShape = "searchParentWalk"
)
// SearchPlan is what a raw SearchIssues filter becomes.
type SearchPlan struct {
Shape SearchShape
// IDs is the exact-ids fan-out, in the caller's order.
IDs []string
// Params is the listing query for the descendant walk. The pager owns the
// per-page `limit` and the cursor.
Params url.Values
}
// PlanSearch classifies a raw types.IssueFilter into one of the bridge's two
// shapes, or refuses.
//
// SHAPE FIRST, THEN FIELDS. Which shape a filter is in decides which of its
// fields are readable at all — a ParentID means nothing to getIssue and an id
// set means nothing to a descendant walk — so the classification happens before
// the refusal sweep rather than after it.
//
// vocabulary is the status and type set the descendant walk's derived-default
// inversion recognizes with (parentwalk.go). It must yield the SAME ListConfig
// the filter was built from, which is what makes the inversion exact rather than
// approximate.
//
// It is a FUNCTION rather than a value because only one of the two shapes reads
// it, and the other one is the resolver's hot path: ResolvePartialID runs on
// every id-taking command, and loading a vocabulary the exact-ids arm never
// consults would put three round trips in front of every `bd show`. Deferring it
// into the arm that needs it is also what keeps a REFUSED plan from dialing at
// all — the shape is decided, and rejected, before the wire is touched.
func PlanSearch(f types.IssueFilter, vocabulary func() ListConfig) (SearchPlan, error) {
hasIDs, hasParent := len(f.IDs) > 0, f.ParentID != nil && *f.ParentID != ""
switch {
case hasIDs && hasParent:
// Refused BEFORE a shape is chosen. Letting precedence pick one would
// make the refusal cite whichever field the loser happened to be,
// which is a worse answer than naming the conflict itself.
return SearchPlan{}, &RefusedError{Op: OpListIssues, Row: RowByID("E-IssueFilter.shapeConflict")}
case hasIDs:
if len(f.IDs) > MaxExactIDs {
return SearchPlan{}, &RefusedError{Op: OpGetIssue, Shape: string(SearchExactIDs), Row: RowByID("E-IssueFilter.IDs@bound")}
}
b := newBuilder(OpGetIssue, string(SearchExactIDs))
b.refuseInexpressible(f)
if _, err := b.done(); err != nil {
return SearchPlan{}, err
}
return SearchPlan{Shape: SearchExactIDs, IDs: append([]string(nil), f.IDs...)}, nil
case hasParent:
v, err := planParentWalk(f, vocabulary())
if err != nil {
return SearchPlan{}, err
}
return SearchPlan{Shape: SearchParentWalk, Params: v}, nil
}
return SearchPlan{}, &RefusedError{Op: OpListIssues, Row: RowByID("E-IssueFilter.noShape")}
}
// issueTypeNames widens a typed exclusion list onto the wire's plain strings.
func issueTypeNames(in []types.IssueType) []string {
if len(in) == 0 {
return nil
}
out := make([]string, 0, len(in))
for _, t := range in {
out = append(out, string(t))
}
return out
}
// builder accumulates one request's parameters and its first refusal.
//
// FIRST refusal rather than last, mirroring internal/httpapi's own query
// decoder: the answer must not depend on the order a caller happens to populate
// fields in, and the table's declaration order is the order the sweep walks.
type builder struct {
op Op
shape string
v url.Values
err error
}
func newBuilder(op Op, shape string) *builder {
return &builder{op: op, shape: shape, v: url.Values{}}
}
// refuseInexpressible walks this encoding's table and refuses the first
// populated field the wire cannot carry.
//
// It is table-driven on purpose. A hand-rolled check per field is a check that
// can be forgotten for the field added next week, and the forgetting is silent:
// the encoder would emit nothing for it and the server would have nothing to
// reject. Reading the table means the encoder and the classification the gates
// verify are the SAME statement rather than two that agree today.
func (b *builder) refuseInexpressible(source any) {
if b.err != nil {
return
}
table, ok := TableFor(b.op, b.shape)
if !ok {
b.err = fmt.Errorf("encode: no encoder table for operation %q shape %q", b.op, b.shape)
return
}
rv := reflect.ValueOf(source)
if rv.Type() != table.Source {
b.err = fmt.Errorf("encode: %s expects %s, got %s", table.Op, table.Source, rv.Type())
return
}
for _, entry := range table.Fields {
if entry.Disposition != DispRefused {
continue
}
field := rv.FieldByName(entry.Name)
if !field.IsValid() {
b.err = fmt.Errorf("encode: %s has no field %s", table.Source, entry.Name)
return
}
if populated(field) {
b.err = &RefusedError{Op: b.op, Shape: b.shape, Row: RowByID(entry.Ledger)}
return
}
}
}
// populated reports whether a field carries a value the caller set.
//
// An empty-but-non-nil slice or map is NOT populated: it constrains nothing, so
// refusing it would turn a no-op into an error. A non-nil pointer IS, even to a
// zero value — priority 0 is a real priority and `Ephemeral: &false` is a real
// restriction, and both have been lost by code that read a zero as absent.
func populated(v reflect.Value) bool {
switch v.Kind() {
case reflect.Slice, reflect.Map:
return v.Len() > 0
default:
return !v.IsZero()
}
}
func (b *builder) str(param, value string) {
if value != "" {
b.v.Set(param, value)
}
}
func (b *builder) strPtr(param string, value *string) {
if value != nil {
b.str(param, *value)
}
}
// boolean emits only the TRUE spelling. Every flag on this surface documents
// false as its default, so an explicit `false` would be a parameter that says
// nothing — and one more value for the server to parse.
func (b *builder) boolean(param string, value bool) {
if value {
b.v.Set(param, "true")
}
}
// intPtr emits a pointer-valued number, INCLUDING zero. The pointer is what
// distinguishes unset from an explicit value, which is the whole reason these
// fields are pointers.
func (b *builder) intPtr(param string, value *int) {
if value != nil {
b.v.Set(param, strconv.Itoa(*value))
}
}
// intPositive emits a plain int only when it bounds something. The legacy
// filters spell "no bound" as 0, so a zero here is an absent parameter rather
// than the wire's `limit=0`, which means unlimited and is refused off loopback.
func (b *builder) intPositive(param string, value int) {
if value > 0 {
b.v.Set(param, strconv.Itoa(value))
}
}
func (b *builder) list(param string, values []string) {
for _, value := range values {
b.v.Add(param, value)
}
}
// timestamp emits an instant in UTC with whatever sub-second precision it
// carries. RFC3339Nano round-trips through the server's time.Parse without
// losing a fractional second, which a bare RFC3339 format would silently drop —
// and a dropped fraction on a created bound is a widened result set.
func (b *builder) timestamp(param string, value *time.Time) {
if value != nil {
b.v.Set(param, value.UTC().Format(time.RFC3339Nano))
}
}
// metadata emits the repeatable key=value equality filter, in key order so one
// filter always produces one query string.
//
// The parameter name is not a parameter of this method: every operation that
// publishes the filter at all spells it `metadata_field`, so taking it from the
// caller would be one more thing a call site could get wrong for no expressive
// gain.
func (b *builder) metadata(fields map[string]string) {
const param = "metadata_field"
if len(fields) == 0 {
return
}
keys := make([]string, 0, len(fields))
for key := range fields {
keys = append(keys, key)
}
sort.Strings(keys)
for _, key := range keys {
b.v.Add(param, key+"="+fields[key])
}
}
// readyFilters emits the filter vocabulary listReadyWork and countReadyWork
// share, which is every parameter but the order and the page.
func (b *builder) readyFilters(req issueops.ReadyRequest) {
b.str("type", req.IssueType)
b.str("assignee", req.Assignee)
b.boolean("unassigned", req.Unassigned)
b.list("label", req.Labels)
b.list("label_any", req.LabelsAny)
b.list("exclude_label", req.ExcludeLabels)
b.str("label_pattern", req.LabelPattern)
b.str("label_regex", req.LabelRegex)
b.intPtr("priority", req.Priority)
b.str("parent", req.ParentID)
b.list("exclude_type", req.ExcludeTypes)
b.metadata(req.MetadataFields)
b.str("has_metadata_key", req.HasMetadataKey)
b.boolean("include_ephemeral", req.IncludeEphemeral)
b.boolean("include_deferred", req.IncludeDeferred)
}
func (b *builder) done() (url.Values, error) {
if b.err != nil {
return nil, b.err
}
return b.v, nil
}