Lab #3563: VaultService.requireExistenceProvider labels the vault instance name as its type

Follow-up to swamp-club#3561. PR #3173 changed requireDeleteProvider, requireAnnotationProvider and requireRefreshHookProvider in src/domain/vaults/vault_service.ts to name the configured vault type via the private vaultTypeOf(vaultName) helper instead of provider.getName(). requireExistenceProvider, added by swamp-club#3557 (PR #3172), merged two minutes earlier and was not covered: on main it still throws Vault 'name' (type: provider.getName()) does not support existence checks (vault_service.ts line 470). For built-in providers getName() returns the instance name (ControlPlaneVaultProvider returns the reserved vault name and does not implement has, so it can reach this message), so the parenthetical shows the vault name instead of its type. Fix: use this.vaultTypeOf(vaultName) in that message, and add a test like the requireDeleteProvider one in vault_service_test.ts: register a per-run vaultTypeRegistry type whose provider lacks has and answers getName() with the instance name, call the existence check on a vault named erp, assert the exact message names the registered type, and invalidateType in finally.

data_writer_property_test: a secret holding a newline and a literal backslash-n escapes the persisted-content property (seed 1648929202)

typed-secrets: the accessor adapter reads a legacy row stamped with the empty namespace as foreign, so its tagged fields stay reference text on the typed path

typed-secrets query view: route a row's JSON content by whether the adapter adapted the record, not by the service's namespace rule

flaky: for_each_name_property_test lets the text around a sentinel equal the secret's value, so the untyped value search replaces both and the property fails by seed

typed-secrets 4.3: the expression-facing query view registers Secret in DataQueryService

flaky: LitestreamReplicator 'a failed launch releases its lock probe, so the next acquire starts a sidecar' fails by timing in verify-build

CEL duration arithmetic is off by a second when a duration has negative nanos (cel-js 7.6.1)

typed-secrets 4.2: live and reconstructed step outputs and child outputs return references through the accessor adapter

A coded UserError a model method throws reaches a workflow step without its code, because InProcessExecutor keeps only the message

Dashboard Workflows page takes ~19s on a serve with many extension workflows: workflow.search resolves each workflow's owner with a full extension-workflow scan

codegen: BROKEN_REGEXES override for the @swamp/aws/invoicing InvoiceUnit name lacks the u flag, so it rejects ordinary names

dashboard: run page polling stacks history.get and history.logs requests while serve is slow

serve: add child spans and attributes to workflow.history.get (and run_summary/run_search) to diagnose slow dashboard loads

serve: webhook-triggered workflow runs can't be cancelled — cancel can't find them, so it reports serve's own pid as "the process running it is still alive"

A workflow step fails on a static validation error in a method it does not invoke, where swamp behavior run of the same method succeeds

serve: a run orphaned by a container restart can't be cancelled — the restarted serve reuses the dead owner's pid, so cancel reports the owner still alive

typed-secrets 4.6: turn the typed path on for every entry point, remove the internal option, and delete the regular-expression rewrite, the value search and the plaintext resolution of tagged fields

typed-secrets 4.5: the inline resolutions refuse or mask: placement, task selectors, child references and deferred targets refuse secrets, assert messages mask them, and the deprecated resolvers go

typed-secrets 4.4: persistence and resume hold references: rehydration stops reading the vault, every persisted copy uses the persisted form, and run events are masked

typed-secrets 4.1: workflow passes bind sentinels as Secrets: typed guards and asserts, forEach items and identities, child bindings, webhook inputs, and the synchronous authorization step

typed-secrets 3.5: local entry points, validation diagnostics, context.runModel and model.method delivery

model.method in a workflow guard fails with 'Do not know how to serialize a BigInt' when its inputs hold an int

data query: filter on data lifecycle so deleted resources can be excluded

CEL expression results that hold a timestamp, duration or uint become an empty object

Catalog rebuild restores pre-rename versions of a name renamed away and written again

Remote resolveSecret allowlist is always empty for workflow steps that use vault.get

swamp issue redacts git commit SHAs as secrets and fast-check replay paths as IP addresses

typed-secrets 3.4: destination refusals, identifier stand-ins, shell safety and masking

Remote readResource does not apply the legacy schema fallback for untagged sensitive records

Flaky: datastore_v3_outbox_model_property_test throws MayLandLaterError on a random seed (aged commit, failed discard-and-mark checkpoint, power cut)

v3 outbox model property test fails: a commit dropped after a failed append-discard-and-mark reports MayLandLaterError instead of the expected outcome

Workflow step dataOutputOverrides vaultName is accepted but silently dropped

typed-secrets 3.3: sensitive-field accessors, data-origin sentinels and reference validation

Generated vault keys carry raw data-name and vary characters that strict vault providers reject

typed-secrets 3.2: vault.get as a CEL function, bare-token rewriting, AST extraction and up-front existence checks

typed-secrets 3.1: the production Secret, its refusals, the fault context, the container rule and the boundary conversion, behind the internal option

Flaky test: extension_pull_dependency_conflict_test fails with 'failed to copy esbuild binary' during deno bundle

Extension tarball analyzer ignores webhook entry points

Registry drops contentMetadata.extensions (method grafts) at confirm-push

digitalocean codegen leaves an orphaned security_secret.ts model file after its endpoint left the spec

A --repo-dir or SWAMP_REPO_DIR through a symlink fails with 'unable to open database file'

@swamp/1password: vault delete of a missing item probably fails instead of being a no-op

@swamp/1password: item or vault names containing 'authorization' are misreported as auth failures

typed-secrets 2.2: VaultSecretBag entries hold references, one registry per run, 128-bit sentinels

Show wait keys and pending signals to remote clients and the dashboard

Flaky: LitestreamReplicator.acquire 'concurrent acquires in one process share one sidecar and one hold' fails 'no hold leaked' under full-suite load

VaultService.requireExistenceProvider labels the vault instance name as its type

VaultService capability errors label the vault instance name as its type

typed-secrets 2.1: VaultExistenceProvider, its conformance suite, and has on the built-in providers

MockVaultProvider.get and delete throw synchronously instead of rejecting

typed-secrets 1.2: pin the Secret Proxy, refusal set and container rule on cel-js 7.6.1

issue-lifecycle: pr_merged and ship report success and advance the phase when swamp-club is unreachable, writing nothing upstream

serve check-config crashes with a TypeError when a list-valued auth key is a string

access grant list --server shows user subjects as user:user:<name>

Flaky: process_bundle_prober_test 'stopping a host that has already exited lists no children under its pid' fails under full-suite load

typed-secrets 0.4: characterize worker secret authorization and control-plane secret traffic

issue-lifecycle: an approved plan cannot be sent back to planning

typed-secrets 1.2: minimal opaque Secret, CelVaultNamespace receiver, policy inventory and evaluation frame

typed-secrets 1.1: commit the cel-js 7.6.1 probe harness as pinned behavior tests

typed-secrets 0.1: land the typed-secrets plan as a design enabler doc

swamp update: a slicker, colorful download progress bar that ends with a newline

gcs-datastore: a failed lock read is reported as "unlocked" — #2298 in the GCS backend

A manual worker verify racing an enrollment probe can leave a healthy worker unverified until it reconnects

bundle freshness: a one-off deno info failure leaves a source on the in-directory fallback for good

serve shutdown waits for an unsignalled run index rebuild: the continuation sweep's boot pass and request-led rebuilds cannot be stopped by SIGTERM

serve: handlers that sanitize an error for the client never log the original, so path-bearing failures are undiagnosable

literal() output in a step's inputs logs repeated Refusing to evaluate expression warnings

Read non-string sensitive resource fields back with their type

serve and swamp dashboard shutdown waits seconds for the run index warm-up: the plain index parse is not abortable, and the warm-up waits on request-led loads it joined (regression from #3105)

Run index snapshot cache keeps serving a stale run status: ctime is only second-resolution so in-place same-size rewrites alias the stamp, and snapshots are cached even when repair could not write the index (regression from #3105)

Flaky: serve_v3_extension_lockfile_test 'serve extension.pull commits the new entry' fails under full-suite load with extension_pull_failed

Relationships

#3563 VaultService.requireExistenceProvider labels the vault instance name as its type

Shipped