mainframe-modernization-toolkit 0.1.0__tar.gz

mainframe_modernization_toolkit-0.1.0/CHANGELOG.md

@@ -0,0 +1,9 @@
+# Changelog
+
+All notable changes to this project are documented in this file.
+
+## 0.1.0 - 2026-08-18
+
+- Initial Python package with 17 deterministic migration CLIs and the `mainframe-toolkit` umbrella command.
+- Bundled standalone VS Code extension and language server.
+- Added workspace templates, schemas, VSIX export/verification, and release validation.

mainframe_modernization_toolkit-0.1.0/LICENSE

@@ -0,0 +1,175 @@
+
+                                 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.

mainframe_modernization_toolkit-0.1.0/MANIFEST.in

@@ -0,0 +1,14 @@
+include LICENSE
+include CHANGELOG.md
+include THIRD_PARTY_NOTICES.md
+include README.md
+recursive-include src/mainframe_modernization_toolkit/resources *
+recursive-include scripts *.py
+prune carddemo-conversion-examples
+prune test-fixtures
+prune tests
+prune extension
+prune server
+prune docs
+prune .github
+global-exclude __pycache__ *.py[cod] .DS_Store .env .env.*

mainframe_modernization_toolkit-0.1.0/PKG-INFO

@@ -0,0 +1,311 @@
+Metadata-Version: 2.4
+Name: mainframe-modernization-toolkit
+Version: 0.1.0
+Summary: Deterministic COBOL/JCL analysis and mainframe modernization tooling
+Author: Mainframe Migration Toolkit Contributors
+License-Expression: Apache-2.0
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Code Generators
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: release
+Requires-Dist: build>=1.2; extra == "release"
+Requires-Dist: twine>=6; extra == "release"
+Dynamic: license-file
+
+# Mainframe Migration Toolkit - COBOL/JCL -> Python/SQL
+
+A VS Code extension + language server + CLI toolkit that gives an AI
+coding agent (GitHub Copilot in agent mode) **deterministic** navigation
+of a legacy COBOL/JCL codebase's dependencies (CALL/COPY/EXEC), and a set
+of scripts that automate the mechanical, low-risk parts of migrating that
+codebase to Python and SQL.
+
+This project intentionally does not try to auto-translate COBOL business
+logic into Python - see [docs/RESEARCH.md](docs/RESEARCH.md) for why that
+approach is unsafe for financial-grade code, and what large migration
+programs do instead.
+
+## Why "deterministic"?
+
+LLMs are good at reading and writing code, but bad at reliably tracing
+"what calls what" across thousands of files inside a limited context
+window - and a hallucinated dependency edge in a mainframe migration can
+mean a silent production regression. Every tool here is a plain parser or
+graph traversal: same input always produces the same output, with no
+model involved. The AI agent's job is to *call* these tools and reason
+over their output, not to re-derive the graph itself.
+
+## How edge cases are handled
+
+No regex-based parser can understand 100% of real-world COBOL/JCL. When
+a tool hits something it can't safely resolve - an unresolved CALL/COPY
+target, a dynamic `CALL WS-VAR`, `EXEC CICS`/`IMS` blocks, `OCCURS ...
+DEPENDING ON` variable-length tables, an unterminated `EXEC SQL` block,
+a missing `PROGRAM-ID`, `GO TO` control flow, an edited/floating-point
+PIC clause, a qualified/indicator SQL host variable, a JCL backward
+reference to a nonexistent step, etc. - it **never guesses**. Instead it
+emits a structured warning (`code`, `severity`, `message`,
+`suggested_action`, `file`, `line`, `snippet`) defined once in
+[scripts/common/warnings_model.py](scripts/common/warnings_model.py) /
+[server/src/warningsModel.ts](server/src/warningsModel.ts), and every
+tool surfaces it:
+
+- Immediately supplyable missing prerequisites produce `BLOCK` and stop
+  the affected file generation before outputs are written. Semantic
+  decisions produce configurable code-local
+  `TODO(mainframe-migration): [CODE] explanation / required decision`
+  markers while unaffected units continue.
+- The language server reports the same facts as editor diagnostics on
+  the offending line, and via the `mainframe/warnings` custom LSP
+  request (also folded into `mainframe/dependencyGraph` and
+  `mainframe/impactAnalysis` results).
+- Known IBM/vendor utility programs (`IEFBR14`, `SORT`, `IDCAMS`, ...)
+  and system copybooks (`SQLCA`, `DFHCOMMAREA`, ...) are allowlisted so
+  real findings aren't buried in expected noise.
+
+See [test-fixtures/edge-cases/](test-fixtures/edge-cases) for a fixture
+per edge case, used to regression-test this behavior.
+
+## Repository layout
+
+```
+extension/        VS Code extension: starts the language server and
+                   registers 5 vscode.lm Language Model Tools for Copilot
+                   agent mode (see extension/package.json
+                   "languageModelTools").
+server/           Deterministic COBOL/JCL language server
+                   (vscode-languageserver, TypeScript). Provides go-to-
+                   definition & hover for CALL/COPY/EXEC PGM=, diagnostics
+                   for unresolved targets, and custom LSP requests
+                   (mainframe/dependencyGraph, mainframe/impactAnalysis,
+                   mainframe/callers, mainframe/resolveCopybook) that back
+                   the extension's LM tools.
+scripts/          17 standalone Python CLI tools for migration planning and
+                   scaffolding (see below). No dependencies beyond the
+                   Python 3 standard library.
+scripts/common/   Shared deterministic COBOL/JCL parsing + workspace
+                   indexing code used by every script (and conceptually
+                   mirrored in server/src/*.ts for the LSP).
+test-fixtures/    An original, small "bank batch" COBOL/JCL system used to
+                   exercise every tool end-to-end (see
+                   test-fixtures/README.md for its call/copy graph).
+docs/RESEARCH.md  Research on migration strategies used by large players,
+                   and which tool here implements each one.
+```
+
+## Configuration and preflight
+
+Use a workspace-relative `mainframe-migration.json` to define ordered
+primary/fallback COBOL, copybook, and JCL libraries. The schema is
+[mainframe-migration.schema.json](mainframe-migration.schema.json), and
+[test-fixtures/mainframe-migration.json](test-fixtures/mainframe-migration.json)
+is a complete example that intentionally includes `edge-cases/` as a
+fallback library.
+
+`mainframe-migration.json` is authoritative for paths, ordered primary and
+fallback libraries, source encoding, extensions, external registries, the
+generated TODO prefix, and optional named `transportProfiles`. A transport
+profile defines fixed-width text charset, line separator, trim policy, and the
+representation of DISPLAY, COMP-3, BINARY/COMP-4, COMP-1, and COMP-2 fields.
+Old configs remain valid, but contract/fixture generation requires an explicit
+profile or `defaultTransportProfile`.
+
+Physical copybook layout and transported text layout are separate contracts.
+For example, a six-byte packed COMP-3 value can become 13 text characters
+(precision digits, decimal point, and sign) without changing its source offset
+or physical length. Expanded decimal width is precision plus an explicit
+decimal point when scale is non-zero plus one sign character when signed;
+expanded integer width is precision plus one sign character when signed.
+
+Run mandatory phase-zero preflight before generating migration output:
+
+```bash
+python3 scripts/migration_preflight.py test-fixtures --jcl BANKRUN --format text
+python3 scripts/migration_preflight.py test-fixtures --format json
+```
+
+Preflight exits `0` when there are no `BLOCK` findings and `2` when a
+human-suppliable fact is missing or ambiguous. Dynamic calls, transaction
+dialects, ODO, `REDEFINES`, edited PICs, and qualified SQL hosts become
+explicit `TODO` findings and do not stop unrelated analysis. Generate a
+starter file with `--write-template`. Present the initial report grouped by
+`user_can_supply=true` and then `false`. Resolution order is fixed: current
+LSP facts, configured primary libraries, configured fallback libraries,
+then verified known externals; exhaustion blocks and requires user input.
+Automated migration repair is capped at 50 total failed attempts.
+
+Configuration-aware CLIs accept `--config`. For single-file CLIs, the selected file must
+exist, match its configured kind, and belong to the selected inventory.
+Omitting config retains legacy behavior.
+
+## Pinned CardDemo validation
+
+Run the parsed phase-3 scenarios against the exact pinned AWS CardDemo revision
+with one command (the runner clones/caches and verifies the detached commit):
+
+```bash
+python3 tests/run_carddemo_scenarios.py
+```
+
+The assertions, observed results, known fixes, and residual TODOs are recorded in
+[`docs/research-carddemo-validation.md`](docs/research-carddemo-validation.md).
+
+## The 17 tools
+
+| Tool | What it answers |
+|------|------------------|
+| [`scripts/migration_preflight.py`](scripts/migration_preflight.py) | Validates configured source inventory, precedence, static dependencies, and migration blockers before generation |
+| [`scripts/dependency_graph.py`](scripts/dependency_graph.py) | "What calls/copies/executes what across the whole codebase?" (JSON/DOT/text) |
+| [`scripts/impact_analysis.py`](scripts/impact_analysis.py) | "If I change X, what breaks?" (transitive upstream/downstream + risk) |
+| [`scripts/dead_code_finder.py`](scripts/dead_code_finder.py) | "Which programs/copybooks are never referenced?" |
+| [`scripts/sql_extractor.py`](scripts/sql_extractor.py) | Pulls embedded `EXEC SQL` out of COBOL into standalone, bind-parameterized `.sql` files |
+| [`scripts/business_rule_extractor.py`](scripts/business_rule_extractor.py) | Mines IF/EVALUATE decision logic (+ preceding comments) into a reviewable rule list |
+| [`scripts/copybook_to_dataclass.py`](scripts/copybook_to_dataclass.py) | Copybook PIC layout -> Python `@dataclass` and/or SQL `CREATE TABLE` |
+| [`scripts/copybook_to_contract.py`](scripts/copybook_to_contract.py) | Copybook physical offsets + selected transport profile -> canonical language-neutral JSON record contract with digest, provenance, and structured TODO/BLOCK findings |
+| [`scripts/generate_copybook_fixtures.py`](scripts/generate_copybook_fixtures.py) | Canonical contract or configured copybook -> deterministic seeded fixed-width input, decoded JSONL, invalid decode cases, and a non-authoritative manifest for ingestion testing only |
+| [`scripts/generate_file_readers.py`](scripts/generate_file_readers.py) | FILE-CONTROL/FD/COPY -> standalone `domain/model` dataclasses and binary-safe fixed-width readers; missing copybooks block writes while semantic layout decisions remain explicit TODO stubs |
+| [`scripts/cobol_to_python_skeleton.py`](scripts/cobol_to_python_skeleton.py) | COBOL paragraph structure -> Python class skeleton (structure preserved, logic left as TODOs) |
+| [`scripts/jcl_flow_extractor.py`](scripts/jcl_flow_extractor.py) | JCL step/COND flow -> explicit orchestration description or Python skeleton |
+| [`scripts/migration_complexity_report.py`](scripts/migration_complexity_report.py) | Ranks every program by migration effort/risk into a wave plan |
+| [`scripts/characterization_test_scaffolder.py`](scripts/characterization_test_scaffolder.py) | Generates a golden-master pytest harness from a program's LINKAGE SECTION contract |
+| [`scripts/generate_program_capsule.py`](scripts/generate_program_capsule.py) | Runs selected-JCL preflight, then creates per-program/utility PARTIAL capsules with deterministic DD/I/O evidence, contract copies, explicit semantic TODO IR, placeholder source/tests, and exact paths/commands; any preflight BLOCK writes nothing |
+| [`scripts/validate_relational_ir.py`](scripts/validate_relational_ir.py) | Pure-stdlib typed validation for relational IR v1; exits `0` only for executable reviewed plans, `2` for BLOCK, and `3` for TODO/non-executable |
+| [`scripts/ir_to_pyspark.py`](scripts/ir_to_pyspark.py) | Deterministically compiles validated executable IR to native PySpark source with `run(inputs, outputs, spark)` and refuses BLOCK/TODO plans before writing |
+
+Every script is runnable standalone:
+
+```bash
+python3 scripts/dependency_graph.py test-fixtures --format text
+python3 scripts/copybook_to_contract.py test-fixtures/copybooks/TRANREC.cpy --config test-fixtures/mainframe-migration.json --out TRANREC.contract.json
+python3 scripts/generate_copybook_fixtures.py TRANREC.contract.json --out-dir synthetic/TRANREC --count 6 --seed 41 --include-invalid
+python3 scripts/generate_file_readers.py test-fixtures --out-dir domain
+python3 scripts/generate_program_capsule.py test-fixtures --jcl BANKRUN --out-dir migration/BANKRUN/capsules --format text
+python3 scripts/validate_relational_ir.py migration/BANKRUN/capsules/mainpgm/ir/plan.scaffold.json --format text
+```
+
+[`relational-ir.schema.json`](relational-ir.schema.json) defines the portable
+relational plan format. An AI may author the semantic operations only after the
+program semantic brief and target design review are approved. The validator and
+PySpark compiler are deterministic; they do not infer missing types or business
+rules. A generated program capsule is intentionally `PARTIAL`, contains an
+explicit semantic `TODO`, and is not a translated or equivalent implementation.
+
+The generated readers open files in binary mode so `COMP-3`, `COMP-4`/
+`BINARY`, and DISPLAY fields retain their physical COBOL representation.
+Each malformed line yields a structured `RecordParseError` by default;
+valid records continue streaming. Missing copybooks block before package
+creation; semantic or unsafe layout decisions generate an empty dataclass
+and reader stub with a standardized TODO instead of a guessed layout.
+
+Synthetic fixture output never contains authoritative expected program output.
+Its manifest says `synthetic=true`, `authoritative=false`, and
+`purpose=ingestion_validation_only`. Raw binary fields are not written into a
+`fixed_width_text` artifact; a `source_bytes` representation requires an
+explicit binary-capable output mode and otherwise blocks generation.
+
+## Copilot migration workflow
+
+Use the workspace-scoped [mainframe JCL migration skill](.github/skills/mainframe-jcl-migration/SKILL.md)
+directly, or select the [Mainframe JCL Migrator agent](.github/agents/mainframe-jcl-migrator.agent.md)
+for the phase-gated workflow. Example invocation:
+
+```text
+/mainframe-jcl-migration /path/to/mainframe-workspace BANKRUN migration/BANKRUN
+```
+
+The first argument is the workspace root, the second is a JCL job name or
+path, and the optional third argument is the target directory.
+
+## The 5 Language Model Tools (for Copilot agent mode)
+
+Registered in [`extension/package.json`](extension/package.json) under
+`contributes.languageModelTools` and implemented in
+[`extension/src/extension.ts`](extension/src/extension.ts):
+
+1. **`mainframe_getDependencyGraph`** - whole-graph or scoped CALL/COPY/EXEC graph.
+2. **`mainframe_getCallers`** - who calls a given program, including JCL `EXEC PGM=`.
+3. **`mainframe_resolveCopybook`** - resolve a COPY target to its file + users.
+4. **`mainframe_impactAnalysis`** - transitive blast-radius + risk rating before any change.
+5. **`mainframe_runMigrationScript`** - runs any of the 17 scripts above, workspace-sandboxed.
+
+These are backed by the same language server used for interactive
+go-to-definition/hover, so an agent and a human developer see identical
+dependency information.
+
+## Building
+
+```bash
+cd server && npm install && npm run compile
+cd ../extension && npm install && npm run compile
+```
+
+Then press F5 in VS Code (or use the "Run Extension" launch
+configuration in [.vscode/launch.json](.vscode/launch.json)) to try it
+against [test-fixtures/](test-fixtures/).
+
+A standalone smoke test for the language server (no VS Code required) is
+at [`server/scripts/smoke_test.js`](server/scripts/smoke_test.js):
+
+```bash
+node server/scripts/smoke_test.js test-fixtures
+node server/scripts/config_parity_test.js test-fixtures
+```
+
+## Installing the release artifacts
+
+Build the wheel, source distribution, and bundled VSIX without publishing:
+
+```bash
+python tools/build_release.py
+python -m pip install dist/mainframe_modernization_toolkit-0.1.0-py3-none-any.whl
+mainframe-toolkit --version
+```
+
+The wheel contains the standalone VS Code extension, including the bundled
+`dist/server.js`. Export and verify the exact embedded bytes before installing
+the VSIX manually:
+
+```bash
+mainframe-toolkit vsix export --output mainframe-migration-toolkit-0.1.0.vsix
+mainframe-toolkit vsix verify mainframe-migration-toolkit-0.1.0.vsix
+code --install-extension mainframe-migration-toolkit-0.1.0.vsix
+```
+
+The extension invokes `mainframe-toolkit` by default. Set
+`mainframeMigration.executablePath` to the installed executable's absolute
+path when it is not on the VS Code extension host's `PATH`. Run
+`mainframe-toolkit workspace init <workspace>` or the
+`Mainframe Migration: Initialize Workspace` command to add the packaged
+configuration, schemas, skill, and agent without overwriting existing files.
+
+## Source extensions referenced
+
+This project was built with the two extensions supplied in the task as
+primary references for real-world COBOL/JCL LSP feature scope:
+
+- [eclipse-che4z/che-che4z-lsp-for-cobol](https://github.com/eclipse-che4z/che-che4z-lsp-for-cobol) -
+  full COBOL LSP (ANTLR-based, JVM). Studied for how it models copybook
+  resolution, dialects, and CALL/COPY dependency nodes; not vendored
+  directly (JVM/Maven toolchain would be heavy for an agent-facing tool -
+  see [docs/RESEARCH.md](docs/RESEARCH.md) for the tradeoff rationale).
+- [BroadcomMFD/jcl-language-support](https://github.com/BroadcomMFD/jcl-language-support) -
+  JCL syntax highlighting/snippets/Zowe integration. Studied for JCL file
+  detection conventions (`.jcl`/`.cntl`, jobcard sniffing) and DD/DSN
+  navigation patterns.
+- Their Marketplace listings (`broadcomMFD.jcl-language-support`,
+  `broadcomMFD.cobol-language-support`) were fetched for feature summaries.
+
+All COBOL/JCL fixtures under `test-fixtures/` are original, written for
+this project (not copied from any repository).