POLICY is the authority for development, checks, merges and releases. Start with CONTRIBUTING for setup and verification; the project README explains Lina and how to run it.
- Open an issue for a bug, feature, compatibility report or design decision. The issue forms show the information to include; small fixes do not require an issue first.
- Open a pull request
targeting
dev. Follow the PR template: explain the problem, resulting behavior, checks actually run and material limitations. - Report vulnerabilities through the private route in SECURITY, keeping exploit details and user data out of public issues and logs.
dev is the default integration branch. Behavior changes start with a failing
regression test. Before merging, the current candidate must pass dev-gate, be
up to date with its target, have no conflicts and have resolved review conversations.
Use merge commits only; do not bypass protection. Required approving reviews are
zero, while confirmed defects still need resolution.
CI operation explains the checks and branch protections;
validation defines their acceptance limits. A future
same-repository dev -> main promotion requires explicit owner instruction,
release notes and release-gate. Source checks do not authorize publication or
deployment.