CONTRIBUTING.md

Rama main · réplica de lectura del repositorio original.

# Contributing

[Documentation](documents/README.md)

Changes should preserve local runtime configuration and keep committed examples
portable.

Before submitting a change:

```bash
make hooks-install
make ci-local JAVA_HOME_21=/path/to/jdk-21 SOURCE_LINT_TOOLING=/path/to/shared
```

Local CI also installs the locked OpenAI OAuth runtime in a temporary directory
and checks response limits, chat and streaming with synthetic responses. Run
`make openai-oauth-source-check` for that focused gate.

Prepare Nodepad’s pinned patched source with `bash stacks/nodepad/clone-repo.sh`,
then run `npm ci` inside `stacks/nodepad/repo`. `make ci-local` runs its proxy,
client and TypeScript controls in a fresh tree made from the pinned Git base and
current patches; it leaves the original clone untouched. `NODEPAD_UPSTREAM_ROOT`
can select an existing prepared public clone. The image build runs the same
verification on its freshly patched source.
Install the locked npm tools in each checkout or worktree. `make ci-local` checks
for its Markdown tooling before running the source suites. The Mylar checks include
workflow intake and authenticated health regressions and the complete portable
publication suite used by the image build, including its recovery controls.
Local health patch checks use the saved public API predecessor; the image gate
also checks the assembled application source.
`make ci-local` runs the worker's full suite through `komga-worker-check` in a
private copy, alongside the portable `komga-source-check` and compiled observer
checks. The full worker and Mylar gates require `ARCHIVING_UTILS_ROOT` pointing
to the checked archive SDK; the worker uses its executable `bin/archiving-utils`
unless `ARCHIVING_UTILS_BIN` explicitly selects the checked backend. The Mylar
gate runs the retained API, worker handoff and authenticated launch controls too.
The full worker gate refuses skipped controls.
Local tagging controls exercise the real native admission modules; three tests
require bundled tagging executables and run in the image build. The image gate
requires all tagging controls to pass without skips.
The Mylar gate also runs the complete standalone installation, backup and terminal suites.
`MYLAR_PYTHON` selects the Mylar source-test interpreter. Authenticated host
controls use `PUBLICATION_HOST_PYTHON` (default `python3`) and require Linux
memfd/seal support; the gate checks those features before running the suites.
Prepare the shared source-lint checkout and locked dependencies as described in
[local CI setup](documents/DEVELOPMENT-WORKFLOW.md#3-local-ci-before-pushing).
Its revision and Ruff version must match the hosted workflow.
The final secret scan covers the complete history reachable from `HEAD`.
Staged secrets remain checked by the commit hook. Use `make secrets` to audit
all local refs, including unrelated branches and snapshots.

Do not commit `stack.env`, `.env`, private keys, credentials, real hostnames,
private addresses, or machine-specific paths. Update `stack.env.example`,
`stack.yaml`, the stack README, and preparation behavior together when a
stack's contract changes.

After adding or renaming a stack, regenerate documentation:

```bash
python3 scripts/build-stack-catalog.py
python3 scripts/build-topology.py --in-place
```

The topology inventory comes from `documents/topology.yaml`. The architecture
diagram has a separate checked source at
`documents/topology.architecture.json`; update and validate that source before
replacing `documents/topology.html` and its `topology-dark.png` preview.

Keep application-specific setup, environment variables, health checks, and
troubleshooting in `stacks/<name>/README.md`. Cross-stack concepts belong in
`documents/`; the root README should remain a short navigation and orientation
page. Update generated documents through their scripts rather than editing
generated sections by hand.

Use focused commits with Conventional Commit subjects. Explain migrations or
behavior changes in the commit body.

Local hooks run staged secret scanning, workflow checks, Dockerfile linting,
dependency configuration validation, repository validation, and whitespace
checks before every commit:

```bash
make hooks-install
```

To opt in to Pages browser tests before pushing, follow the
[pre-push setup](documents/DEVELOPMENT-WORKFLOW.md#3-local-ci-before-pushing).
The default hook installation runs commit checks only.

## Devcontainer

See [the devcontainer guide](.devcontainer/README.md) for the repository toolchain,
setup, checks and platform limits.