feat(core): add read-only progress diagnostics (#1060)#1103
Open
shaun0927 wants to merge 1 commit into
Open
Conversation
Constraint: OpenChrome core may expose deterministic session facts but must not stop, retry, or recover on behalf of the host.\nRejected: Automatic stuck-session recovery in core | would turn hinting into hidden workflow policy and conflict with the pilot boundary.\nConfidence: high\nScope-risk: moderate\nDirective: Keep recovery execution in pilot-only tools; oc_progress_status should remain advisory and side-effect-free.\nTested: npm test -- --runInBand tests/tools/oc-progress-status.test.ts; npm run build; npm run lint:changed\nNot-tested: Live MCP browser smoke with coordinate-click fixture
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
ⓘ You've reached your Qodo monthly free-tier limit. Reviews pause until next month — upgrade your plan to continue now, or link your paid account if you already have one. |
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
28 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #1060.
Directionality / overlap check
ProgressTrackerand activity-tracker telemetry instead of adding a new autonomous harness loop.oc_progress_statussurface or equivalent anti-wandering diagnostic endpoint.Summary
oc_progress_statuswith structuredprogressing | stalling | stuckdiagnostics.refresh_state,switch_strategy,checkpoint_and_recover, orstop_episodewithout performing those actions.includeRecentCallsis requested.Verification
npm test -- --runInBand tests/tools/oc-progress-status.test.tsnpm run lint:changednpm run build(afternpm installto restoreyamlfrom currentdevelopdependencies)Merge-after validation with OpenChrome
read_page,tabs_context,computerscreenshot), then calloc_progress_status({ includeRecentCalls: true }); expectstatus: "stalling", redacted compact call summaries, andsuggestedPolicy: "refresh_state".oc_progress_status; expectstatus: "stuck",consecutiveErrors >= 3, andsuggestedPolicy: "checkpoint_and_recover".oc_progress_status; expectcoordinateClickStreak >= 3,topSignal.rule: "coordinate-click-stall", andsuggestedPolicy: "switch_strategy".Not tested