vac-optimizer/AGENTS.md

Agent skills

Issue tracker

Issues and specs live in Gitea Issues; use tea-cli for supported tracker operations. Before tracker work, read docs/agents/issue-tracker.md for commands and API alternatives.

Triage labels

Use the default canonical labels: needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix. See docs/agents/triage-labels.md.

Domain docs

This is a single-context repo using root CONTEXT.md and docs/adr/. See docs/agents/domain.md.

GitFlow

• develop is the default integration branch; main contains releases. Start feature/* branches from the current origin/develop and target their PRs to develop.
• Rebase working branches onto the latest origin/develop before opening or merging a PR. If develop advances, rebase and rerun the PR checks before merging.
• Integrate through PRs with successful required checks and merges restricted to designated maintainers through Gitea's merge allowlist. Use merge commits (--no-ff) with squashing disabled. Direct and forced pushes to main and develop are forbidden.
• Use Conventional Commits for new commits and PR titles.
• Create release/X.Y.Z from develop and hotfix/X.Y.Z from main. Only release/* and hotfix/* PRs target main. Merge each release or hotfix into both main and develop, keeping its branch until both PRs are merged.
• Use merges and back-merges for releases and hotfixes. Never rebase main, develop, or a frozen release branch.

The CI workflow is .gitea/workflows/ci.yml. Activation is tracked in Gitea issue #268; Actions is enabled with owner approval, and the migration gate stays required until live workflow validation and merge-message review. Before changing CI, image publication, or activation settings, read Gitea Actions.

Before preparing a release or hotfix, creating a tag, or changing image publication, read GitFlow and releases for package versions, explicit stable tags, and image promotion.