gormes-dev-runtime

Prevent PATH conflicts during local Go development by isolating runtime surfaces to distinguish between source checkout, live binaries, and the installed command. This separation avoids executing outdated builds and prevents session-state leaks across execution cycles.

Gormes dev-runtime surface discovery identifies and validates the active runtime paths across source checkout, runtime binaries, and the installed command. It ensures environment isolation by mapping which execution context is active, preventing cross-contamination of session-state and gateway configurations during local development.

Validate local Gormes changes by running the dev runtime surface to test modifications in an isolated environment. This workflow confirms that your source checkout operates correctly across go run, bin/gormes, and install.sh workflows before you commit to a full build or system installation.

Session-state leaks between build cycles occur because the runtime surfaces for the source checkout, live binary, and installed command are not properly isolated. Distinguishing these execution contexts and applying environment isolation prevents state contamination across go run and install.sh workflows.

Yes, environment isolation workflows apply to both go run and install.sh commands. The dev-runtime validation process distinguishes between the current checkout, the live binary, and the installed command, ensuring safe execution flows and preventing PATH conflicts across all Gormes build and run cycles.

Diagnose gateway and sessions.db issues by validating local runtime surfaces to ensure environment isolation. Checking for PATH conflicts and session-state leaks between the source checkout and runtime binaries helps identify if incorrect execution contexts are causing database or gateway failures during development.