Skip to main content
These two commands give you a structural view of the porting workspace and let you measure how closely the Python implementation tracks the original TypeScript archive.

​
manifest

Prints the current Python workspace manifest. 
python3 -m src.main manifest
Builds a PortManifest by scanning all .py files under src/, then formats the result as Markdown. The manifest includes the source root path, total file count, and an annotated list of all top-level Python modules sorted by file count (most files first). Output fields
FieldDescription
Port rootAbsolute path to the src/ directory
Total Python filesTotal number of .py files found recursively
Top-level Python modulesEach top-level module with its file count and a short notes string
The notes string is looked up from a built-in table for known modules (main.py, commands.py, tools.py, etc.). Unknown modules are labelled Python port support module. Example output 
Port root: `/home/user/claw-code/src`
Total Python files: **74**

Top-level Python modules:
- `commands.py` (1 files) — command backlog metadata
- `tools.py` (1 files) — tool backlog metadata
- `models.py` (1 files) — shared dataclasses
- `main.py` (1 files) — CLI entrypoint
- `query_engine.py` (1 files) — port orchestration summary layer
- `port_manifest.py` (1 files) — workspace manifest generation
- `task.py` (1 files) — task-level planning structures
- `assistant` (4 files) — Python port support module
- `bootstrap` (3 files) — Python port support module
When to use it Run manifest when you need a quick inventory of how many Python files exist and which top-level modules are present. It is a lighter-weight alternative to summary when you only care about the file structure.

​
parity-audit

Compares the Python workspace against the local TypeScript archive when the archive is available. 
python3 -m src.main parity-audit
Runs run_parity_audit() which checks:
  • Root file coverage — how many of the expected root-level Python port targets (e.g. main.py, tools.py, setup.py) exist in src/.
  • Directory coverage — how many expected subdirectory ports (e.g. assistant/, bootstrap/, cli/) exist in src/.
  • Total file ratio — current Python file count vs. the archived TypeScript-like file count stored in reference_data/archive_surface_snapshot.json.
  • Command entry coverage — entries in reference_data/commands_snapshot.json vs. the reference command count.
  • Tool entry coverage — entries in reference_data/tools_snapshot.json vs. the reference tool count.
The archive lives at archive/claude_code_ts_snapshot/src/ relative to the project root. If this directory does not exist, the audit reports that the archive is unavailable and skips the comparison tables.
Example output (archive present) 
# Parity Audit

Root file coverage: **17/18**
Directory coverage: **28/29**
Total Python files vs archived TS-like files: **74/80**
Command entry coverage: **42/42**
Tool entry coverage: **18/18**

Missing root targets:
- none

Missing directory targets:
- upstreamproxy
Example output (archive absent) 
# Parity Audit

Local archive unavailable; parity audit cannot compare against the original snapshot.
When to use it Run parity-audit after adding new Python modules or updating the reference snapshots to confirm coverage is complete. The missing target lists pinpoint exactly which files or directories still need to be created.

Build docs developers (and LLMs) love

Get started for freeTalk to us