Pre-release soak: v0.1.0-rc.15

[Cliftonz]

Soak metadata

• Pre-release tag: v0.1.0-rc.15
• Tag commit: fca4225
• Target stable: v0.1.0
• Bump kind: minor (v0.0.5 → v0.1.0)
• Soak start (UTC): 2026-05-27T03:06:14Z
• Soak end (UTC, minimum, +72h): 2026-05-30T03:06:14Z
• Diff vs last stable: v0.0.5...v0.1.0-rc.15
• Diff vs prior rc.14: v0.1.0-rc.14...v0.1.0-rc.15
• Cohort planned: macOS arm64 + Ubuntu / Fedora / Windows VMs (TBD per maintainer availability)
• Channels excluded per docs/release-quirks-jarvy.md: Homebrew, install.sh, install.ps1 (tarball pipeline gap, broken since v0.0.1)

Trigger-matrix rows matched (13 of 15)

• Tool registry, Setup orchestration, Provisioner, Package deps, Network/proxy,
  Self-update, Roles, Drift detection, Git config, Logging/ticket, Telemetry,
  Distro packaging, Release workflow

Carry-forward from rc.14 soak (#11, signed off 2026-05-22..25)

Finding	Severity	rc.15 status
Windows .msi cohort gap	gap (signed off)	Still applies — solo maintainer, no Windows hardware. Re-evaluate if host becomes available before promotion.
Finding 7 — v0.0.5 jarvy update is no-op	sev-2 documented	Already in [Unreleased] CHANGELOG (a736354); will roll into curated ## [v0.1.0] on stable cut.
Findings 2, 3, 5, 6, 8 (cosmetic)	sev-3	Tracked for v0.1.x backlog; do not block promotion.

Delta rc.14 → rc.15 (what specifically must re-soak)

The rc.14 install/upgrade/rollback findings still carry IF the underlying code paths didn't change. Delta touches:

• src/telemetry.rs (+366 LoC) — OTLP env opt-in fix, host.name resource attr, Source::Request variant
• src/tools/unsupported.rs (+671 LoC, new) — jarvy tools --request feedback loop
• src/tools/spec.rs (+171 LoC) — fuzzy-suggest cache, iter_tool_names
• src/network/auth.rs (+37 LoC) — url_encode delegation
• OTEL crate stack 0.31 → 0.32 — affects only telemetry-enabled users
• dist/helm/jarvy-telemetry-forwarder — chart-only, not CLI; does not affect end-user soak surface

Install / upgrade / rollback code paths are NOT touched rc.14 → rc.15. Paths 1, 2, 4, 5 from the rc.14 soak still carry. Newly required for rc.15: verify telemetry env-only opt-in actually exports + jarvy tools --request works.

Validation Progress

• Step 1: Trigger matrix matched (13/15 rows)
• Step 2: This issue
• Step 3: Pre-soak matrix (carry-forward + delta)
  • Path 1 — Fresh install (macOS arm64) — CARRIES from rc.14 (install path untouched)
  • Path 1 — Fresh install (Ubuntu 22.04 x86_64 .deb) — CARRIES from rc.14
  • Path 1 — Fresh install (Fedora 40 x86_64 .rpm) — CARRIES from rc.14
  • Path 1 — Fresh install (Windows 11 .msi) — GAP (signed off in rc.14 soak)
  • Path 2 — Upgrade v0.0.5 → rc.15 — CARRIES from rc.14 (update code path untouched)
  • Path 3 — Skip-version (N/A — v0.0.5 is only prior stable)
  • Path 4 — Rollback rc.15 → v0.0.5 — CARRIES from rc.14
  • Path 5 — Multi-tool 10+ tool config — CARRIES from rc.14
  • NEW rc.15 delta — Telemetry env-only opt-in actually exports records (the fixed bug)
  • NEW rc.15 delta — jarvy tools --request <name> happy path + already-supported short-circuit
• Step 4: Major-only matrix — N/A (minor bump)
• Step 5: Open soak window
• Step 6: Fault-injection drills — N/A (minor bump)
• Step 7: Evaluate promotion criteria
• Step 8: Promote to v0.1.0 OR cut -rc.16
• Step 9: Post-stable propagation (AUR, winget, Chocolatey)

Pre-flight verifications

• Tag signature: ✓ Good ED25519 signature (git tag -v v0.1.0-rc.15)
• isPrerelease: pending (release workflow still building at issue-open time)
• Tag commit fca4225 matches main HEAD

Soak signal log

(append comments throughout the 72h window)

Promotion decision

(filled at Step 7)

[Cliftonz]

rc.15 release workflow: SUCCESS ✓

Check	Status
Workflow conclusion	success
Failed jobs	0
Tag signature	ED25519 verified (git tag -v v0.1.0-rc.15)
isPrerelease	true ✓
isDraft	true (per docs/release-quirks-jarvy.md — manual publish step deferred until soak passes)
Primary assets	13 (3 .rpm + 3 .deb + 1 .dmg + 1 .msi + 1 .exe + 1 .AppImage + SHA256SUMS + 2 SBOMs)
Sigstore companions	36 (12 × .sig/.pem/.bundle)
Sigstore verify on jarvy_0.1.0_aarch64.dmg	Verified OK ✓
Tarballs (install.sh / Homebrew)	absent — documented gap per quirks doc; cohort excludes those channels

Release URL: https://github.com/bearbinary/Jarvy/releases/tag/v0.1.0-rc.15

The draft will publish after the soak window elapses + delta paths verify, per the per-version-authorization rule in docs/release-quirks-jarvy.md ("The point of no return is the draft publish, not the tag push").

Running the two rc.15 delta paths next.

[Cliftonz]

rc.15 delta verification: BOTH PATHS PASS ✓

Delta 1 — jarvy tools --request <name> flow

Ran four sub-cases against target/release/jarvy built at commit fca4225 (the rc.15 tag commit):

Sub-case	Input	Result
1a unknown tool, telemetry off	--request webdev-cli	Pre-filled GitHub URL printed; scaffold rendered; all 8 template placeholders substituted including __PKG_BSD__ (the drift fix from a31d875) ✓
1b already-supported inventory tool	--request git	"already supported" short-circuit; no request URL leaked ✓
1c already-supported registry-only tool	--request nvm	"already supported" short-circuit ✓ — confirms both spec::get_tool_spec AND registry::get_tool branches are checked (would silently emit a bogus request if the registry branch was dropped)
1d typo → fuzzy suggest	--request dokcer	Suggested docker, dagger, dotnet in that order — confirms the prefix-match-boost ranks docker first (the round-2 review check) ✓

Delta 2 — Telemetry env-only opt-in actually exports records

This is the bug fix from commit 0c6538c. Reproduced the pre-fix condition: no ~/.jarvy/config.toml telemetry section, env-only opt-in (JARVY_TELEMETRY=1 JARVY_OTLP_ENDPOINT=http://localhost:4318). Started a local Python HTTP server on :4318 that accepts and counts POSTs, then ran jarvy tools --request fake-tool-xyz-123 (which emits one tool.unsupported event + counter increment).

Result:

HTTP POSTs received: 2
  → POST /v1/metrics  ct=application/x-protobuf  body=513 bytes
  → POST /v1/logs     ct=application/x-protobuf  body=646 bytes

Pre-fix this run would have produced zero POSTs (the bug). Post-fix both the metrics and logs pipelines exported, and they went to the correct /v1/{logs|metrics} paths (fix #2 in the same commit — with_endpoint() needs the full URL, not a base, hence the resolve_otlp_endpoint helper).

Also worth noting: jarvy telemetry status with the same env shows Status: enabled / Exporter: healthy (no separate file-config required), and lists environment variables in the "Configuration sources" footer. The "half-on telemetry stack" the commit message warns about is gone.

Pre-soak matrix verdict for rc.15

Path	Status
1 macOS arm64 fresh install	carries from rc.14 (install path untouched between rc.14 → rc.15)
1 Ubuntu .deb fresh install	carries from rc.14
1 Fedora .rpm fresh install	carries from rc.14
1 Windows .msi fresh install	gap (signed off in rc.14 soak; no Windows host)
2 upgrade v0.0.5 → rc.15	carries from rc.14 (update path untouched)
3 skip-version	N/A — v0.0.5 is only prior stable
4 rollback rc.15 → v0.0.5	carries from rc.14
5 multi-tool 10+ tool config	carries from rc.14
NEW jarvy tools --request flow	PASS (this comment)
NEW telemetry env-only opt-in exports	PASS (this comment)

Net: 9/10 PASS, 1 gap (Windows .msi) signed off. Pre-soak matrix complete.

Soak window OFFICIALLY OPEN

• Soak start (UTC): 2026-05-27T03:06:14Z
• Earliest promotion (+72h minor minimum): 2026-05-30T03:06:14Z

Signals to watch through the window:

• ERROR/WARN lines in ~/.jarvy/logs/jarvy.log on cohort hosts not present in v0.0.5 baseline
• GitHub issues against rc.15 tagged release-blocker or regression
• jarvy drift check unexpected non-zero exits
• Telemetry export errors (now that env-only opt-in actually exports — any BatchLogProcessor.ExportError lines would surface here)

Pace: 12h check-ins on this issue. /loop 12h is appropriate for a 72h minor soak.