Crate sofie_cli 

Structs

BenchReport

Binary

BuildOptions

The app’s own binary, or <app>-worker (worker); pgo rebuilds it with a profile recorded under sofie bench’s load.

Change

FeatureEdit

Finding

FixReport

FuzzOptions

FuzzReport

Measurement

NewCommand

NewMenuEntry

NewRoute

RouteResult

ScaffoldedTests

SeedReport

SeededRoute

Split

SplitPlan

UpgradeReport

Enums

AccountScreen

A member’s own screen sofie-identity ships, mounted in one of the module’s areas.

AreaAccess

The variants of sofie::http::Access, each fixed by the principal the area is written with.

Built

FeatureChange

FileChange

GenError

GenMode

GenOutcome

Image

IslandMode

NewCode

Outcome

Verdict

Constants

NEW_COMMANDS

Functions

bench

Without a target it builds the app, starts it on a free local port with the shield off and its database on this machine, and loads that; a target must run with SOFIE_SHIELD=off, and one not on this machine is signed in to only as accounts named in SOFIE_BENCH_<AREA>_EMAIL/_PASSWORD.

build

--image builds nothing on the host: the image builds the binary itself.

change_feature

Edits only the features array of the sofie dependency in app/Cargo.toml, as text, so the manifest keeps its comments and layout.

check_app

Generated files are rendered only from a model the rules accept, and dead code is judged only against current ones.

check_config

Values are never repeated, as they may be secrets.

check_in_build_script

check_schema

Run through the app’s own binary, the only one knowing its aggregates.

component

enabled is asked only for a component behind a feature, as reading it runs Cargo.

component_list

With the app’s sofie features, each feature a component needs is marked on or off.

dev

Development builds migrate on start, so a database on another host takes remote_database, never what the shell or .env happens to hold.

explain

fix_app

fresh_database

Run through the app’s own binary, the only one embedding the migrations; production binaries leave the command out.

fuzz

The routes take turns; what each request sends is drawn from the seed, so a run sends the same requests again, apart from the record ids the database lists.

gen_app

Writing, it first makes the generated code reachable, as sofie fix would.

has_islands

new_app

new_code

Writes only the sources; sofie gen and sofie check follow, as after any edit. A failure part-way undoes what was written.

new_module

openapi

regenerate

regenerated

sofie gen: the generated code, then docs/gen/ for an app keeping its docs, read from the model the new code gives.

route_table

The framework packages’ routes are part of the table, so failing to read them fails it.

run_schedule

Queues the schedule’s job through the app’s development binary, the only one knowing the worker’s schedules; the worker sofie dev runs takes it next, whatever its interval.

scaffold_screen

scaffold_tests

seed

Records are made the way the app makes them: posted to its creating routes, whose actions call the factories, as the member sofie bench signs in with, so the load reads them. Each module’s seeds/<area>.<handler>.json is posted first, then volume generated inputs per route.

serve_mcp

Every tool reads the app afresh, so edits between calls show.

split_module

split_plan

task_table

typescript

upgrade

Without write, shows what each codemod would change and touches nothing.

write_docs