jvcode 0.1.1

jvcode

jvcode is an installable command-line tool for local Markdown Issues, offline Workflow checks, and configured direct Provider Runs. This README is the installed-tool quick start; it does not require a source checkout.

Prerequisites

• A .NET 10 runtime and Git.
• An installed jvcode command.
• PowerShell 7 (pwsh) for the workflow and direct-run profiles. The issues-only profile does not need PowerShell or a Provider.

All three profiles are local and additive. Initialization does not start a Provider, make a network request, or create a Git commit.

Start in an empty Git repository

Create or enter an empty repository, then choose one profile:

git init
jvcode init --profile issues-only --output plain

The init command is additive and fail-safe. Use --dry-run to preview the files before writing; commit the generated tracked files yourself when you are satisfied.

Every profile starts with the same offline preflight and validation:

jvcode doctor --output plain
jvcode issues validate --profile completion --output plain

doctor is read-only. It checks the discovered repository, configuration, Ticket Source, Roles, and Provider executables without starting work.

issues-only: inspect a local Issue

After the commands above, select the sample Issue or your own local Issue:

jvcode issues next --output plain

This profile needs no Provider, credentials, or network access.

workflow: prove one offline Workflow

In a new empty Git repository, run the following complete smoke journey verbatim:

jvcode init --profile workflow --output plain
jvcode doctor --output plain
jvcode issues validate --profile completion --output plain
jvcode workflow validate .jvcode/workflows/smoke.workflow.yaml --output plain
jvcode workflow validate .jvcode/workflows/smoke.loop.yaml --output plain
jvcode workflow plan .jvcode/workflows/smoke.workflow.yaml --output plain
jvcode gate run --checkpoint smoke --output plain
jvcode workflow run .jvcode/workflows/smoke.workflow.yaml --quiet --output plain
jvcode workflow loop .jvcode/workflows/smoke.loop.yaml --max-iterations 1 --quiet --output plain

The generated Gate is the offline success. The Workflow and Loop leave evidence under .agent-runs/; they do not claim or complete the sample Issue and do not require Provider credentials.

direct-run: prove one local direct Run

In a new empty Git repository with pwsh on PATH, run:

jvcode init --profile direct-run --output plain
jvcode doctor --output plain
jvcode config explain --output plain
jvcode issues validate --profile completion --output plain
jvcode run --prompt-file .jvcode/prompts/direct/smoke.md --role smoke --dry-run --output plain
jvcode run --prompt-file .jvcode/prompts/direct/smoke.md --role smoke --output plain

The generated generic Provider wrapper is deterministic, local, and network-free. It is only a smoke adapter: replace the smoke candidate and keep credentials in environment or ignored local configuration before using a real Provider.

For the full command contracts and stable exit-code meanings, see the jvcode documentation and the exit-code reference.