First Run¶

Goal¶

Use this page when you want the shortest honest verification that the installed runtime works.

sequenceDiagram
    participant U as User
    participant C as CLI
    U->>C: bijux --version
    C-->>U: runtime identity
    U->>C: bijux --help
    C-->>U: command surface
    U->>C: bijux status --format json --no-pretty
    C-->>U: machine-readable output

This sequence shows the smallest honest verification loop: identity first, then help generation, then one ordinary command rendered as machine-readable output.

flowchart TD
    A[Install bijux-cli] --> B[Run bijux --version]
    B --> C[Run bijux --help]
    C --> D[Run bijux status --format json --no-pretty]
    D --> E[You have verified identity, routing, and structured output]

This flowchart summarizes what each verification step adds. By the end of the path, you have checked that the binary resolves, the command tree renders, and the runtime can emit stable structured output.

Minimal Verification¶

Run these commands:

bijux --version
bijux --help
bijux status --format json --no-pretty

What Each Step Proves¶

bijux --version proves the installed entrypoint resolves and reports runtime identity
bijux --help proves routing and help generation are available
bijux status --format json --no-pretty proves normal command execution and structured output emission

What This Does Not Prove¶

These commands do not prove:

plugin lifecycle behavior
configuration file workflows
REPL operation
release-channel compatibility beyond the installed package you are running

If Any Step Fails¶

Go to: