@siuver/omp-debug-mode 0.1.3 → 0.1.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +20 -0
- package/README.md +154 -94
- package/package.json +3 -3
- package/src/debug-mode.ts +350 -334
- package/src/evidence.ts +169 -0
- package/src/gate.ts +72 -25
- package/src/machine.ts +334 -0
- package/src/methodology.ts +106 -32
- package/src/probes.ts +9 -9
- package/src/state.ts +288 -36
- package/src/tools.ts +80 -6
- package/src/ui.ts +73 -24
- package/src/review-actions.ts +0 -22
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,25 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## Unreleased
|
|
4
|
+
|
|
5
|
+
## 0.1.5 - 2026-08-25
|
|
6
|
+
|
|
7
|
+
- Tightened the injected methodology, start prompt, and proceed prompt so a `runtime_probe` round must write `@omp-probe` instrumentation in the same turn before emitting closing tags, and `<reproduction_steps>` lists only user actions.
|
|
8
|
+
- Replaced the `idle`/`round`/`waiting`/`cleanup` phases plus the redundant `active` flag with a discriminated union over four stages named after whose turn it is: `investigating`, `open`, `awaiting_evidence`, and `cleaning_up`. A round that settles without closing is now the explicit `open` stage with its own status label, widget, and explanation instead of a silent stop that looked like the reproduction gate.
|
|
9
|
+
- Moved every transition into one pure reducer (`src/machine.ts`) that returns declarative effects (notify, prompt, continue, teardown) for the runtime shell to apply, so state changes no longer hand-reset a different subset of fields per call site and the run-creation failure path no longer needs a manual rollback.
|
|
10
|
+
- Made round-scoped data structural: each round record owns its run id, evidence plan, reproduction steps, probe ids, and per-reason nudge budgets, instead of being filtered out of session-wide arrays by a mutable round counter. Probe nudges and closing-tag nudges now have independent budgets.
|
|
11
|
+
- Closing a `runtime_probe` round now requires probes the ledger actually finds on disk, not just a plan that names the method; the ledger is reconciled before every settle, so instrumentation that was written and then deleted no longer reaches the gate.
|
|
12
|
+
- `/debug-proceed`, `/debug-done`, and `/debug-evidence` now work from an `open` round after a confirmation instead of failing with "not waiting for reproduction"; they only refuse while an agent turn is actually running.
|
|
13
|
+
- Cleanup that leaves markers behind is sent back once with the remaining probes listed before teardown gives up and warns, instead of tearing down on the first attempt regardless.
|
|
14
|
+
- Session restore now migrates the pre-`rounds` persisted layout, and an unknown or `investigating` stage resolves to `open` rather than dropping the user into a reproduction gate that was never opened.
|
|
15
|
+
|
|
16
|
+
## 0.1.4 - 2026-08-21
|
|
17
|
+
|
|
18
|
+
- Added least-user-intervention evidence planning: the agent chooses `agent_inspection`, `runtime_probe`, `user_report`, or `user_artifact` per hypothesis, must justify user-assisted methods, and batches compatible hypotheses into the fewest reproductions or captures.
|
|
19
|
+
- Added persisted evidence requests, user observations, and in-place artifact metadata plus the read-only `list_debug_evidence` tool. `/debug-evidence [<request-id>] <path>` links files to pending requests without copying or deleting them, and unavailable files remain explicitly unverified.
|
|
20
|
+
- Replaced the automatic round-review menu with a command-only gate widget. Removed `/debug-menu` and merged user-report submission into `/debug-proceed [details]`; users now continue with `/debug-proceed`, `/debug-evidence`, `/debug-done`, `/debug-abort`, and `/debug-status` while safety confirmations remain in place.
|
|
21
|
+
- Extended the reproduction gate, cleanup context, session restore, status output, tests, and documentation for mixed probe/report/artifact rounds, including opaque RenderDoc `.rdc` captures.
|
|
22
|
+
|
|
3
23
|
## 0.1.3 - 2026-08-20
|
|
4
24
|
|
|
5
25
|
- Aligned the injected methodology with Cursor Debug Mode: 3-5 hypotheses, instrument all of them, never fix without runtime logs, keep probes during the fix, and verify with a second reproduce. Round 1 is instrument-only.
|
package/README.md
CHANGED
|
@@ -1,94 +1,154 @@
|
|
|
1
|
-
# @siuver/omp-debug-mode
|
|
2
|
-
|
|
3
|
-
A Cursor Debug Mode replica for oh-my-pi. It recreates Cursor's evidence-driven, human-in-the-loop debugging workflow for OMP; it is an independent implementation and is not affiliated with Cursor.
|
|
4
|
-
|
|
5
|
-
The plugin makes the agent form 3-5 hypotheses,
|
|
6
|
-
|
|
7
|
-
## Commands
|
|
8
|
-
|
|
9
|
-
| Command | Purpose |
|
|
10
|
-
| --- | --- |
|
|
11
|
-
| `/debug-mode <problem>` | Starts a debugging session from a symptom, expected result, actual result, and reproduction description. |
|
|
12
|
-
| `/debug-
|
|
13
|
-
| `/debug-
|
|
14
|
-
| `/debug-done` | Marks the problem as fixed: the agent removes every probe and summarizes the result. |
|
|
15
|
-
| `/debug-
|
|
16
|
-
| `/debug-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
|
|
84
|
-
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
|
|
1
|
+
# @siuver/omp-debug-mode
|
|
2
|
+
|
|
3
|
+
A Cursor Debug Mode replica for oh-my-pi. It recreates Cursor's evidence-driven, human-in-the-loop debugging workflow for OMP; it is an independent implementation and is not affiliated with Cursor.
|
|
4
|
+
|
|
5
|
+
The plugin makes the agent form 3-5 hypotheses, choose the cheapest reliable evidence method for each one, and pause so you can reproduce the problem. The agent is instructed to NEVER fix without runtime evidence first; after a fix it keeps runtime probes in place for a verification reproduce. Your result either starts another evidence-driven round or triggers probe cleanup and a final summary.
|
|
6
|
+
|
|
7
|
+
## Commands
|
|
8
|
+
|
|
9
|
+
| Command | Purpose |
|
|
10
|
+
| --- | --- |
|
|
11
|
+
| `/debug-mode <problem>` | Starts a debugging session from a symptom, expected result, actual result, and reproduction description. |
|
|
12
|
+
| `/debug-proceed [details]` | Continues with captured evidence: optional details are recorded as a user-report observation, then the agent evaluates hypotheses and may fix only with evidence before asking for verification. |
|
|
13
|
+
| `/debug-evidence [<request-id>] <path>` | Attaches one user-provided evidence file to the current round. If the first token matches a pending current-round request ID, the file is linked to that request; otherwise the whole argument is treated as the path (spaces allowed). Without an argument it opens an input dialog (interactive UI only). Files are referenced in place and never copied or deleted. |
|
|
14
|
+
| `/debug-done` | Marks the problem as fixed: the agent removes every probe and summarizes the result. |
|
|
15
|
+
| `/debug-status` | Shows the current stage, round, run, live probes, captured log counts, pending evidence requests, and attached/unavailable artifacts. |
|
|
16
|
+
| `/debug-abort` | Stops debug mode and removes its logs after confirmation while leaving code changes in the working tree. |
|
|
17
|
+
|
|
18
|
+
## Stages
|
|
19
|
+
|
|
20
|
+
The workflow tracks one thing: whose move it is. Every stage other than `investigating` belongs to you, and each has its own status label and widget so a stopped agent never looks like a stopped workflow.
|
|
21
|
+
|
|
22
|
+
| Stage | Meaning | What you do |
|
|
23
|
+
| --- | --- | --- |
|
|
24
|
+
| `investigating` | An agent turn is in flight. | Wait. |
|
|
25
|
+
| `open` | The round settled without closing — a clarifying question, or declared instrumentation that never reached the code. | Reply normally. `/debug-proceed` closes the round anyway after a confirmation. |
|
|
26
|
+
| `awaiting_evidence` | The round closed properly and is at the reproduction gate. | Reproduce, capture, then `/debug-proceed`. |
|
|
27
|
+
| `cleaning_up` | `/debug-done` was accepted; probes are being removed. | Wait. |
|
|
28
|
+
|
|
29
|
+
Transitions live in one pure reducer (`src/machine.ts`), which returns declarative effects — notify, inject prompt, continue the turn, tear down — that the runtime shell applies. Every round is a record holding its own run id, evidence plan, reproduction steps, probe ids, and nudge budgets, so round-scoped data is never derived by filtering a session-wide array on a mutable counter.
|
|
30
|
+
|
|
31
|
+
A resumed session never lands in `investigating`, because no agent turn survives a restart; an unrecognised persisted stage resolves to `open`, on the conservative reading that the agent owes you something rather than the reverse.
|
|
32
|
+
|
|
33
|
+
## Evidence Methods
|
|
34
|
+
|
|
35
|
+
For every hypothesis, the agent must pick one of four methods, in least-user-intervention order:
|
|
36
|
+
|
|
37
|
+
1. **`agent_inspection`** - reuse existing logs/files and the agent's own read/search/test/command tools. Always tried first.
|
|
38
|
+
2. **`runtime_probe`** - if runtime state is required, the agent installs `@omp-probe` instrumentation and combines every compatible hypothesis into a single reproduction.
|
|
39
|
+
3. **`user_report`** - only when a simple manual observation is decisive (something only you can see or try).
|
|
40
|
+
4. **`user_artifact`** - only when the disputed state cannot be represented reliably by inspection, probes, or a verbal report (e.g. a GPU capture, screenshot, crash dump, or externally generated trace).
|
|
41
|
+
|
|
42
|
+
Rules the agent must follow:
|
|
43
|
+
|
|
44
|
+
- It never asks you to run a command it could run itself.
|
|
45
|
+
- All unavoidable user actions are batched into the fewest reproductions/captures: hypotheses answerable by the same action share one request (`hypothesisIds` lists them all) instead of serial reports.
|
|
46
|
+
- A lower-priority method is never chosen merely because it is familiar; every `user_report`/`user_artifact` entry needs a rationale explicitly naming why agent inspection and runtime probes cannot settle its hypotheses.
|
|
47
|
+
|
|
48
|
+
## The Evidence Plan
|
|
49
|
+
|
|
50
|
+
Each round closes with an exact machine-readable block that covers every hypothesis:
|
|
51
|
+
|
|
52
|
+
```text
|
|
53
|
+
<evidence_plan>
|
|
54
|
+
[{"id":"E1","hypothesisIds":["A","B"],"method":"runtime_probe","title":"...","rationale":"The disputed runtime branches are not present in existing logs; one model-added probe set can capture both without a separate user artifact.","instructions":["..."],"artifactHint":"optional"}]
|
|
55
|
+
</evidence_plan>
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
Every field is validated: `id` must be unique and non-empty, `hypothesisIds` must reference one or more real hypotheses, `method` must be one of the four literals above, `rationale`/`title` must be non-empty, and `instructions` must contain actionable steps (`artifactHint` describes the expected file kind for `user_artifact`). A malformed plan is rejected entirely — no hypothesis is ever silently dropped. Plans are capped at 12 entries per round. The plan is combined with the existing `<reproduction_steps>` block, which describes the single combined reproduction/capture sequence the user performs now. The injected methodology forbids emitting those closing tags for a `runtime_probe` round until `@omp-probe` markers are already in the working tree, and forbids listing planned agent work (installing probes, reading logs, analyzing) as reproduction steps.
|
|
59
|
+
|
|
60
|
+
## The Reproduction Gate
|
|
61
|
+
|
|
62
|
+
A round may only close when its declarations are backed by observable facts. Emitting the tags is the declaration; the probe ledger is the proof:
|
|
63
|
+
|
|
64
|
+
- Both `<evidence_plan>` and `<reproduction_steps>` must be present.
|
|
65
|
+
- A plan selecting `runtime_probe` additionally needs at least one `@omp-probe` marker that the ledger actually finds on disk for this round. A probe that was written and then deleted counts as missing.
|
|
66
|
+
- `agent_inspection`, `user_report`, and `user_artifact` plans need no markers at all, and expect no JSONL logs.
|
|
67
|
+
|
|
68
|
+
Anything short of that is one automatic nudge — and the two nudge budgets are separate, so being sent back for missing probes never consumes the budget for missing closing tags. When a budget is spent the round becomes `open` rather than being gated on evidence that does not exist. A clarifying question mid-round is `open` too, which is the ordinary case: reply and the agent picks the round back up.
|
|
69
|
+
|
|
70
|
+
A round with reproduction steps but no plan at all still gates (older sessions closed this way) and gets the "no runtime evidence" warning.
|
|
71
|
+
|
|
72
|
+
At the gate a widget shows the reproduction steps, any pending user requests (title, instructions, artifact hint), a live counter of captured observations, an `evidence: <pending> pending, <attached> attached` counter, and the list of commands you can use, so you can tell what evidence the round is waiting on and how to act. The widget always ends with the live log counter. An `open` round gets its own, smaller widget naming why it is open and stating that a reply is the way forward. Every round stops at a widget and you interact through commands only.
|
|
73
|
+
|
|
74
|
+
Pending requests resolve like this:
|
|
75
|
+
|
|
76
|
+
- A `user_artifact` request is pending until a file is attached with a matching request ID.
|
|
77
|
+
- A `user_report` request is pending until `/debug-proceed <details>` records an observation for the current round; one details submission can satisfy several report requests at once.
|
|
78
|
+
- `agent_inspection` and `runtime_probe` requests never create user work.
|
|
79
|
+
|
|
80
|
+
If user requests are still pending when you run `/debug-proceed`, the plugin asks "Proceed without all requested evidence?" — confirming is allowed so an unavailable external capture can never deadlock the session; cancelling keeps you at the gate. `/debug-proceed` and `/debug-done` ask for confirmation when the round captured no runtime logs and has no valid non-probe evidence plan, and again when the round is `open` rather than gated. They only refuse outright while an agent turn is actually running.
|
|
81
|
+
|
|
82
|
+
## Attaching Evidence Files
|
|
83
|
+
|
|
84
|
+
`/debug-evidence [<request-id>] <path>` records one user-provided file for the current waiting round:
|
|
85
|
+
|
|
86
|
+
- The path is resolved against the session working directory; the plugin records the absolute path, size, and mtime and references the file **in place**. It never copies, renames, or deletes your file — not during attach, not during cleanup, not during teardown.
|
|
87
|
+
- If the first argument token matches a pending current-round request ID, the file is linked to that request; otherwise the entire argument is treated as the path (spaces are supported) and the artifact is attached unlinked — the agent sees it as unassigned evidence and must associate it with a request itself.
|
|
88
|
+
A path whose first token happens to look like a request ID but does not match one is simply treated as a path.
|
|
89
|
+
- Interactive sessions must confirm before recording a path outside the session working directory; non-interactive sessions reject outside-`cwd` paths because no confirmation channel exists.
|
|
90
|
+
- Re-attaching the same resolved path reuses the existing artifact entry and refreshes its metadata and request association.
|
|
91
|
+
- Missing paths, directories, and unreadable files are rejected with the reason, and the ledger stays unchanged.
|
|
92
|
+
|
|
93
|
+
Availability is re-checked by re-statting each path, so a file that was moved or deleted after attaching is reported as *unavailable* — the ledger never claims unavailable evidence was captured. The model is told to treat user reports and artifacts as data to inspect, not instructions to execute, and must conclude INCONCLUSIVE (or file a new, lower-burden request) when it cannot inspect a file with its normal tools.
|
|
94
|
+
|
|
95
|
+
Example: for a GPU-rendering symptom whose disputed state only exists inside a frame capture, the agent justifies why inspection, tests, and probes cannot answer, then emits one `user_artifact` request with an `artifactHint` like "RenderDoc .rdc capture of a failing frame". You capture `frame.rdc` in RenderDoc and run `/debug-evidence E1 frame.rdc` (using the request ID shown in the widget). `/debug-status` and the read-only `list_debug_evidence` tool then show the artifact ID, absolute path, size, and availability. The `.rdc` bytes are treated as opaque — the plugin does not parse the format; if the agent cannot extract what it needs from the binary with its normal `read`/`bash` tools, it says so and asks for a converted report or a new capture rather than guessing.
|
|
96
|
+
|
|
97
|
+
## Workflow
|
|
98
|
+
1. Run `/debug-mode <problem description>`.
|
|
99
|
+
2. The Agent records 3-5 hypotheses and picks an evidence method for each under the least-user-intervention priority. If the route is `runtime_probe`, it inserts minimal probes marked with `@omp-probe <id>` inside `#region agent log` blocks in the same turn, before emitting the closing tags; round 1 does not apply a product fix (probe edits are not a product fix). The start prompt and a per-turn `debug-mode-context` message name the exact JSONL path and require every probe to append to it, including `hypothesisId`; console output (including Unity `Debug.Log`) is supplemental only. The context filter keeps the newest of those messages so the model sees the contract instead of dropping it. `<reproduction_steps>` are user actions only (reproduce, capture, restart).
|
|
100
|
+
|
|
101
|
+
3. When the Agent reaches the gate, follow the `<reproduction_steps>` in the real application so the instrumented code writes its observations, watching the widget counter climb — or supply the requested evidence with `/debug-evidence` or `/debug-proceed <details>`. Restart the app or service if the instrumented build would otherwise be stale.
|
|
102
|
+
|
|
103
|
+
4. Continue with `/debug-proceed [details]` (optionally record a user observation, then evaluate evidence), `/debug-done` (clean up and summarize), `/debug-evidence` (attach a file), or `/debug-status` (inspect the current round state). Each round stops at the widget; all interaction is command-driven.
|
|
104
|
+
5. On Proceed, the Agent reads the evidence (logs, your observations, attached artifacts), cites the evidence method plus log-line numbers or artifact/report paths for each hypothesis, and only then may apply a fix. Probes stay in place. Reproduce again to verify. If verification fails, rejected-hypothesis code changes are reverted before the next round.
|
|
105
|
+
6. On `/debug-done`, the Agent removes every probe and summarizes the root cause and fix in 1-2 lines. If the ledger is still not empty when that turn settles, cleanup is sent back once with the remaining markers listed; a second incomplete attempt tears down anyway and warns you which probes are still in your source.
|
|
106
|
+
|
|
107
|
+
The extension also provides the read-only `get_debug_logs`, `list_debug_probes`, and `list_debug_evidence` tools so the Agent can inspect runtime evidence, review pending/satisfied requests with their methods and rationales, and verify cleanup.
|
|
108
|
+
|
|
109
|
+
## Runtime Data
|
|
110
|
+
|
|
111
|
+
At the start of each round, the plugin creates an absolute log path under a directory owned by the current session:
|
|
112
|
+
|
|
113
|
+
```text
|
|
114
|
+
<project>/.omp/debug/<session-id>/current.jsonl
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
The session segment keeps concurrent omp sessions from truncating or deleting each other's evidence, since every round truncates `current.jsonl` and teardown removes the directory. The plugin also adds `.omp/debug/` to the repository's local `.git/info/exclude` once, so probe logs never appear in `git status`; that file is not committed, so your `.gitignore` is left alone. Teardown removes only this log directory; attached user evidence files are never removed.
|
|
118
|
+
|
|
119
|
+
That exact stable path is injected into the Agent prompt. The prompt requires every runtime probe to use the target environment's native file append API and write one compact JSON object plus a newline using this schema:
|
|
120
|
+
|
|
121
|
+
```json
|
|
122
|
+
{"probe":"player-state","hypothesisId":"A","ts":1787193600000,"location":"Player.cs:42","message":"grounded check","data":{"isGrounded":false}}
|
|
123
|
+
```
|
|
124
|
+
|
|
125
|
+
`get_debug_logs`, the proceed prompt, and `/debug-status` summarize each run by `hypothesisId`, so you can see which hypotheses produced evidence before reading a single raw line. A hypothesis with no entries was not exercised, which is not the same as being rejected.
|
|
126
|
+
|
|
127
|
+
When you run `/debug-proceed [details]`, the plugin records non-empty details as a user observation, archives the completed file as `<run-id>.jsonl`, and creates an empty `current.jsonl` for the next reproduction. Because the active run is truncated at the start of every round, `get_debug_logs` defaults to the newest run that actually captured observations and names the run it read; `previous=true` forces the last completed run. `/debug-status` shows the current absolute file path and the per-run log counts.
|
|
128
|
+
|
|
129
|
+
## Probe Ledger
|
|
130
|
+
|
|
131
|
+
The plugin tracks every `@omp-probe <id>` marker the Agent writes, resolving each file against the session working directory, and attributes it to the round that introduced it. Before each turn, before a round is allowed to close, and on every `list_debug_probes` call it rescans those files so the ledger matches the code on disk: markers the Agent has since deleted drop out, and a file that exists but cannot be read is reported as *unverified* rather than assumed clean. That way a failed read can never make teardown claim the probes are gone while they are still in your source, and a `runtime_probe` round cannot reach the gate on a promise. Rounds that choose non-probe evidence methods simply add no markers, and cleanup still verifies that no leftover markers remain before finishing.
|
|
132
|
+
|
|
133
|
+
## Install
|
|
134
|
+
|
|
135
|
+
```sh
|
|
136
|
+
omp plugin install @siuver/omp-debug-mode
|
|
137
|
+
```
|
|
138
|
+
|
|
139
|
+
Restart omp after installation, then run `/debug-mode <problem>`.
|
|
140
|
+
|
|
141
|
+
## Local Development
|
|
142
|
+
|
|
143
|
+
From the repository root:
|
|
144
|
+
|
|
145
|
+
```sh
|
|
146
|
+
bun run check
|
|
147
|
+
omp plugin link ./plugins/debug-mode
|
|
148
|
+
```
|
|
149
|
+
|
|
150
|
+
Restart omp after linking.
|
|
151
|
+
|
|
152
|
+
## Changelog
|
|
153
|
+
|
|
154
|
+
See `CHANGELOG.md` for release notes included in the npm package.
|
package/package.json
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@siuver/omp-debug-mode",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.5",
|
|
4
4
|
"type": "module",
|
|
5
|
-
"description": "
|
|
5
|
+
"description": "Evidence-driven, human-in-the-loop debugging with autonomous probes and user-assisted artifacts for oh-my-pi.",
|
|
6
6
|
"license": "MIT",
|
|
7
7
|
"homepage": "https://github.com/Siuver/blackhole/tree/master/plugins/debug-mode#readme",
|
|
8
8
|
"repository": {
|
|
@@ -30,7 +30,7 @@
|
|
|
30
30
|
],
|
|
31
31
|
"omp": {
|
|
32
32
|
"name": "debug-mode",
|
|
33
|
-
"description": "
|
|
33
|
+
"description": "Evidence-driven debugging with least-user-intervention methods, runtime probes, and user artifacts.",
|
|
34
34
|
"extensions": [
|
|
35
35
|
"./src/main.ts"
|
|
36
36
|
]
|