ReversePort changelog

version

1.22.0 → 1.24.0

version

1.21.0 → 1.22.0

version

1.20.0 → 1.21.0

version

1.19.0 → 1.20.0

version

1.18.0 → 1.19.0

version

1.16.0 → 1.18.0

https://raw.githubusercontent.com/laaielichter/reverseport/HEAD/AGENTS.md

− Use [.nvmrc](.nvmrc) and `package.json#packageManager` for the pinned toolchain. Cursor Cloud may place older Node.js first on `PATH`; environment setup installs the pinned toolchain under `/usr/local/bin`.− For test changes or provider claims, use [docs/testing.md](docs/testing.md). Prefer real public CLI/MCP workflows, then production-boundary integration, then producer goldens. Keep module tests for distinct semantics stronger workflows cannot reliably reproduce. Preserve malformed-input, cancellation, cleanup, permission, capacity, and target-identity coverage when pruning. Report unverified coverage explicitly; simulated providers do not establish real-provider behavior.+ > **Using ReversePort rather than changing it?** This file is for contributors. To use it: connect with+ > `reverseport mcp` (`reverseport connect <client>` prints the config for any agent), follow the server's+ > instructions and start with `re_scan {path}`. `skills/reverse-engineer/SKILL.md` covers recon,+ > `skills/port-project/SKILL.md` porting, and `skills/troubleshoot/SKILL.md` errors.+ Follow the [contribution scope and fail-closed integration rule](CONTRIBUTING.md#contribution-scope). Do not integrate capabilities while material scope, authority, side-effect, or required verification questions remain unresolved. For new providers or capabilities involving target execution, injection, mutation, or protection recovery, seek the required maintainer scope decision before substantial implementation for integration. Welcome early proposals, small exploratory prototypes, and draft P+ For lifecycle changes, follow [ownership and completion invariants](docs/tool-design.md#own-the-lifecycle) and select the applicable [lifecycle regressions](docs/testing.md#lifecycle-regressions). Include late handshakes, cancellation during final cleanup, mixed child outcomes, and cleanup retry where those stages exist; active-execution cancellation alone does not cover finalization.+ Before adding complexity for a speculative or vanishingly unlikely race or security edge case, explain the concrete failure mode, likelihood, and complexity cost to the user and get their buy-in. Do not silently expand scope for theoretical robustness.+ When addressing a review thread, inspect the producing boundary and affected consumers for brittleness. Complete directly related refactoring in the same change. Before resolving the thread, explain the root cause, structural fix, validation, and any remaining cleanup.+ ## Performance+ Design analysis workflows and agent interfaces for efficiency from the first+ implementation. Correctness, useful answers, Evidence provenance, caller choices,+ compatibility and safe resource bounds remain required.+ Optimize in this order:+ 1. Agent tokens and context. Return the smallest sufficient answer with+    necessary provenance, coverage and limitations. Use task selection,+    summaries, paging and retained Evidence where supported; honor requested+    detail and keep complete Evidence accessible. Count the whole task,+    including schemas, extra calls and retries.+ 2. Analysis time. Reuse validated results and shared work. Cache keys must+    cover result-affecting inputs; define invalidation and lifetime. Validate+    freshness before reporting cached live state as current.+ 3. CPU and memory. Avoid unnecessary work and copies; bound concurrency,+    retained state and serialization growth.+ For changes affecting these costs, measure representative completed tasks and+ compare equivalent workflows before and after where available. Report token+ usage, elapsed time, CPU time and peak process-family memory. Separate cold+ and warm runs, label estimates, and state unmeasured costs. Fewer bytes alone+ do not establish fewer tokens or faster analysis.+ Use [.nvmrc](.nvmrc) and `package.json#packageManager` for the pinned toolchain. Cursor Cloud may place older Node.js first on `PATH`; environment setup installs the pinned toolchain under `/usr/local/bin`. Prefix `PATH="/usr/local/bin:$PATH"` before `node` and `npm`.+ Do not add `.gitattributes` rules: the Claude plugin directory rejects the repository when a clone can differ from its download. Line endings are LF, except CRLF for `.cmd` fixtures; see [Windows source checkouts](CONTRIBUTING.md#windows-source-checkouts).+ Coordinate expensive checks across agents. If a test unexpectedly consumes heavy CPU, stop its owned process family and profile a bounded representative case before retrying. Inspect production work, fixture generation, subprocesses, and repeated setup; preserve regression coverage when optimizing. Follow the [test resource guidance](docs/testing.md#developer-commands).+ For test changes or provider claims, use [docs/testing.md](docs/testing.md). Select applicable [boundary regressions](docs/testing.md#boundary-regressions) for parser, inventory, snapshot, and projection fixes. Prefer real public CLI/MCP workflows, then production-boundary integration, then producer goldens. Keep module tests for distinct semantics stronger workflows cannot reliably reproduce. Preserve malformed-input, cancellation, cleanup, permission, capacity, and target-identity coverage whe+ ## Issue Reports+ Follow [issue reporting guidance](CONTRIBUTING.md#reporting-issues) and the matching+ issue form. Keep reports concise and cite the smallest useful evidence.+ Distinguish observed results, source-derived reasoning, hypotheses, and proposed+ checks. Never claim runtime reproduction or measurements you did not perform.+ Use `NOT_ENOUGH_INFO` with an explanation for missing narrative answers or evidence.+ Incomplete reports, source-only findings, and early feature or design ideas are+ welcome when their limitations are explicit; a completed diagnosis or fix is not

version

1.15.0 → 1.16.0

description

Reverse engineer anything. Port it anywhere. One MCP server for coding agents. → Reverse engineer and port apps and games: Godot, Unity IL2CPP, .NET, binaries, with parity checks.

version

1.9.0 → 1.15.0

website_url

https://github.com/laaielichter/reverseport → https://laaielichter.github.io/Reverseport/

version

1.8.0 → 1.9.0

https://raw.githubusercontent.com/laaielichter/reverseport/HEAD/AGENTS.md

+ - `hooks/hooks.json` and `port/hooks/guard.mjs`: the plugin's deterministic guard hooks (no model, no network).+   `port/src/proofcase.mjs` is the `re_case` ledger; `port/src/stashpad.mjs` the optional Stashpad link.

version

1.7.0 → 1.8.0

version

1.6.0 → 1.7.0

version

1.5.0 → 1.6.0

version

1.0.0 → 1.5.0