Skip to content

fix(context): keep private store errors behind verbose output - #220

Merged
scbrown merged 2 commits into
mainfrom
gennaro/880-private-store-diagnostic-20261029
Nov 5, 2026
Merged

scbrown merged 2 commits into
mainfrom
gennaro/880-private-store-diagnostic-20261029

Conversation

@scbrown

@scbrown scbrown commented Oct 29, 2026

Copy link
Copy Markdown
Collaborator

A knowledge-enabled bobbin context can still return useful code when its optional Quipu store is unavailable, but its default warning prints the full backend error, including the absolute database path. Emit one short notice that graph ranking is unavailable and keep the backend error behind the existing --verbose option.

Quiet, JSON and explicit PPR-off behavior remain unchanged. This does not repair an unavailable store or claim graph ranking occurred; the normal code-context result remains visible.

Validation: built the exact base and repair with --features knowledge. On the same public Flask index, the base reproduces the private-path warning and the repair returns the expected function with exactly one path-free fallback notice. Verbose retains details; quiet, JSON and PPR-off remain clean. All six real CLI controls pass. Repository knowledge/private-key controls pass. Both builds and controls use the HOME-escape guard; 157 watched paths and five UID resources remain untouched.

Demo: the unchanged shared terminal renderer accepts both native search/context frames from the repair as a 20-second recording, including the honest optional-store warning. The original failing before-frame contains an absolute private path, so its raw reproduction is retained privately for the independent reviewer. No terminal-output filtering or renderer fork. This source patch does not publish a release, replace an installed executable or activate a runtime consumer.

Work-item: aegis-880

Bead: aegis-880

Overlap preflight: b5eb0ed34723ac4ae38ea84151e29be341debb3ae2b371f0b139e6af0747cc92

@scbrown
scbrown marked this pull request as ready for review November 5, 2026 14:31
@scbrown

scbrown commented Nov 5, 2026

Copy link
Copy Markdown
Collaborator Author

P0 aegis-iwm author refresh: normal current-main merge d9ad0d2. Actual knowledge-feature cargo check PASS/HOME158paths+5UID clean; final proposal diff remains the same single context-warning file. Normal publication remote-exact; marked ready. Prior six native CLI behavior controls retained in PR body; no claim they were rerun in this refresh. Fresh hosted complete-green gate pending; Tim owns classify/ONE review/land, release/install separate.

@scbrown
scbrown merged commit ed39298 into main Nov 5, 2026
3 checks passed
@scbrown
scbrown deleted the gennaro/880-private-store-diagnostic-20261029 branch November 5, 2026 14:45
@scbrown

scbrown commented Nov 5, 2026

Copy link
Copy Markdown
Collaborator Author

Independent post-merge source audit of head d9ad0d2, merged as ed39298: no blocking code findings in the one-file, five-insertion/three-deletion delta. The default store-open failure notice is constant and path-free; the backend error chain prints only with explicit verbose output inside the unchanged non-quiet/non-JSON guard. PPR-off does not enter store opening; successful store attachment and later assembly/access filtering are unchanged. The notice truthfully describes fallback without graph ranking.

Scope: exact source diff and surrounding selection/store/assembly path only. I did not reproduce a new build, native frame, installed executable or release. Author controls remain attributed to the author. This advisory audit is post-merge, not a retrospective pre-merge approval receipt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant