kedi-debugger 0.1.0__tar.gz

kedi_debugger-0.1.0/.gitignore

@@ -0,0 +1,16 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+.venv/
+.env
+.env.*
+.pypirc
+.coverage
+.coverage.*
+coverage.xml
+htmlcov/
+.pytest_cache/
+.ruff_cache/
+build/
+dist/
+.DS_Store

kedi_debugger-0.1.0/LICENSE

@@ -0,0 +1,203 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   Copyright © 2025 - Kedi Programming Language
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

kedi_debugger-0.1.0/PKG-INFO

@@ -0,0 +1,206 @@
+Metadata-Version: 2.5
+Name: kedi-debugger
+Version: 0.1.0
+Summary: Optional stdio Debug Adapter Protocol backend for Kedi
+Project-URL: Documentation, https://docs.kedi-lang.org/tooling/debugger/
+Project-URL: Source, https://github.com/kedi-lang/kedi-debugger
+Project-URL: Tracker, https://github.com/kedi-lang/kedi-debugger/issues
+License: Apache-2.0
+License-File: LICENSE
+Requires-Python: >=3.11
+Requires-Dist: kedi<0.2,>=0.1.1
+Requires-Dist: python-dotenv<2,>=1.2.2
+Description-Content-Type: text/markdown
+
+# Kedi Debugger
+
+An optional, local Debug Adapter Protocol (DAP) backend shared by the Kedi VS Code
+and Zed extensions. The protocol supervisor owns a separate Kedi worker process.
+The normal runtime does not import this package or record debugger snapshots.
+
+This package lives in [kedi-lang/kedi-debugger](https://github.com/kedi-lang/kedi-debugger)
+and is pinned as the `debugger/` submodule in the Kedi repository. From an existing
+Kedi checkout, initialize it with `git submodule update --init debugger`.
+
+## Local Installation
+
+The updated editor extensions automatically install this package in their shared
+managed environment, including upgrades of existing managed installations. This
+requires the matching runtime and debugger releases on the package index; source
+changes do not publish those releases.
+
+For local development or a selected host Python, use the same interpreter for
+the editor, Kedi, debugger, and program dependencies:
+
+```sh
+python -m pip install -e /path/to/kedi
+python -m pip install --no-deps -e /path/to/kedi/debugger
+python -c 'import kedi_debugger; from kedi.debugging import DebugEvent, observe_execution'
+```
+
+This source checkout adds runtime hooks that older Kedi installations do not have.
+The debugger and updated extensions have not been published automatically. A
+missing package is an installation error, not a reason to select another Python.
+Both extensions reuse the selected host interpreter or `~/.kedi/editor-venv`;
+neither creates a second debugger environment or modifies a host environment.
+
+The machine-facing entry point is `python -m kedi_debugger --stdio`.
+`kedi debug --stdio` is an equivalent CLI bridge. Start the backend through an
+editor, not an interactive terminal: stdin/stdout carry DAP frames.
+
+## Launch Contract
+
+```json
+{
+  "type": "kedi",
+  "request": "launch",
+  "name": "Debug Kedi",
+  "program": "${file}",
+  "cwd": "${workspaceFolder}",
+  "args": [],
+  "env": {},
+  "stopOnEntry": true
+}
+```
+
+`adapter` and `model` optionally select the existing CLI runtime defaults;
+program/profile directives still follow normal Kedi rules. Before starting the
+worker or importing Kedi, the debugger finds the nearest `.env` starting at
+`cwd` and searching its parents. Without `cwd`, it starts at the program's
+directory. It loads one file, not a merge of every parent file. API keys and
+`KEDI_ADAPTER`, `KEDI_ADAPTER_MODEL`, and `MODEL_NAME` are available before model
+selection, including when the editor was opened outside a terminal.
+
+Launch `env` entries take priority over inherited environment variables, which
+take priority over `.env` values. Strings override values; null removes a
+variable even if `.env` defines it; an empty string remains an empty value.
+Dotenv quoting, multiline values, and `${NAME}` interpolation are supported.
+Explicit launch `adapter`/`model` fields take priority over environment defaults.
+Missing `.env` files are optional; unreadable or invalid files fail launch without
+printing their contents. The supervisor's own environment is never mutated.
+
+Set `PYTHON_DOTENV_DISABLED=1` in the inherited environment or launch `env` to
+skip dotenv discovery. After resolving the worker environment, the debugger sets
+this flag for the worker to prevent later `load_dotenv()` calls from finding a
+different file or restoring removed variables. Restart the debug session after
+changing `.env`. Known credentials from the loaded file are masked in debugger
+output and inspections. Keep credentials out of checked-in launch files.
+
+The selected interpreter launches both supervisor and worker; launch arguments
+cannot silently replace it.
+
+## Execution Controls
+
+- Breakpoints stop before executable Kedi statements. Unsupported locations and
+  conditional/log/hit-count breakpoints are rejected, not silently relocated.
+- Step into enters a Kedi procedure; next steps over it; step out reaches the
+  next boundary after it returns. Embedded Python blocks are opaque units.
+- Pause requests the next cooperative boundary. It cannot freeze an active
+  network call or arbitrary Python instruction.
+- Independent model jobs remain concurrent. A stop affects one lane and never
+  claims that every thread stopped. Continue normally releases paused lanes;
+  a single-thread request releases only the selected lane.
+  Stepping also resumes paused peers by default so a capture can receive its
+  result. Explicit single-thread stepping can wait for a paused producer; resume
+  that producer separately when needed.
+- Optional exception/event filters `model_input` and `model_result` expose the
+  prepared model input before its conversation transaction and its returned
+  result afterward. `exceptions` stops at raised Kedi execution boundaries.
+- Request assembly is observation-only inside a conversation transaction. The
+  `request` scope contains the actual assembled Kedi prompt/instructions/tool
+  names, not an invented provider wire payload. Available usage is observed, not
+  estimated. The `model_input` scope precedes request-transforming hooks.
+  Nested synchronous tool execution is also observation-only while the model
+  transaction owns its resources. A propagated tool failure can stop afterward,
+  once the transaction has released them. Provider failures from parallel model
+  jobs reach exception stops just like failures on the main lane.
+
+Pausing does not suspend external deadlines, undo effects, replay a request, or
+override tool approval. Interactive stdin and terminal approval prompts are not
+supported in the DAP worker. Existing noninteractive approval policies continue
+to apply; a denied tool is not automatically approved for debugging.
+
+## Read-only Inspection
+
+Native editor stack/scopes/variables show lexical locals, bounded closure scopes, globals, Python prelude
+values, recent model observations, and changes in captured values. Completed
+captures expose their already-published values, including typed fields, without
+calling `resolve()` or waiting. Pending/failed/cancelled captures remain explicit.
+Inspecting a result never makes another model or tool call. Unknown objects stay
+opaque rather than running their repr, properties, serializers, or iterators.
+
+Watch/evaluate accepts names and paths such as `answer`, `record.name`, and
+`items[0]`, restricted to already captured values. It cannot run Python, call
+functions, mutate state, or retrieve omitted/truncated values. Handles expire
+when their lane resumes. After outstanding jobs drain, a bounded final snapshot stays in the process until
+the editor disconnects; there is no persistent execution archive.
+
+When distinct dictionary keys have the same display name (for example `1` and
+`"1"`), watch evaluation rejects the ambiguous path instead of guessing. Inspect
+the displayed variables directly in that case.
+
+Snapshots bound items, depth, text length and encoded bytes. Limits and cycles
+are visible, not represented as complete values. Sensitive field names and known
+environment secrets are redacted, including source responses without shifting
+their line positions. Arbitrary user text can still contain unknown
+sensitive information; review before sharing screenshots or logs. There is no
+Logfire dependency or telemetry exporter configured by the debugger.
+
+Large containers cannot consume the slots reserved for later sibling bindings.
+Each scope has a separate item budget within the bounded stop snapshot; empty
+and scalar scopes have valid inspection references too. A truncated scope includes
+a `<snapshot>` notice so omitted bindings are not mistaken for missing program
+variables. Resolved promises display their memoized value, not a later replacement
+in the shared model-result mapping.
+
+## Restart and Run State
+
+Use the editor's **Restart/Rerun** action after saving source or `.env` changes.
+The adapter supports the DAP terminate/disconnect restart sequence: the editor
+launches a fresh adapter and worker, with fresh configuration and breakpoints.
+There is no in-place hot reload of an executing program. Attempting to continue
+after a source edit leaves execution paused and explains the required restart
+in the console.
+
+Thread names stay stable. Running/stopped state comes from DAP control events,
+not a cached suffix on the thread name. Clients supporting progress reporting
+receive balanced capture-wait progress events; already-completed captures do
+not report waiting. Completion ends outstanding progress and sends thread-exit
+events before the program's exit code and session termination.
+
+Statement stepping stops at the next eligible Kedi statement, not at each
+internal model observation on the same line. Explicit model event breakpoints
+continue to work. A statement is stopped **before** it executes, so a newly
+assigned value becomes visible at the following stop. On normal completion,
+editors may clear their Variables panel; inspect before continuing past the
+last breakpoint when you need to retain the view.
+
+## Boundaries
+
+Launch trusted saved `.kedi` files only. There is no remote attach, hot reload,
+reverse execution, arbitrary evaluate, Python-internal stepping, notebook/REPL
+debugging, terminal input, or subagent-internal async stepping. Synchronous
+observers on an asyncio loop are observation-only. Blocking unmanaged code may
+need worker termination; that does not imply rollback or graceful cleanup of
+remote services. Only the owned process group is terminated.
+
+Source snapshots are frozen for the session. Changed sources are rejected before
+configuration or resuming execution; restart to run an edited program. The actual
+compiled source is checked too, including imported Kedi modules.
+
+## Validation
+
+The runtime integration tests live in the parent
+[Kedi repository](https://github.com/kedi-lang/kedi/tree/stable/tests), not in
+this package checkout. From that repository's development environment:
+
+```sh
+python -m pytest tests/test_debugging.py tests/test_debugger_*.py
+```
+
+These tests use deterministic adapters and actual DAP subprocesses. They do not
+call Claude, other paid providers, or Terminal-Bench tasks. Editor extension
+builds/tests are separate from these backend tests; installing/publishing the
+extensions is a separate release step.
+
+Protocol reference: [DAP overview](https://microsoft.github.io/debug-adapter-protocol/overview).

kedi_debugger-0.1.0/README.md

@@ -0,0 +1,192 @@
+# Kedi Debugger
+
+An optional, local Debug Adapter Protocol (DAP) backend shared by the Kedi VS Code
+and Zed extensions. The protocol supervisor owns a separate Kedi worker process.
+The normal runtime does not import this package or record debugger snapshots.
+
+This package lives in [kedi-lang/kedi-debugger](https://github.com/kedi-lang/kedi-debugger)
+and is pinned as the `debugger/` submodule in the Kedi repository. From an existing
+Kedi checkout, initialize it with `git submodule update --init debugger`.
+
+## Local Installation
+
+The updated editor extensions automatically install this package in their shared
+managed environment, including upgrades of existing managed installations. This
+requires the matching runtime and debugger releases on the package index; source
+changes do not publish those releases.
+
+For local development or a selected host Python, use the same interpreter for
+the editor, Kedi, debugger, and program dependencies:
+
+```sh
+python -m pip install -e /path/to/kedi
+python -m pip install --no-deps -e /path/to/kedi/debugger
+python -c 'import kedi_debugger; from kedi.debugging import DebugEvent, observe_execution'
+```
+
+This source checkout adds runtime hooks that older Kedi installations do not have.
+The debugger and updated extensions have not been published automatically. A
+missing package is an installation error, not a reason to select another Python.
+Both extensions reuse the selected host interpreter or `~/.kedi/editor-venv`;
+neither creates a second debugger environment or modifies a host environment.
+
+The machine-facing entry point is `python -m kedi_debugger --stdio`.
+`kedi debug --stdio` is an equivalent CLI bridge. Start the backend through an
+editor, not an interactive terminal: stdin/stdout carry DAP frames.
+
+## Launch Contract
+
+```json
+{
+  "type": "kedi",
+  "request": "launch",
+  "name": "Debug Kedi",
+  "program": "${file}",
+  "cwd": "${workspaceFolder}",
+  "args": [],
+  "env": {},
+  "stopOnEntry": true
+}
+```
+
+`adapter` and `model` optionally select the existing CLI runtime defaults;
+program/profile directives still follow normal Kedi rules. Before starting the
+worker or importing Kedi, the debugger finds the nearest `.env` starting at
+`cwd` and searching its parents. Without `cwd`, it starts at the program's
+directory. It loads one file, not a merge of every parent file. API keys and
+`KEDI_ADAPTER`, `KEDI_ADAPTER_MODEL`, and `MODEL_NAME` are available before model
+selection, including when the editor was opened outside a terminal.
+
+Launch `env` entries take priority over inherited environment variables, which
+take priority over `.env` values. Strings override values; null removes a
+variable even if `.env` defines it; an empty string remains an empty value.
+Dotenv quoting, multiline values, and `${NAME}` interpolation are supported.
+Explicit launch `adapter`/`model` fields take priority over environment defaults.
+Missing `.env` files are optional; unreadable or invalid files fail launch without
+printing their contents. The supervisor's own environment is never mutated.
+
+Set `PYTHON_DOTENV_DISABLED=1` in the inherited environment or launch `env` to
+skip dotenv discovery. After resolving the worker environment, the debugger sets
+this flag for the worker to prevent later `load_dotenv()` calls from finding a
+different file or restoring removed variables. Restart the debug session after
+changing `.env`. Known credentials from the loaded file are masked in debugger
+output and inspections. Keep credentials out of checked-in launch files.
+
+The selected interpreter launches both supervisor and worker; launch arguments
+cannot silently replace it.
+
+## Execution Controls
+
+- Breakpoints stop before executable Kedi statements. Unsupported locations and
+  conditional/log/hit-count breakpoints are rejected, not silently relocated.
+- Step into enters a Kedi procedure; next steps over it; step out reaches the
+  next boundary after it returns. Embedded Python blocks are opaque units.
+- Pause requests the next cooperative boundary. It cannot freeze an active
+  network call or arbitrary Python instruction.
+- Independent model jobs remain concurrent. A stop affects one lane and never
+  claims that every thread stopped. Continue normally releases paused lanes;
+  a single-thread request releases only the selected lane.
+  Stepping also resumes paused peers by default so a capture can receive its
+  result. Explicit single-thread stepping can wait for a paused producer; resume
+  that producer separately when needed.
+- Optional exception/event filters `model_input` and `model_result` expose the
+  prepared model input before its conversation transaction and its returned
+  result afterward. `exceptions` stops at raised Kedi execution boundaries.
+- Request assembly is observation-only inside a conversation transaction. The
+  `request` scope contains the actual assembled Kedi prompt/instructions/tool
+  names, not an invented provider wire payload. Available usage is observed, not
+  estimated. The `model_input` scope precedes request-transforming hooks.
+  Nested synchronous tool execution is also observation-only while the model
+  transaction owns its resources. A propagated tool failure can stop afterward,
+  once the transaction has released them. Provider failures from parallel model
+  jobs reach exception stops just like failures on the main lane.
+
+Pausing does not suspend external deadlines, undo effects, replay a request, or
+override tool approval. Interactive stdin and terminal approval prompts are not
+supported in the DAP worker. Existing noninteractive approval policies continue
+to apply; a denied tool is not automatically approved for debugging.
+
+## Read-only Inspection
+
+Native editor stack/scopes/variables show lexical locals, bounded closure scopes, globals, Python prelude
+values, recent model observations, and changes in captured values. Completed
+captures expose their already-published values, including typed fields, without
+calling `resolve()` or waiting. Pending/failed/cancelled captures remain explicit.
+Inspecting a result never makes another model or tool call. Unknown objects stay
+opaque rather than running their repr, properties, serializers, or iterators.
+
+Watch/evaluate accepts names and paths such as `answer`, `record.name`, and
+`items[0]`, restricted to already captured values. It cannot run Python, call
+functions, mutate state, or retrieve omitted/truncated values. Handles expire
+when their lane resumes. After outstanding jobs drain, a bounded final snapshot stays in the process until
+the editor disconnects; there is no persistent execution archive.
+
+When distinct dictionary keys have the same display name (for example `1` and
+`"1"`), watch evaluation rejects the ambiguous path instead of guessing. Inspect
+the displayed variables directly in that case.
+
+Snapshots bound items, depth, text length and encoded bytes. Limits and cycles
+are visible, not represented as complete values. Sensitive field names and known
+environment secrets are redacted, including source responses without shifting
+their line positions. Arbitrary user text can still contain unknown
+sensitive information; review before sharing screenshots or logs. There is no
+Logfire dependency or telemetry exporter configured by the debugger.
+
+Large containers cannot consume the slots reserved for later sibling bindings.
+Each scope has a separate item budget within the bounded stop snapshot; empty
+and scalar scopes have valid inspection references too. A truncated scope includes
+a `<snapshot>` notice so omitted bindings are not mistaken for missing program
+variables. Resolved promises display their memoized value, not a later replacement
+in the shared model-result mapping.
+
+## Restart and Run State
+
+Use the editor's **Restart/Rerun** action after saving source or `.env` changes.
+The adapter supports the DAP terminate/disconnect restart sequence: the editor
+launches a fresh adapter and worker, with fresh configuration and breakpoints.
+There is no in-place hot reload of an executing program. Attempting to continue
+after a source edit leaves execution paused and explains the required restart
+in the console.
+
+Thread names stay stable. Running/stopped state comes from DAP control events,
+not a cached suffix on the thread name. Clients supporting progress reporting
+receive balanced capture-wait progress events; already-completed captures do
+not report waiting. Completion ends outstanding progress and sends thread-exit
+events before the program's exit code and session termination.
+
+Statement stepping stops at the next eligible Kedi statement, not at each
+internal model observation on the same line. Explicit model event breakpoints
+continue to work. A statement is stopped **before** it executes, so a newly
+assigned value becomes visible at the following stop. On normal completion,
+editors may clear their Variables panel; inspect before continuing past the
+last breakpoint when you need to retain the view.
+
+## Boundaries
+
+Launch trusted saved `.kedi` files only. There is no remote attach, hot reload,
+reverse execution, arbitrary evaluate, Python-internal stepping, notebook/REPL
+debugging, terminal input, or subagent-internal async stepping. Synchronous
+observers on an asyncio loop are observation-only. Blocking unmanaged code may
+need worker termination; that does not imply rollback or graceful cleanup of
+remote services. Only the owned process group is terminated.
+
+Source snapshots are frozen for the session. Changed sources are rejected before
+configuration or resuming execution; restart to run an edited program. The actual
+compiled source is checked too, including imported Kedi modules.
+
+## Validation
+
+The runtime integration tests live in the parent
+[Kedi repository](https://github.com/kedi-lang/kedi/tree/stable/tests), not in
+this package checkout. From that repository's development environment:
+
+```sh
+python -m pytest tests/test_debugging.py tests/test_debugger_*.py
+```
+
+These tests use deterministic adapters and actual DAP subprocesses. They do not
+call Claude, other paid providers, or Terminal-Bench tasks. Editor extension
+builds/tests are separate from these backend tests; installing/publishing the
+extensions is a separate release step.
+
+Protocol reference: [DAP overview](https://microsoft.github.io/debug-adapter-protocol/overview).

kedi_debugger-0.1.0/pyproject.toml

@@ -0,0 +1,31 @@
+[build-system]
+requires = ["hatchling==1.32.0"]
+build-backend = "hatchling.build"
+
+[project]
+name = "kedi-debugger"
+version = "0.1.0"
+description = "Optional stdio Debug Adapter Protocol backend for Kedi"
+readme = "README.md"
+requires-python = ">=3.11"
+license = {text = "Apache-2.0"}
+dependencies = ["kedi>=0.1.1,<0.2", "python-dotenv>=1.2.2,<2"]
+
+[project.scripts]
+kedi-debugger = "kedi_debugger.__main__:main"
+
+[project.urls]
+Documentation = "https://docs.kedi-lang.org/tooling/debugger/"
+Source = "https://github.com/kedi-lang/kedi-debugger"
+Tracker = "https://github.com/kedi-lang/kedi-debugger/issues"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/kedi_debugger"]
+
+[tool.ruff]
+line-length = 100
+target-version = "py311"
+
+[tool.ruff.lint]
+# Ruff 0.17 widened its default rule set; keep the rules this project was linted with.
+select = ["E4", "E7", "E9", "F"]

kedi_debugger-0.1.0/src/kedi_debugger/__init__.py

@@ -0,0 +1,7 @@
+"""Optional Kedi debugger. Importing the transport does not load the runtime."""
+
+from __future__ import annotations
+
+__version__ = "0.1.0"
+
+__all__ = ["__version__"]