jessey/rigdoctor
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 59 Wiki Activity

feat: guided diagnostic session (CLI) — pick a game, capture, analyze — 0.11.0 #6

Merged
jessey merged 1 commits from feat/m6-steam-detection into main 2026-05-22 06:28:21 +00:00
Conversation 0 Commits 1 Files Changed 10
+263 -5
jessey commented 2026-05-22 06:28:14 +00:00
Owner
Copy Link
Copy Source

The seed use case end to end, orchestrating M3 + M4 (ARCHITECTURE §7.1).

  • core/diagnostic.py: start(game) runs a focused, game-tagged capture into a
    dedicated diagnostic log (window-scoped report, separate from the always-on
    crash log); finish() stops it and combines the capture summary (M3) with the
    health findings (M4). Game recorded as a log event so it survives crash+reboot.
  • CLI: rigdoctor diagnose start --game/--appid | status | finish.
  • recorder/record run gained an optional --game tag; reccontrol passes it through.
  • Tests for game recovery + the finish() combination.

GUI/tray "Run Diagnostic" button and auto start/stop (D12 wrapper) come next.

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

The seed use case end to end, orchestrating M3 + M4 (ARCHITECTURE §7.1). - core/diagnostic.py: start(game) runs a focused, game-tagged capture into a dedicated diagnostic log (window-scoped report, separate from the always-on crash log); finish() stops it and combines the capture summary (M3) with the health findings (M4). Game recorded as a log event so it survives crash+reboot. - CLI: rigdoctor diagnose start --game/--appid | status | finish. - recorder/record run gained an optional --game tag; reccontrol passes it through. - Tests for game recovery + the finish() combination. GUI/tray "Run Diagnostic" button and auto start/stop (D12 wrapper) come next. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
jessey added 1 commit 2026-05-22 06:28:15 +00:00
feat: guided diagnostic session (CLI) — pick a game, capture, analyze — 0.11.0 5682878f22 
The seed use case end to end, orchestrating M3 + M4 (ARCHITECTURE §7.1).

- core/diagnostic.py: start(game) runs a focused, game-tagged capture into a
  dedicated diagnostic log (window-scoped report, separate from the always-on
  crash log); finish() stops it and combines the capture summary (M3) with the
  health findings (M4). Game recorded as a log event so it survives crash+reboot.
- CLI: rigdoctor diagnose start --game/--appid | status | finish.
- recorder/record run gained an optional --game tag; reccontrol passes it through.
- Tests for game recovery + the finish() combination.

GUI/tray "Run Diagnostic" button and auto start/stop (D12 wrapper) come next.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
jessey merged commit 7a283dc338 into main 2026-05-22 06:28:21 +00:00
jessey deleted branch feat/m6-steam-detection 2026-05-22 06:28:22 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Improvement
Improvement suggestions on existing functionality
 bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jessey
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: jessey/rigdoctor#6
Delete Branch "feat/m6-steam-detection"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?