Skip to content

docs: add missing module-level docstrings#373

Open
Blackgaurd wants to merge 1 commit into
docs-retire-backend-specfrom
docs-module-docstrings
Open

docs: add missing module-level docstrings#373
Blackgaurd wants to merge 1 commit into
docs-retire-backend-specfrom
docs-module-docstrings

Conversation

@Blackgaurd

Copy link
Copy Markdown
Collaborator

What

Adds a short module-level docstring to the 22 backend modules that had none: `main.py`, `core/api/routes.py`, `core/db/`, `core/utils/`, `core/calendars/*` (interface, registry, utils, and the 4 definitions), and the previously-undocumented `core/service/{builder,catalog,models,locks}.py` and `core/runtime/{config,loader,registry,runner,validator}.py`.

Why

The "self-documenting code" half of the docs restructure: per-module purpose should live in the code itself, complementing the co-located `AGENTS.md` files. The complex `service/` and parts of `runtime/` already had rich module docstrings; this fills the gaps.

Benefit

Every backend module now states its purpose at the top. No behavior change.

Stacked on #372.

add a short module docstring to the modules that had none (main.py,
api/routes, db, utils, calendars, and the undocumented service/runtime
modules) so per-module purpose lives in the code itself, complementing
the co-located AGENTS.md files. no behavior change.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Jul 5, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant