TypeScript Frida CLI Architecture

Configure a pnpm-based Node.js TypeScript project using ESM, strict compiler settings, ESLint, Prettier, and Vitest.

Model process identifiers, session identifiers, commands, and instrumentation states with branded types, readonly data, and discriminated unions.

Validate unknown configuration and runtime data at application boundaries with Zod schemas.

Represent expected failures with typed result values and translate unexpected exceptions into application errors.

Write Vitest unit tests for an asynchronous TypeScript service using test doubles and deterministic assertions.

Define a bounded domain vocabulary for processes, instrumentation sessions, probes, trace events, and recordings.

Partition process discovery, interception, API tracing, and recording into cohesive vertical feature slices.

Define application ports that keep Frida, terminal I/O, and file storage outside the domain and application layers.

Model valid instrumentation-session transitions as an explicit state machine.

Represent significant session actions as immutable domain events without coupling them to storage or display concerns.

Assemble handlers and adapters in a composition root without using a global service locator.

Parse quoted REPL input into a typed command name, arguments, and options.

Implement application command handlers whose behavior is independent of terminal parsing and rendering.

Route one-shot CLI commands and interactive REPL commands through the same application handlers.

Build an asynchronous REPL loop with Node.js readline/promises that survives recoverable command failures.

Implement an extensible command registry that supplies help text and tab-completion candidates.

Propagate cancellation from Ctrl+C to a running command without terminating the entire REPL.

Render typed success and error results consistently for human-readable terminal output.

Configure separate TypeScript build targets for the Node.js host and the Frida JavaScript agent using Frida type definitions and an agent bundler.

Distinguish responsibilities that must run in the Node.js host from those that must run inside the target process.

Attach to an authorized local Windows test process and load a minimal compiled agent.

Define and validate a typed message protocol between the host and the injected agent.

Expose a typed agent operation through Frida RPC and invoke it from the Node.js host.

Handle detach notifications and agent script destruction through an idempotent session lifecycle.