Module service 

The web host’s one way into the runtime: every entry point it uses, re-exported or delegated without changing a result. A write the host serves goes through actions::perform, like every interface’s; a later feature adds read views here as delegates, never a second write path. The layering test holds the host to this module.

Re-exports

pub use crate::RunOptions;

Modules

actions

The action list and the one dispatcher.

approvals

Calls waiting for a person, and who answers them.

bug

A bug as speccoder keeps it (read-only; a bug’s actions are kinds).

code

The code view: the branch’s change, its files.

controls

Tokens and money.

current

The features.

doctor

The machine and the project, checked.

documents

The feature’s documents.

evidence

A task’s evidence.

github

GitHub: sign-in, issues, the branch’s pull request.

handoff

The pull request, previewed.

inbox

Needs You.

init

Setting up a project.

next

The next steps a result names.

progress

A run’s progress, as it happens and as another process left it.

review

The person’s review of the spec.

settings

speccoder.toml.

status

Read views.

tour

A task’s evidence tour (evidence_tour), read as recorded.

worktree

Where speccoder keeps its state.

Structs

FormatWords

How the project’s format words things, for the page’s header.

Functions

commit_patch

One commit’s patch, if commit names a commit (a blob or a tree id from elsewhere in the repository is never shown); empty otherwise.

create_skill

The installed name of the format’s skill that creates a unit, if it has one.

format_words

The words of the format of the project at root.