Separate Rider discovery from readiness

This commit is contained in:
Meta Vens 2026-07-13 17:08:29 +01:00
commit 53e5246896
6 changed files with 19 additions and 8 deletions

View file

@ -29,8 +29,8 @@ fn run_smoke() -> Result<Value> {
let status = run_bridge(&root, &workspace, &artifact_root, &fake_rider, &["status"])?;
require(
status["status"] == "ready",
"fake Rider path should make status ready",
status["status"] == "discovered",
"fake Rider path should be reported as discovered",
)?;
require(
status["riderPath"] == fake_rider.to_string_lossy().as_ref(),

View file

@ -311,7 +311,7 @@ fn discover_solution(project_root: &Path) -> Result<serde_json::Value> {
top_level.sort();
if !top_level.is_empty() {
return Ok(json!({
"status": "ready",
"status": "found",
"path": top_level[0],
"candidates": top_level.iter().take(8).collect::<Vec<_>>(),
}));
@ -319,7 +319,7 @@ fn discover_solution(project_root: &Path) -> Result<serde_json::Value> {
let mut candidates = Vec::new();
collect_solutions(&root, &root, &mut candidates)?;
Ok(json!({
"status": if candidates.is_empty() { "missingSolution" } else { "ready" },
"status": if candidates.is_empty() { "missingSolution" } else { "found" },
"path": candidates.first(),
"candidates": candidates.iter().take(8).collect::<Vec<_>>(),
}))
@ -384,7 +384,7 @@ fn vcs_summary(project_root: &Path) -> serde_json::Value {
}
}
json!({
"status": if branch.is_some() { "ready" } else { "notGit" },
"status": if branch.is_some() { "gitDetected" } else { "notGit" },
"branch": branch,
"dirty": status.as_deref().is_some_and(|value| !value.is_empty()),
"changedFiles": changed_files,
@ -438,12 +438,12 @@ fn status_rider(options: &RiderOptions) -> Result<serde_json::Value> {
let solution = discover_solution(&project_root)?;
let first_rider = installations.first();
let status = if first_rider.is_some() {
"ready"
"discovered"
} else {
"missingRider"
};
let note = if first_rider.is_some() {
"Rider executable is available for explicit source navigation and context capture."
"A Rider executable candidate was discovered for explicit source navigation and context capture."
} else {
"No Rider executable was found. Install Rider or set EPIPHANY_RIDER_PATH."
};

View file

@ -1480,3 +1480,10 @@ only for a matching completed receipt, `attention` for an inconsistent pair,
when neither exists. The operator snapshot readback likewise reports `loaded`,
not `ready`, when a snapshot is merely present. Cache lookup owns retrieval;
the joined lifecycle evidence owns lifecycle status.
## Tool discovery is not operational readiness
The Rider bridge called a discovered executable path, solution file, and Git
branch `ready` without executing or validating any of them. These projections
now report `discovered`, `found`, and `gitDetected`. Discovery owns topology;
only an actual launch receipt may later claim operability.

View file

@ -564,3 +564,7 @@ an older latest completion. Its statuses are lifecycle facts (`missing`,
Negative unit coverage proves intent presence is only requested and mismatched
receipt identity cannot close it. Both native smokes, 259 library tests, focused
binary tests, and the all-bin check pass.
Rider bridge topology no longer claims readiness from path existence. Rider is
`discovered`, solutions are `found`, and repository topology is `gitDetected`;
the native bridge smoke passes with the renamed evidence states.

Binary file not shown.

View file

@ -660,4 +660,4 @@ current_status:
- Service lifecycle receipt history is now event-only: `load_epiphany_cultmesh_daemon_service_lifecycle_receipts` filters out the `epiphany-local/daemon-service-lifecycle-receipt/latest` mirror, while `load_latest_epiphany_cultmesh_daemon_service_lifecycle_receipt` remains the latest-state reader. Focused unit test `service_lifecycle_receipt_history_excludes_latest_mirror` proves two per-receipt writes return exactly two history records and latest points at the second. Fresh smoke `verse-query-lifecycle-history-filter-smoke` and live overview/triage `local-20260618-145632-497-efac6f0d` / `local-20260618-145632-321-867947af` prove compact swarm sights still expose service lifecycle attention plus the present elevated runbook artifact without daemon pokes or service mutation. Do not use a broad unscoped cargo test filter for this check on Windows; it fans out across bin harnesses and hit a broken pipe during this pass.
- `epiphany-verse-query seed-compact` is the compact seed receipt for wrappers and read-only rites. The older `seed` command still prints the full local Verse context for explicit debugging, but compact wrapper modes now avoid full `seed`/final `query` readback after the combined overview proof exposed Windows debug stack overflow from full-context serialization pressure.
last_completed_repo_swarm_cut: Huginn live-fire has crossed the first real repo Body from Persona pressure to branch-local Hands commit and Soul/Mind closure, and now has repeatable closure and redacted-public-proof mouths. On `E:\Projects\Huginn` branch `epiphany/huginn/first-awakening`, `tools/epiphany_local_run.ps1 -Mode repo-persona-intake` accepted item `huginn-inspection-readback-livefire`, Weksa/Persona intake remained sealed, and `epiphany-work derive-plan` lowered it to model-authored safe family `repo.status_section` for `README.md` only. `tools/epiphany_local_run.ps1 -Mode repo-swarm-run` advanced four bounded pulses: run-from-plan, adopt-from-plan, execute-from-plan, and close-from-execute. Huginn commit `e9b07c38fceabbdc89ea35c2156326c80c0393a2` updated only `README.md`; closure receipt `.epiphany\work\work-close-huginn-inspection-readback-livefire.json` records status `closed`, Soul verdict `passed`, Mind state commit `repo-work-close-huginn-inspection-readback-livefire-mind-commit`, safe family `repo.status_section`, path scope `README.md`, Bifrost publication gate, and `privateStateExposed=false`. Verification also ran Huginn's TypeScript compiler through concrete Node path: `C:\Program Files\nodejs\node.exe E:\Projects\Huginn\node_modules\typescript\bin\tsc -p tsconfig.json` passed. Native verifier `epiphany-repo-livefire-closure-smoke --workspace E:\Projects\Huginn --item huginn-inspection-readback-livefire --expected-path README.md --expected-family repo.status_section --expected-gate awaiting-publication --expected-blocker bifrost-publication-missing` checks closure receipt, Mind map entry, overview gate/blocker, authority seals, and `git show` changed paths, returning `status=ok`, `soulVerdict=passed`, `publicationGate=Bifrost`, and `privateStateExposed=false`. Wrapper `tools/epiphany_local_run.ps1 -Mode repo-livefire-closure -Workspace E:\Projects\Huginn -RepoWorkItem huginn-inspection-readback-livefire -SkipBuild` exposes the same read-only proof through the local operator mouth; artifact `local-20260621-190156-803-2f85ba15` printed commit, path, gate, blocker, Soul verdict, Mind commit receipt, and `privateStateExposed=False` without push, merge, publication, or target mutation. New wrapper `tools/epiphany_local_run.ps1 -Mode repo-work-public-proof -Workspace E:\Projects\Huginn -RepoWorkItem huginn-inspection-readback-livefire -SkipBuild` exports the redacted proof bundle and repo-local Verse index without publishing; artifact `local-20260621-190645-345-4555b1dc` wrote `.epiphany\public\proof-bundles\repo-work-public-proof-huginn-inspection-readback-livefire.json`, proof id `repo-work-public-proof-huginn-inspection-readback-livefire`, SHA-256 `857545b199f3e37eb06c2e757e5cfc201958e46667bb1f8403fd333a22620f63`, nine artifact rows, zero publication rows, and `privateStateExposed=False`. swarm overview readback `local-20260621-190701-140-b9519ec6` sees the `REPO-WORK-PUBLIC-PROOF` row and action row from Huginn's repo-local Verse with the same SHA-256 while Bifrost publication remains missing. Launcher compact modes are now named compact operator-context modes instead of read-only modes, and `bifrost-public-proof` summaries print item, target public Verse, room, proof SHA-256, review receipts, and credit receipts so publication receipts are auditable without claiming upstream sync.
next_action: Continue the observation-to-consequence audit. Heartbeat store presence no longer claims scheduler readiness, operator snapshots report `loaded`, and operator-run latest joins the newest intent to its exact `run_id` receipt before deriving lifecycle status; independent latest mirrors cannot counterfeit completion. Next inspect remaining `ready` projections, especially git/repository and provider-capability surfaces, for topology or existence standing in for operational readiness. Keep closure's zero-substring invariant.
next_action: Continue the observation-to-consequence audit. Heartbeat, operator-cache, and Rider topology projections no longer turn presence into readiness; Rider paths are discovered, solutions found, and Git topology detected. Next inspect provider-capability and editor-bridge projections for discovery or configuration standing in for verified operability. Keep closure's zero-substring invariant.