Run Your First Commands¶

Goal¶

Use a small command set to prove the runtime is alive, reachable, and returning useful output.

flowchart TD
    A[bijux --help] --> B[Discover top-level commands]
    B --> C[bijux status]
    C --> D[See normal command execution]
    D --> E[bijux doctor]
    E --> F[See diagnostics behavior]

This flowchart shows the minimal progression from discovery to confidence. Help proves the command tree exists, status proves normal execution works, and doctor proves the runtime can inspect its own environment.

flowchart LR
    A[Help] --> B[Routing proof]
    C[Status] --> D[Execution proof]
    E[Doctor] --> F[Diagnostic proof]

The second diagram compresses the same idea into capability labels. It explains why these three commands are paired together instead of treated as redundant checks.

Minimal Command Set¶

Run these in order:

bijux --help
bijux status
bijux doctor

Why These Commands¶

bijux --help proves the command surface is available
bijux status proves ordinary command execution works
bijux doctor proves diagnostic reporting works and often catches issues that status alone does not expose

What Not To Infer Yet¶

These commands do not prove:

plugin lifecycle behavior
configuration file workflows
REPL behavior
compatibility with every packaging channel on the machine

Practical Reading¶

At this point you should know whether the runtime is usable. You should not yet assume it is production-ready for automation until you have checked structured output and any environment-specific constraints.