Skip to content

Fix self-test probe isolation and cleanup - #113

Open
PracticalSwan wants to merge 1 commit into
rebel0789:mainfrom
PracticalSwan:fix/self-test-probe-isolation
Open

Fix self-test probe isolation and cleanup#113
PracticalSwan wants to merge 1 commit into
rebel0789:mainfrom
PracticalSwan:fix/self-test-probe-isolation

Conversation

@PracticalSwan

Copy link
Copy Markdown

Summary

  • run the selected-only Pro context probe even when the write probe is disabled
  • use a bounded existing workspace file, or an empty selected-only context, instead of depending on the temporary write probe
  • restore a pre-existing .ai-bridge/codexpro-self-test.md exactly after diagnostics, or remove the transient probe and empty directory when self-test created them
  • add smoke coverage for disabled write probing, transient cleanup, and pre-existing probe restoration

Fixes #104
Fixes #105

Verification

  • npm run build
  • node scripts/smoke.mjs
  • git diff --check

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.

Self-test write probe can leave .ai-bridge residue after diagnostics pro_context_probe is skipped when self-test write_probe is disabled

1 participant