c64-mcp 0.99.0__tar.gz

c64_mcp-0.99.0/.gitignore

@@ -0,0 +1,8 @@
+.venv/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+__pycache__/
+dist/
+build/
+*.egg-info/

c64_mcp-0.99.0/AGENTS.md

@@ -0,0 +1,11 @@
+# AGENTS.md
+
+- Never use conventional-commit prefixes (`feat/`, …) in commit titles or branch names
+
+## Releasing
+
+- **Do not write tests for the release script.** No unit tests, no fixtures, no
+  mutation checks, no CI assertions about it. Releasing is verified by running
+  `tools/release <major|minor|patch>` and seeing what happens; a test suite around
+  it has repeatedly cost more than it caught. If a release breaks, fix the script.
+- This is a standing instruction from the maintainer, not an oversight to correct.

c64_mcp-0.99.0/CHANGELOG.md

@@ -0,0 +1,64 @@
+# Changelog
+
+## Unreleased
+
+### Changed
+
+- Renamed the project from `ghidra-mcp-c64` to `c64-mcp`, and the Python package
+  from `ghidra_mcp_c64` to `c64_mcp`. The old name implied a sibling of
+  `ghidra-mcp-next`; this is not a Ghidra extension and contains no Java. It is an
+  MCP server that reaches Ghidra over HTTP and VICE through the connector's
+  TraceRMI contract, and roughly half of it — the PETSCII and screen-code tables,
+  the C64 symbol profile, the tool-visibility profiles — needs neither.
+  **The console script is now `c64-mcp`**: update the `command` in any `.mcp.json`
+  and re-sync the virtualenv, which otherwise keeps the old script.
+
+### Added
+
+- Added `tools/release <major|minor|patch>`, a single command that refuses unless
+  the checkout is on the default branch, clean and exactly in sync with origin,
+  then writes the version to `pyproject.toml`, regenerates `uv.lock`, rolls the
+  changelog, runs the gates through `uv run --locked` against that candidate,
+  builds, commits, tags and pushes. There is deliberately no publishing step:
+  nothing consumes a c64 release, and its compatibility with the connector rests
+  on the `c64.vice/1` runtime handshake rather than on matching versions.
+  Everything that can fail runs before the push, since the push cannot be undone;
+  until then a failure restores the working tree, the index and the branch ref.
+
+### Changed
+
+- Version moves to `0.99.0`. `__version__` is now derived from installed package
+  metadata rather than duplicated as a literal, so it cannot drift from
+  `pyproject.toml`.
+- Dropped `connector.version` from the packaged `c64-vice-api-v1.json`, matching
+  the connector: it is release metadata rather than part of the `c64.vice/1`
+  compatibility surface, and keeping it required a coordinated commit here on
+  every connector release. The runtime `connector_version` from `status` is
+  unaffected.
+
+### Added
+
+- `minimal`, `static`, `vice`, and `full` tool-visibility profiles with
+  runtime group listing, search, load, and unload tools.
+- Initial standalone package scaffold.
+- Immutable, source-cited 256-entry PETSCII and C64 screen-code tables for
+  both C64 character-set modes.
+- Lossless bounded PETSCII/screen-code decoding with fixed, terminated, and
+  length-prefixed sources, high-bit policies, control rendering, and
+  caller-owned token expansion.
+- `decode_c64_text`, `search_c64_text`, and dry-run-first
+  `define_c64_text` MCP tools over the public Ghidra HTTP boundary.
+- A versioned, source-attributed C64 profile covering VIC-II, SID, CIA,
+  KERNAL, vectors, workspace, control-bit equates, and opt-in memory
+  templates.
+- `get_c64_symbol_profile` and dry-run-first
+  `apply_c64_symbol_profile` MCP tools.
+- A strict packaged `c64.vice/1` connector contract and race-safe local
+  binding keyed by the Ghidra target token and connector instance ID.
+- Complete `vice_*` tools for connector-owned registers, banks, memory,
+  checkpoints, execution, stop waits, reset, and cached session status.
+- Dry-run-first `copy_vice_memory_to_ghidra`, with one complete VICE read,
+  SHA-256 verification, exactly one generic program write, and no payload
+  echo.
+- Distinct connector, generic TraceRMI, and HTTP timeout reporting with
+  operation-specific uncertainty flags and no automatic retries.

c64_mcp-0.99.0/LICENSE

@@ -0,0 +1,190 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   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
+
+   Copyright 2026 Saverio Proto
+
+   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.

c64_mcp-0.99.0/NOTICE

@@ -0,0 +1,16 @@
+c64-mcp
+Copyright 2026 Saverio Proto
+
+This product includes C64-specific interoperability data whose individual
+source attributions are recorded with the bundled profile and codec tables.
+
+The bundled PETSCII and screen-code tables are transcribed from Appendices B
+and C of the Commodore 64 Programmer's Reference Guide, published by
+Commodore Business Machines, Inc. The package data records the source URL and
+printed page references.
+
+The bundled C64 symbol profile is transcribed and normalized from the
+Commodore 64 Programmer's Reference Guide and Service Manual and the
+MOS/Commodore 6581 SID and 6526 CIA data sheets. The generated package data
+records the source title, relevant section or page range, and URL for every
+symbol group.

c64_mcp-0.99.0/PKG-INFO

@@ -0,0 +1,133 @@
+Metadata-Version: 2.4
+Name: c64-mcp
+Version: 0.99.0
+Summary: C64-specific MCP tools for Ghidra and the Ghidra VICE connector
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Requires-Python: >=3.10
+Requires-Dist: mcp==1.28.1
+Description-Content-Type: text/markdown
+
+# c64-mcp
+
+C64-specific MCP tools layered over the public `ghidra-mcp` HTTP API and the
+separately installed Ghidra VICE connector.
+
+The server uses stdio transport by default. It does not open a VICE binary
+monitor socket; the connector remains the sole owner of that connection.
+
+## Tool visibility
+
+The default `static` profile exposes the symbol and text groups plus four
+small catalog-management tools. This keeps live-debugger schemas out of the
+agent context until they are needed. `minimal` starts with management tools
+only, `vice` starts with the live-debugger group, and `full` exposes every
+tool.
+
+Use `list_c64_tool_groups`, `search_c64_tools`, and
+`load_c64_tool_group` to discover and expose hidden tools at runtime.
+`unload_c64_tool_group` removes only groups loaded after startup; profile
+baseline groups remain visible. Thus `static` followed by loading `all`
+still permits unloading the transient VICE group, while the `full` profile
+does not permit partial unloading.
+
+## VICE debugger tools
+
+The `vice_*` tools bind to the active **VICE C64 Debugger** TraceRMI target
+through the generic Ghidra MCP HTTP API. Install and launch the separately
+released `ghidra-vice-connector` first, then call `vice_connect`. The handshake
+checks the complete versioned `c64.vice/1` method schema, capability set,
+machine, limits, and immutable connector instance ID. Compatibility is based
+on that runtime contract rather than an assumed package-version pairing.
+
+The tool set covers cached status, dynamic registers and banks, bank-aware
+memory, checkpoints, execution control, stop-event waits, and reset.
+`vice_disconnect` releases only this MCP process's local binding; it never
+closes the connector socket, trace, or VICE process. `vice_status` is cached
+and performs no discovery or network operation.
+
+`copy_vice_memory_to_ghidra` is the only implicit bridge from live VICE memory
+to a static program. It performs one complete connector read, verifies the
+exact byte count, computes SHA-256, and calls the generic
+`write_memory_bytes` endpoint exactly once. It defaults to `dry_run=true` and
+never returns the complete payload. It does not create memory blocks or
+disassemble.
+
+Connector, generic target-method, and HTTP timeouts remain distinguishable.
+Mutating timeout responses explicitly say which VICE or Ghidra state may have
+changed, and no timed-out operation is retried automatically. The C64 MCP
+contains no VICE monitor host, port, socket, or binary protocol fallback.
+
+## C64 symbol profile
+
+`get_c64_symbol_profile` returns the bundled, versioned C64 platform profile.
+`apply_c64_symbol_profile` applies that exact profile to an explicitly named
+Ghidra program through the generic `apply_symbol_profile` endpoint. It
+defaults to `dry_run=true`, `conflict_policy=error`, and memory-block creation
+disabled. Re-applying an unchanged profile is idempotent.
+
+The profile covers the 6510 processor port, all VIC-II and SID registers,
+both CIA devices, color RAM, the 39 standard KERNAL jump-table entry points,
+processor vectors, and common KERNAL workspace addresses. Value-only equates
+name documented VIC-II, SID, and CIA control bits. Optional RAM, ROM, I/O,
+and color-RAM block templates are only considered when
+`create_memory_blocks=true`; the generic endpoint preflights the complete
+request before mutation and refuses ordinary-block overlap.
+
+The checked-in profile is generated deterministically by
+`tools/generate_c64_profile.py`. Every symbol group cites its authoritative
+Commodore manual or chip data sheet in the package data.
+
+## C64 text tools
+
+The server includes immutable 256-entry mappings for upper/graphics and
+lower/upper PETSCII and C64 screen codes:
+
+- `decode_c64_text` decodes inline hex/byte arrays or an exact bounded read
+  from a named Ghidra program.
+- `search_c64_text` searches an inclusive program range by exact raw bytes or
+  exact decoded Unicode code points.
+- `define_c64_text` decodes first, then sends one flat contiguous region to
+  Ghidra with byte typing, an optional label/namespace, and a complete plate
+  comment. It defaults to `dry_run=true`.
+
+Every decode uses exactly one of a positive fixed `length`, a one-byte
+`terminator`, or a one/two-byte little-endian `prefix_size`. Terminators are
+consumed but excluded from text. Prefixes are consumed and excluded from
+text, and may either describe payload length or include themselves.
+
+`high_bit` accepts `exact`, `strip`, or `annotate_reverse`; the latter is
+screen-code-only. `controls` accepts `names`, `escaped`, or `unicode`.
+Lossless payload output retains every original text byte as a stable fragment
+such as `{A:$41}`, `{CLR:$93}`, or `{REV A:$81}`. Prefix and terminator bytes
+remain available in `consumed_bytes` and the per-byte records even though
+framing bytes are excluded from both decoded text renderings.
+
+Caller token maps use unprefixed decimal keys (`"129"`) or explicitly
+hexadecimal keys (`"0x81"`). Expansion is single-pass by default. Recursive
+mode recognizes two-digit hexadecimal references such as `{81}`, enforces a
+caller-selected depth, detects cycles, and fails rather than truncating when
+the aggregate rendering cap is exceeded.
+
+All reads and inline inputs have a 1 MiB hard cap. Search defaults to 64 KiB
+and 100 results, with hard caps of 1 MiB and 1,000 results. Ghidra reads must
+be complete; partial or unmapped reads are errors.
+
+The normative mapping source is Appendices B and C of the official
+*Commodore 64 Programmer's Reference Guide*. The generated package data
+records the source URL and printed page references.
+
+## Configuration
+
+- `GHIDRA_MCP_URL` defaults to `http://127.0.0.1:8089`.
+- `GHIDRA_MCP_AUTH_TOKEN` optionally supplies a bearer token.
+- `GHIDRA_MCP_TIMEOUT` defaults to 30 seconds.
+- `GHIDRA_MCP_C64_TOOL_PROFILE` accepts `minimal`, `static`, `vice`, or
+  `full`; the default is `static`.
+
+The `--tool-profile` command-line option overrides the environment setting.
+
+VICE method calls accept a caller-visible `timeout_ms` from 1 through 55,000.
+The wrapper reserves an additional five seconds for generic TraceRMI
+invocation and another five seconds for HTTP transport.

c64_mcp-0.99.0/README.md

@@ -0,0 +1,122 @@
+# c64-mcp
+
+C64-specific MCP tools layered over the public `ghidra-mcp` HTTP API and the
+separately installed Ghidra VICE connector.
+
+The server uses stdio transport by default. It does not open a VICE binary
+monitor socket; the connector remains the sole owner of that connection.
+
+## Tool visibility
+
+The default `static` profile exposes the symbol and text groups plus four
+small catalog-management tools. This keeps live-debugger schemas out of the
+agent context until they are needed. `minimal` starts with management tools
+only, `vice` starts with the live-debugger group, and `full` exposes every
+tool.
+
+Use `list_c64_tool_groups`, `search_c64_tools`, and
+`load_c64_tool_group` to discover and expose hidden tools at runtime.
+`unload_c64_tool_group` removes only groups loaded after startup; profile
+baseline groups remain visible. Thus `static` followed by loading `all`
+still permits unloading the transient VICE group, while the `full` profile
+does not permit partial unloading.
+
+## VICE debugger tools
+
+The `vice_*` tools bind to the active **VICE C64 Debugger** TraceRMI target
+through the generic Ghidra MCP HTTP API. Install and launch the separately
+released `ghidra-vice-connector` first, then call `vice_connect`. The handshake
+checks the complete versioned `c64.vice/1` method schema, capability set,
+machine, limits, and immutable connector instance ID. Compatibility is based
+on that runtime contract rather than an assumed package-version pairing.
+
+The tool set covers cached status, dynamic registers and banks, bank-aware
+memory, checkpoints, execution control, stop-event waits, and reset.
+`vice_disconnect` releases only this MCP process's local binding; it never
+closes the connector socket, trace, or VICE process. `vice_status` is cached
+and performs no discovery or network operation.
+
+`copy_vice_memory_to_ghidra` is the only implicit bridge from live VICE memory
+to a static program. It performs one complete connector read, verifies the
+exact byte count, computes SHA-256, and calls the generic
+`write_memory_bytes` endpoint exactly once. It defaults to `dry_run=true` and
+never returns the complete payload. It does not create memory blocks or
+disassemble.
+
+Connector, generic target-method, and HTTP timeouts remain distinguishable.
+Mutating timeout responses explicitly say which VICE or Ghidra state may have
+changed, and no timed-out operation is retried automatically. The C64 MCP
+contains no VICE monitor host, port, socket, or binary protocol fallback.
+
+## C64 symbol profile
+
+`get_c64_symbol_profile` returns the bundled, versioned C64 platform profile.
+`apply_c64_symbol_profile` applies that exact profile to an explicitly named
+Ghidra program through the generic `apply_symbol_profile` endpoint. It
+defaults to `dry_run=true`, `conflict_policy=error`, and memory-block creation
+disabled. Re-applying an unchanged profile is idempotent.
+
+The profile covers the 6510 processor port, all VIC-II and SID registers,
+both CIA devices, color RAM, the 39 standard KERNAL jump-table entry points,
+processor vectors, and common KERNAL workspace addresses. Value-only equates
+name documented VIC-II, SID, and CIA control bits. Optional RAM, ROM, I/O,
+and color-RAM block templates are only considered when
+`create_memory_blocks=true`; the generic endpoint preflights the complete
+request before mutation and refuses ordinary-block overlap.
+
+The checked-in profile is generated deterministically by
+`tools/generate_c64_profile.py`. Every symbol group cites its authoritative
+Commodore manual or chip data sheet in the package data.
+
+## C64 text tools
+
+The server includes immutable 256-entry mappings for upper/graphics and
+lower/upper PETSCII and C64 screen codes:
+
+- `decode_c64_text` decodes inline hex/byte arrays or an exact bounded read
+  from a named Ghidra program.
+- `search_c64_text` searches an inclusive program range by exact raw bytes or
+  exact decoded Unicode code points.
+- `define_c64_text` decodes first, then sends one flat contiguous region to
+  Ghidra with byte typing, an optional label/namespace, and a complete plate
+  comment. It defaults to `dry_run=true`.
+
+Every decode uses exactly one of a positive fixed `length`, a one-byte
+`terminator`, or a one/two-byte little-endian `prefix_size`. Terminators are
+consumed but excluded from text. Prefixes are consumed and excluded from
+text, and may either describe payload length or include themselves.
+
+`high_bit` accepts `exact`, `strip`, or `annotate_reverse`; the latter is
+screen-code-only. `controls` accepts `names`, `escaped`, or `unicode`.
+Lossless payload output retains every original text byte as a stable fragment
+such as `{A:$41}`, `{CLR:$93}`, or `{REV A:$81}`. Prefix and terminator bytes
+remain available in `consumed_bytes` and the per-byte records even though
+framing bytes are excluded from both decoded text renderings.
+
+Caller token maps use unprefixed decimal keys (`"129"`) or explicitly
+hexadecimal keys (`"0x81"`). Expansion is single-pass by default. Recursive
+mode recognizes two-digit hexadecimal references such as `{81}`, enforces a
+caller-selected depth, detects cycles, and fails rather than truncating when
+the aggregate rendering cap is exceeded.
+
+All reads and inline inputs have a 1 MiB hard cap. Search defaults to 64 KiB
+and 100 results, with hard caps of 1 MiB and 1,000 results. Ghidra reads must
+be complete; partial or unmapped reads are errors.
+
+The normative mapping source is Appendices B and C of the official
+*Commodore 64 Programmer's Reference Guide*. The generated package data
+records the source URL and printed page references.
+
+## Configuration
+
+- `GHIDRA_MCP_URL` defaults to `http://127.0.0.1:8089`.
+- `GHIDRA_MCP_AUTH_TOKEN` optionally supplies a bearer token.
+- `GHIDRA_MCP_TIMEOUT` defaults to 30 seconds.
+- `GHIDRA_MCP_C64_TOOL_PROFILE` accepts `minimal`, `static`, `vice`, or
+  `full`; the default is `static`.
+
+The `--tool-profile` command-line option overrides the environment setting.
+
+VICE method calls accept a caller-visible `timeout_ms` from 1 through 55,000.
+The wrapper reserves an additional five seconds for generic TraceRMI
+invocation and another five seconds for HTTP transport.