Repository navigation
deps: refresh minimal embedded profile to the current qualified telemetry stack #167
Description
The root application and minimal embedded profile intentionally have separate
dependency authorities, but the embedded profile is now substantially behind
the stack being qualified for current telemetry capture.
Root update branch:
deps/sorted-json-sdk-stack-20261018.
The three-file root update does not claim to update or qualify the profile.
profiles/embedded/deps.edn currently pins SDK 8110c12f, driver 3e3141fd,
exporter dfbc9ea6, ordinary JSON 97298fd8. The root candidate uses SDK
7878a2eb, driver 3d766fa, exporter 4d48871c, ordinary JSON 0f51b991, with
native byte JSON 96f3e47d opt-in. Shared source alone does not propagate these
dependency updates to applications selecting :deps/root "profiles/embedded".
Follow-up acceptance:
- Refresh the profile's declared SDK/exporter/driver/ordinary JSON selections
together, with explicit opt-in byte-JSON configuration if exposed. Preserve
its no-server/no-viewer dependency boundary and consumer precedence. - Choose an actually qualified runtime/floor; do not continue advertising an
older floor merely because it is written in the previous profile. Preserve
current runtime-control binaries and benchmark baselines as historical data. - Update the profile's exact-root and mutation tests plus user documentation.
- Requalify authoritative application state plus embedded telemetry, typed
capture/query, background-query retirement, bounded remote-destination
behavior and fresh recovery where applicable. No live Langfuse or Samizdat
integration claim from a hermetic fixture alone. - Keep provider ownership, independent queues and shutdown/confirmation
guarantees intact. Run the real profile fixture from its own working
directory; root application tests do not qualify the profile.
This is a follow-up to the already completed profile delivery in #77, not a
reason to reopen it or rerun unchanged exhaustive models. Coordinate with the
existing #144 fixture work before superseding or rebasing it.
Activity
casselc commentedon Oct 21, 2026
Root-only follow-up is now PR #178 at
95ec6cb518897b9f0dcc60cff5ff787caafef845: exporter -> mergeda6cbf939, while direct SDK3366a332/driver3314b79/ordinary JSON0f51b991/codec7ab2bed and all defaults remain unchanged.This does NOT update this issue's minimal profile or roll out stacked #144's ancestors. The correct current-main baseline and candidate headless suites pass on official stock Jolt0.8.23; each graph must select its own native package. Forcing root26.9 globally onto the old26.7.3 minimal profile correctly fails its timestamp guard, so that launcher mismatch is explicitly retained rather than called a profile implementation regression.
Root stock CI has actually run the new post-startup field-slot witness, existing file-backed embedded/standalone fresh-reader cases and native HTTP reader. Other final-head checks remain pending; PR178 is not merged yet.
Independent typed physical-field recovery is tracked separately in #177: the current typed fixture is memory-backed/live-query, not the same file-backed recovery case. That distinction also belongs in this issue's eventual minimal-profile qualification. No profile scope or runtime floor is silently changed by root greens.
casselc commentedon Oct 21, 2026
Root-stack pin PR #178 merged at 0aa881c after all seven exact-head checks passed, including Durable/S3, stock mixed signals, native profiles, headless and Chromium. Claude bounded source review completed. This integrates exporter a6cbf939 only at the root; profiles/embedded remains untouched, so this issue stays open. No rollout of stacked #144 or throughput/tail claim. Independent typed file-backed recovery remains separately tracked by #177.