From 7d60157863bf11957c3265cce680e3e264fd5605 Mon Sep 17 00:00:00 2001 From: Nessar Date: Tue, 13 Oct 2026 19:38:32 +0200 Subject: [PATCH] docs: migrate repository guidance to Gitea --- .agents/skills/code-review/SKILL.md | 2 +- .../skills/setup-matt-pocock-skills/SKILL.md | 4 +- .../issue-tracker-gitea.md | 48 +++++++++++++++ .agents/skills/wizard/SKILL.md | 2 +- .antigravityrules | 12 ++-- ...uvegarder-et-figer-les-jours-deja-poses.md | 4 +- ...odes-de-repos-autour-des-jours-declares.md | 6 +- ...urs-declares-dans-les-regles-de-periode.md | 6 +- ...les-motifs-if-then-et-les-droits-acquis.md | 8 +-- ...n-statistics-for-calculated-leave-usage.md | 4 +- ...rk-sequence-and-time-off-period-lengths.md | 6 +- ...w-gross-earned-leave-by-generating-rule.md | 6 +- ...-public-holidays-connected-to-a-weekend.md | 6 +- .../05-warn-about-weeks-with-one-workday.md | 6 +- ...evaluation-et-comparaison-des-objectifs.md | 2 +- ...prevention-des-pertes-depuis-les-regles.md | 2 +- ...mposer-regles-semaines-feriees-et-repos.md | 2 +- ...04-composer-regles-sequences-de-travail.md | 2 +- .../05-piloter-economie-des-jours-appoint.md | 2 +- ...regles-sauvegardees-et-valider-ensemble.md | 2 +- .../01-remove-original-decision-trace.md | 2 +- .../issues/02-verify-trace-free-planning.md | 4 +- ...verify-and-optimize-planning-benchmarks.md | 2 +- AGENTS.md | 14 +++-- README.md | 42 ++++++++----- ...d-horizons-and-cancellable-calculations.md | 2 +- ...007-declared-days-and-reported-balances.md | 2 +- docs/agents/issue-tracker.md | 61 +++++++++++-------- docs/benchmark/README.md | 17 +++--- docs/planner-cancellation.md | 2 +- docs/statistics.md | 2 +- 31 files changed, 180 insertions(+), 102 deletions(-) create mode 100644 .agents/skills/setup-matt-pocock-skills/issue-tracker-gitea.md diff --git a/.agents/skills/code-review/SKILL.md b/.agents/skills/code-review/SKILL.md index 8979b06..b194fe6 100644 --- a/.agents/skills/code-review/SKILL.md +++ b/.agents/skills/code-review/SKILL.md @@ -35,7 +35,7 @@ Inspect `git status --short` and distinguish pre-existing user changes from task Look for the originating spec, in this order: 1. The user's explicit spec, ticket, path, or acceptance criteria in the conversation. Preserve it as authoritative even when commits reference other work. -2. Issue/MR references in relevant commit messages — fetch via `docs/agents/issue-tracker.md` when no explicit source was supplied. +2. Issue/PR references in relevant commit messages — fetch via `docs/agents/issue-tracker.md` when no explicit source was supplied. 3. A PRD/spec file under `docs/`, `specs/`, or `.scratch/` matching the branch name or feature. 4. If nothing is found or the source is inaccessible, continue the Standards review and report the Spec coverage limitation. Ask for a source only when needed to answer the user's request; do not invent requirements or require tracker setup. diff --git a/.agents/skills/setup-matt-pocock-skills/SKILL.md b/.agents/skills/setup-matt-pocock-skills/SKILL.md index 12136b4..3c32a7a 100644 --- a/.agents/skills/setup-matt-pocock-skills/SKILL.md +++ b/.agents/skills/setup-matt-pocock-skills/SKILL.md @@ -42,10 +42,11 @@ Preserve the configured tracker. For a new setup, infer a likely tracker from th - **GitHub** — issues live in the repo's GitHub Issues (uses the `gh` CLI) - **GitLab** — issues live in the repo's GitLab Issues (uses the [`glab`](https://gitlab.com/gitlab-org/cli) CLI) +- **Gitea** — issues live in the repo's Gitea Issues (uses `tea-cli`, or `tea` where that is the installed binary; inspect its help for supported commands) - **Local markdown** — issues live as files under `.scratch//` in this repo (good for solo projects or repos without a remote) - **Other** (Jira, Linear, etc.) — ask the user to describe the workflow in one paragraph; the skill will record it as freeform prose -Record the choice in `docs/agents/issue-tracker.md`. The GitHub and GitLab templates carry a "PRs as a request surface" flag, defaulted **off** — leave it off and don't raise it; a user who wants external PRs in the triage queue can flip the flag in the file later. +Record the choice in `docs/agents/issue-tracker.md`. The GitHub, GitLab, and Gitea templates carry a "PRs as a request surface" flag, defaulted **off** — leave it off and don't raise it; a user who wants external PRs in the triage queue can flip the flag in the file later. **Section B — Triage label vocabulary.** Skip this section entirely if the `triage` skill isn't installed (exploration told you) — an uninstalled skill needs no labels. @@ -105,6 +106,7 @@ Then write the docs files using the seed templates in this skill folder as a sta - [issue-tracker-github.md](./issue-tracker-github.md) — GitHub issue tracker - [issue-tracker-gitlab.md](./issue-tracker-gitlab.md) — GitLab issue tracker +- [issue-tracker-gitea.md](./issue-tracker-gitea.md) — Gitea issue tracker - [issue-tracker-local.md](./issue-tracker-local.md) — local-markdown issue tracker - [triage-labels.md](./triage-labels.md) — label mapping (only if `triage` is installed) - [domain.md](./domain.md) — domain doc consumer rules + layout diff --git a/.agents/skills/setup-matt-pocock-skills/issue-tracker-gitea.md b/.agents/skills/setup-matt-pocock-skills/issue-tracker-gitea.md new file mode 100644 index 0000000..0298bf9 --- /dev/null +++ b/.agents/skills/setup-matt-pocock-skills/issue-tracker-gitea.md @@ -0,0 +1,48 @@ +# Issue tracker: Gitea + +Issues and specs for this repo live as Gitea issues. Use the [`tea`](https://gitea.com/gitea/tea) CLI, called `tea-cli` on some systems. Record the instance URL, repository owner/name, installed command version, and supported operations when adapting this template. + +## Access and conventions + +Use the existing configured login and infer the repository from `git remote -v`. Check the installed binary's help before selecting commands: tea 1.0 changes the command groups, authentication, flags, and output formats. The examples here use `tea-cli` 0.9.2; options precede positional issue or PR numbers. + +- **Authenticate**: use the existing login; for a new login, run interactive `tea-cli login add` with the repository's instance URL. +- **Create an issue**: `tea-cli issues create --title "..." --description "..." --labels "needs-triage"`. Pass multiline descriptions as one quoted argument. +- **Read an issue**: `tea-cli issues --comments `. +- **List issues**: `tea-cli issues --state open --labels "..." --fields index,title,body,state,labels,assignees,url --output yaml`. Paginate with `--page` and `--limit` until all matching issues have been read. +- **Comment**: `tea-cli comment "..."`. +- **Close**: post the explanation first, then `tea-cli issues close `. +- **Pull requests**: `tea-cli pulls create --base --title "..." --description "..."`, `tea-cli pulls --comments `, and `tea-cli pulls --state open --output yaml`. +- **Milestones**: `tea-cli milestones --state all --fields id,title --output tsv`. Verify migrated milestone IDs rather than copying source-tracker IDs. + +This version has no JSON output, issue-edit command, or `api` command. Structured output flags apply to lists; detail views render for display. For unsupported operations, use the instance's `/api/swagger` explorer and `/swagger.v1.json` schema, or the Gitea UI. Authenticate API requests with an authorized token without displaying or committing it. API paths below are relative to the instance's `/api/v1`: + +- Read issue details and comments with `GET /repos///issues/` and its `/comments` endpoint; paginate comments. +- Resolve label IDs with `GET /repos///labels`. Add labels with `POST /repos///issues//labels`, body `{"labels":[]}`; remove one with `DELETE` on `/labels/`. Preserve unrelated labels. +- Edit a body or assignment with `PATCH /repos///issues/`, body `{"body":"..."}` or `{"assignees":[""]}`. Read current assignees before updating the list. +- Read a PR diff with `GET /repos///pulls/.diff`. + +## Pull requests as a triage surface + +**PRs as a request surface: no.** _(Set to `yes` if this repo treats external pull requests as feature requests; `/triage` reads this flag.)_ + +When enabled, read and list with `tea-cli pulls`; keep only external requests after checking collaborator or organization membership. Use `tea-cli comment`, the issue-label API, and `tea-cli pulls close ` for comment / label / close operations. + +Resolve bare `#` references by checking the resource kind with `tea-cli issues --kind all --fields index,kind,title,url --output yaml` or the issue API's `pull_request` field. Issue URLs use `/issues/`; PR URLs use `/pulls/`. + +## When a skill says "publish to the issue tracker" + +Create a Gitea issue with `tea-cli issues create`. + +## When a skill says "fetch the relevant ticket" + +Run `tea-cli issues --comments ` and read its labels and assignees. + +## Wayfinding operations + +- **Map**: an issue labelled `wayfinder:map`, holding the Notes / Decisions-so-far / Fog body. Create it with `tea-cli issues create --title "..." --description "..." --labels "wayfinder:map"`. +- **Child ticket**: an issue with `Part of #` at the top of its description, labels `wayfinder:` (`research`/`prototype`/`grilling`/`task`), and an ordered link in the map's body. +- **Blocking**: `POST /repos///issues//dependencies`, body `{"owner":"","repo":"","index":}`. `GET` lists blockers; `DELETE` with the same body removes one. Where native dependencies are unavailable, use `Blocked by: #, #` at the top of the description. Every blocker must be closed before the ticket is unblocked. +- **Frontier query**: list all open children with bodies and assignees, drop assigned tickets and those with an open native or description-line blocker; first in map order wins. +- **Claim**: assign the authenticated username through the issue API or Gitea UI — the session's first write. +- **Resolve**: comment with `tea-cli comment`, close with `tea-cli issues close`, and update the map's Decisions-so-far through the issue API or Gitea UI. diff --git a/.agents/skills/wizard/SKILL.md b/.agents/skills/wizard/SKILL.md index 74a5454..ca9e297 100644 --- a/.agents/skills/wizard/SKILL.md +++ b/.agents/skills/wizard/SKILL.md @@ -19,7 +19,7 @@ A wizard is ephemeral by default — built for one run, saved to a scratch or `s Work out every manual step the human must take and every value that gets captured along the way. Read the repo first — don't ask cold: -- For setup: configuration examples, README, compose/framework configuration, and the actual CI files (this repository uses `.gitlab-ci.yml`). Inspect secret names and references without displaying existing secret values. Include only values needed for the requested procedure, not every variable in the repository. +- For setup: configuration examples, README, compose/framework configuration, and the actual CI files. This repository is hosted on Gitea; read the README's migration status, `.gitea/workflows/` when present, and the preserved `.gitlab-ci.yml` while conversion is pending. Inspect secret names and references without displaying existing secret values. Include only values needed for the requested procedure, not every variable in the repository. - For a migration or transition: the current state, the target state, and the irreversible actions between them. Then show the user the ordered list of stages and the values each produces, and confirm — they may add, drop, or reorder. diff --git a/.antigravityrules b/.antigravityrules index a3e44b1..501a40a 100644 --- a/.antigravityrules +++ b/.antigravityrules @@ -6,7 +6,8 @@ All AI agents (including Cline, Antigravity, Cursor, and Copilot) must adhere to - The overall project code coverage (Statements, Lines, and Functions) must be maintained at **80% or higher**. - Verify coverage by running: ```bash - bun run test --watch=false --coverage + bun scripts/generate-langs.js + NODE_OPTIONS=--max-old-space-size=2048 bunx vitest run --coverage --maxWorkers=1 --exclude='src/app/benchmark/**' ``` - If your changes introduce new code or modify existing code in a way that drops the coverage below 80%, you must write appropriate unit tests in `.spec.ts` files to bring it back up. @@ -24,10 +25,11 @@ All AI agents (including Cline, Antigravity, Cursor, and Copilot) must adhere to bun run build ``` -4. **GitLab Pipeline Checks**: - - You must execute the local equivalent of the GitLab CI/CD pipeline steps before completing your task. All of the following commands must pass: +4. **CI Checks**: + - You must execute the local validation commands before completing your task. CI conversion to Gitea Actions is tracked in issue #268; the preserved `.gitlab-ci.yml` is a migration reference, and local checks do not satisfy Gitea's migration gate. All of the following commands must pass: - **Linting check**: `bun run lint` (or use `bun run lint:fix` to resolve auto-fixable issues) - **Formatting check**: `bun run format:check` - - **TypeScript Type check**: `bunx tsc --noEmit` - - **Unit Tests and Coverage**: `bun run test --watch=false --coverage` + - **TypeScript Type check**: `bunx tsc --noEmit -p tsconfig.app.json` and `bunx tsc --noEmit -p tsconfig.spec.json` + - **Unit Tests and Coverage**: generate the language registry, then run the coverage command in rule 1, matching the preserved functional-test job. - **Production Build**: `bun run build -- --configuration production` + - The separate performance benchmark remains advisory while issue #78 is open. Run it outside coverage with `NODE_OPTIONS=--max-old-space-size=2048 bunx vitest run src/app/benchmark/leave-planner-benchmark.spec.ts --maxWorkers=1` when verifying performance; see `docs/benchmark/README.md`. diff --git a/.scratch/jours-deja-poses/issues/01-saisir-sauvegarder-et-figer-les-jours-deja-poses.md b/.scratch/jours-deja-poses/issues/01-saisir-sauvegarder-et-figer-les-jours-deja-poses.md index 46f8c3d..5c9a577 100644 --- a/.scratch/jours-deja-poses/issues/01-saisir-sauvegarder-et-figer-les-jours-deja-poses.md +++ b/.scratch/jours-deja-poses/issues/01-saisir-sauvegarder-et-figer-les-jours-deja-poses.md @@ -6,9 +6,9 @@ **Status:** ready-for-agent -**GitLab:** [#61](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/61) +**Gitea:** [#61](https://gitea.nessar.fr/nessar/vac-optimizer/issues/61) -Source : [issue #13](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/13), entretien et spécification de développement. Respecter le glossaire du domaine et les ADR 0002, 0005, 0006 et 0007. +Source : [issue #13](https://gitea.nessar.fr/nessar/vac-optimizer/issues/13), entretien et spécification de développement. Respecter le glossaire du domaine et les ADR 0002, 0005, 0006 et 0007. - [ ] Un mode explicite « Saisir les jours déjà posés » présente l’horizon actuellement choisi et permet de sélectionner CP, RTT ou Autre. Autre couvre toutes les autres raisons de ne pas travailler ; ANY reste uniquement un sélecteur de règle. - [ ] Un clic sur une date admissible ajoute le type sélectionné ; un deuxième clic avec ce type supprime la déclaration ; un clic avec un autre type la remplace. Une date porte au maximum une déclaration. diff --git a/.scratch/jours-deja-poses/issues/02-optimiser-les-periodes-de-repos-autour-des-jours-declares.md b/.scratch/jours-deja-poses/issues/02-optimiser-les-periodes-de-repos-autour-des-jours-declares.md index 930ed0c..fb0e416 100644 --- a/.scratch/jours-deja-poses/issues/02-optimiser-les-periodes-de-repos-autour-des-jours-declares.md +++ b/.scratch/jours-deja-poses/issues/02-optimiser-les-periodes-de-repos-autour-des-jours-declares.md @@ -4,13 +4,13 @@ **Blocked by:** -- 01 — Saisir, sauvegarder et figer les jours déjà posés ([#61](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/61)). +- 01 — Saisir, sauvegarder et figer les jours déjà posés ([#61](https://gitea.nessar.fr/nessar/vac-optimizer/issues/61)). **Status:** ready-for-agent -**GitLab:** [#62](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/62) +**Gitea:** [#62](https://gitea.nessar.fr/nessar/vac-optimizer/issues/62) -Source : [issue #13](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/13), entretien et spécification de développement. Respecter les définitions de période de repos, gain en jours non travaillés, séquence de travail et semaine de jour férié du glossaire, ainsi que les ADR 0006 et 0007. +Source : [issue #13](https://gitea.nessar.fr/nessar/vac-optimizer/issues/13), entretien et spécification de développement. Respecter les définitions de période de repos, gain en jours non travaillés, séquence de travail et semaine de jour férié du glossaire, ainsi que les ADR 0006 et 0007. - [ ] Un vendredi ordinaire déclaré Autre, sans solde ni règle, produit une période vendredi–dimanche de trois jours. Cette période existe sans nouveau placement et ne provoque aucun débit. - [ ] Les déclarations, nouveaux placements, week-ends et jours fériés adjacents forment des périodes contiguës fusionnées. Chaque date contribue une seule fois à leur durée ; l’origine et le type des déclarations restent distincts des placements. diff --git a/.scratch/jours-deja-poses/issues/03-compter-les-jours-declares-dans-les-regles-de-periode.md b/.scratch/jours-deja-poses/issues/03-compter-les-jours-declares-dans-les-regles-de-periode.md index 6337e74..e1c8fda 100644 --- a/.scratch/jours-deja-poses/issues/03-compter-les-jours-declares-dans-les-regles-de-periode.md +++ b/.scratch/jours-deja-poses/issues/03-compter-les-jours-declares-dans-les-regles-de-periode.md @@ -4,13 +4,13 @@ **Blocked by:** -- 01 — Saisir, sauvegarder et figer les jours déjà posés ([#61](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/61)). +- 01 — Saisir, sauvegarder et figer les jours déjà posés ([#61](https://gitea.nessar.fr/nessar/vac-optimizer/issues/61)). **Status:** ready-for-agent -**GitLab:** [#63](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/63) +**Gitea:** [#63](https://gitea.nessar.fr/nessar/vac-optimizer/issues/63) -Source : [issue #13](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/13), entretien et spécification de développement. Respecter les quantités, fenêtres inclusives, obligations conjointes, priorités et contributions partagées du glossaire, ainsi que l’ADR 0007. +Source : [issue #13](https://gitea.nessar.fr/nessar/vac-optimizer/issues/13), entretien et spécification de développement. Respecter les quantités, fenêtres inclusives, obligations conjointes, priorités et contributions partagées du glossaire, ainsi que l’ADR 0007. - [ ] Dans une semaine ordinaire, avec quatre CP restants, un mercredi déclaré CP et une obligation de cinq CP du lundi au vendredi, le calcul ajoute quatre CP et débite uniquement ces quatre jours. - [ ] Les déclarations compatibles contribuent aux obligations exactes et aux préférences demandant jusqu’à une quantité donnée, dans l’intersection entre la fenêtre inclusive de la règle et l’horizon soumis. Une déclaration extérieure à ces limites ne contribue pas à la règle. diff --git a/.scratch/jours-deja-poses/issues/04-appliquer-les-motifs-if-then-et-les-droits-acquis.md b/.scratch/jours-deja-poses/issues/04-appliquer-les-motifs-if-then-et-les-droits-acquis.md index f5dd9db..db56be3 100644 --- a/.scratch/jours-deja-poses/issues/04-appliquer-les-motifs-if-then-et-les-droits-acquis.md +++ b/.scratch/jours-deja-poses/issues/04-appliquer-les-motifs-if-then-et-les-droits-acquis.md @@ -4,14 +4,14 @@ **Blocked by:** -- 02 — Optimiser les périodes de repos autour des jours déclarés ([#62](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/62)). -- 03 — Compter les jours déclarés dans les règles de période ([#63](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/63)). +- 02 — Optimiser les périodes de repos autour des jours déclarés ([#62](https://gitea.nessar.fr/nessar/vac-optimizer/issues/62)). +- 03 — Compter les jours déclarés dans les règles de période ([#63](https://gitea.nessar.fr/nessar/vac-optimizer/issues/63)). **Status:** ready-for-agent -**GitLab:** [#64](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/64) +**Gitea:** [#64](https://gitea.nessar.fr/nessar/vac-optimizer/issues/64) -Source : [issue #13](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/13), entretien et spécification de développement. Respecter les occurrences et modes IF_THEN, les droits acquis et l’ordre des objectifs du glossaire, ainsi que les ADR sur les artefacts du même calcul et l’ADR 0007. +Source : [issue #13](https://gitea.nessar.fr/nessar/vac-optimizer/issues/13), entretien et spécification de développement. Respecter les occurrences et modes IF_THEN, les droits acquis et l’ordre des objectifs du glossaire, ainsi que les ADR sur les artefacts du même calcul et l’ADR 0007. - [ ] Les motifs IF_THEN utilisent les véritables jours fériés français nationaux et les modes before, after, around et auto existants. Une déclaration ne crée pas une occurrence de jour férié et ne permet pas de déplacer le motif hors de ses limites admissibles. - [ ] Une déclaration compatible occupe sa position normale dans le motif et réduit le nombre de nouveaux placements nécessaires. Une déclaration incompatible ne peut être retypée ou déplacée, ni être sautée pour reporter la position demandée sur un jour plus éloigné. Les obligations restent obligatoires pour chaque occurrence ; les préférences conservent leur exigence de motif complet et leurs priorités. diff --git a/.scratch/plan-statistics/issues/01-open-plan-statistics-for-calculated-leave-usage.md b/.scratch/plan-statistics/issues/01-open-plan-statistics-for-calculated-leave-usage.md index 8d34a58..705ebd0 100644 --- a/.scratch/plan-statistics/issues/01-open-plan-statistics-for-calculated-leave-usage.md +++ b/.scratch/plan-statistics/issues/01-open-plan-statistics-for-calculated-leave-usage.md @@ -6,9 +6,9 @@ **Status:** ready-for-agent -**GitLab:** [#65](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/65) +**Gitea:** [#65](https://gitea.nessar.fr/nessar/vac-optimizer/issues/65) -Source: the agreed Plan Statistics Popup spec for [#3](https://gitlab.nessar.fr/nessar/vac-optimizer/-/issues/3) and [#29](https://gitlab.nessar.fr/nessar/vac-optimizer/-/issues/29), in milestone %3: V1 stats. Follow the domain glossary and ADRs 0002, 0004, 0006, and 0007. +Source: the agreed Plan Statistics Popup spec for [#3](https://gitea.nessar.fr/nessar/vac-optimizer/issues/3) and [#29](https://gitea.nessar.fr/nessar/vac-optimizer/issues/29), in milestone V1 stats. Follow the domain glossary and ADRs 0002, 0004, 0006, and 0007. - [ ] A labelled calendar control opens one statistics popup for the latest calculated valid plan. Opening it runs no optimization and changes no planning data. - [ ] The popup shows the number of leave placement dates with an explicit leave-day label. Declared non-working days consume no balance and are excluded from this count. A valid plan with no placements displays 0 and still permits opening the popup. diff --git a/.scratch/plan-statistics/issues/02-show-work-sequence-and-time-off-period-lengths.md b/.scratch/plan-statistics/issues/02-show-work-sequence-and-time-off-period-lengths.md index a14f9c0..35a4f27 100644 --- a/.scratch/plan-statistics/issues/02-show-work-sequence-and-time-off-period-lengths.md +++ b/.scratch/plan-statistics/issues/02-show-work-sequence-and-time-off-period-lengths.md @@ -5,13 +5,13 @@ **Blocked by:** - 01 — Open plan statistics for calculated leave usage. -- [#62 — Optimiser les périodes de repos autour des jours déclarés](https://gitlab.nessar.fr/nessar/vac-optimizer/-/issues/62), which establishes time-off periods and work sequences that include declared non-working days. +- [#62 — Optimiser les périodes de repos autour des jours déclarés](https://gitea.nessar.fr/nessar/vac-optimizer/issues/62), which establishes time-off periods and work sequences that include declared non-working days. **Status:** ready-for-agent -**GitLab:** [#66](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/66) +**Gitea:** [#66](https://gitea.nessar.fr/nessar/vac-optimizer/issues/66) -Source: the agreed Plan Statistics Popup spec for [#3](https://gitlab.nessar.fr/nessar/vac-optimizer/-/issues/3) and [#29](https://gitlab.nessar.fr/nessar/vac-optimizer/-/issues/29), including [#7](https://gitlab.nessar.fr/nessar/vac-optimizer/-/issues/7). The existing longest work-sequence metric from #28 is reused. Follow the domain glossary and ADRs 0004, 0006, and 0007. +Source: the agreed Plan Statistics Popup spec for [#3](https://gitea.nessar.fr/nessar/vac-optimizer/issues/3) and [#29](https://gitea.nessar.fr/nessar/vac-optimizer/issues/29), including [#7](https://gitea.nessar.fr/nessar/vac-optimizer/issues/7). The existing longest work-sequence metric from #28 is reused. Follow the domain glossary and ADRs 0004, 0006, and 0007. - [ ] Add five labelled metrics: non-working-day gain, average work-sequence length, longest work-sequence length, average time-off period length, and longest time-off period length. Work lengths use working days; break lengths use calendar days. - [ ] The work-sequence average includes every non-empty sequence inside the submitted horizon, including both edges. Weekends and French public holidays neither count nor split a sequence; leave placements and declared non-working days interrupt it. Consecutive days off introduce no zero-length samples. diff --git a/.scratch/plan-statistics/issues/03-show-gross-earned-leave-by-generating-rule.md b/.scratch/plan-statistics/issues/03-show-gross-earned-leave-by-generating-rule.md index 4d3448f..de74114 100644 --- a/.scratch/plan-statistics/issues/03-show-gross-earned-leave-by-generating-rule.md +++ b/.scratch/plan-statistics/issues/03-show-gross-earned-leave-by-generating-rule.md @@ -5,13 +5,13 @@ **Blocked by:** - 01 — Open plan statistics for calculated leave usage. -- [#64 — Appliquer les motifs IF_THEN et les droits acquis aux jours déclarés](https://gitlab.nessar.fr/nessar/vac-optimizer/-/issues/64), which establishes finalized earned entitlements and the fixed Europe/Paris calculation-date cutoff. +- [#64 — Appliquer les motifs IF_THEN et les droits acquis aux jours déclarés](https://gitea.nessar.fr/nessar/vac-optimizer/issues/64), which establishes finalized earned entitlements and the fixed Europe/Paris calculation-date cutoff. **Status:** ready-for-agent -**GitLab:** [#67](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/67) +**Gitea:** [#67](https://gitea.nessar.fr/nessar/vac-optimizer/issues/67) -Source: the agreed Plan Statistics Popup spec for [#3](https://gitlab.nessar.fr/nessar/vac-optimizer/-/issues/3) and [#29](https://gitlab.nessar.fr/nessar/vac-optimizer/-/issues/29), including [#8](https://gitlab.nessar.fr/nessar/vac-optimizer/-/issues/8). Follow the domain glossary and ADRs 0004, 0006, and 0007. +Source: the agreed Plan Statistics Popup spec for [#3](https://gitea.nessar.fr/nessar/vac-optimizer/issues/3) and [#29](https://gitea.nessar.fr/nessar/vac-optimizer/issues/29), including [#8](https://gitea.nessar.fr/nessar/vac-optimizer/issues/8). Follow the domain glossary and ADRs 0004, 0006, and 0007. - [ ] Display gross earned leave from every applicable generating rule, including Samedi Malin, with a per-rule breakdown whose quantities sum to the total. - [ ] A plan earning 3 days and consuming 2 reports 3 earned days. Fully consumed earned entitlements remain included even when absent from remaining balances; generating a future entitlement does not require consuming it inside the horizon. diff --git a/.scratch/plan-statistics/issues/04-count-public-holidays-connected-to-a-weekend.md b/.scratch/plan-statistics/issues/04-count-public-holidays-connected-to-a-weekend.md index c4fb7ab..0d09f71 100644 --- a/.scratch/plan-statistics/issues/04-count-public-holidays-connected-to-a-weekend.md +++ b/.scratch/plan-statistics/issues/04-count-public-holidays-connected-to-a-weekend.md @@ -5,13 +5,13 @@ **Blocked by:** - 01 — Open plan statistics for calculated leave usage. -- [#62 — Optimiser les périodes de repos autour des jours déclarés](https://gitlab.nessar.fr/nessar/vac-optimizer/-/issues/62), which provides shared time-off periods including declared non-working days and adjacent context dates. +- [#62 — Optimiser les périodes de repos autour des jours déclarés](https://gitea.nessar.fr/nessar/vac-optimizer/issues/62), which provides shared time-off periods including declared non-working days and adjacent context dates. **Status:** ready-for-agent -**GitLab:** [#68](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/68) +**Gitea:** [#68](https://gitea.nessar.fr/nessar/vac-optimizer/issues/68) -Source: the agreed Plan Statistics Popup spec for [#3](https://gitlab.nessar.fr/nessar/vac-optimizer/-/issues/3) and [#29](https://gitlab.nessar.fr/nessar/vac-optimizer/-/issues/29), including [#9](https://gitlab.nessar.fr/nessar/vac-optimizer/-/issues/9). Follow the domain glossary and ADRs 0004, 0006, and 0007. +Source: the agreed Plan Statistics Popup spec for [#3](https://gitea.nessar.fr/nessar/vac-optimizer/issues/3) and [#29](https://gitea.nessar.fr/nessar/vac-optimizer/issues/29), including [#9](https://gitea.nessar.fr/nessar/vac-optimizer/issues/9). Follow the domain glossary and ADRs 0004, 0006, and 0007. - [ ] Show the number of distinct Monday-to-Friday French public-holiday dates in planned time-off periods containing at least one Saturday or Sunday. Each qualifying period contains at least one leave placement or declared non-working day. - [ ] Count direct Monday/Friday connections and connections through leave, such as a Tuesday holiday joined to a weekend by Monday off. Declared non-working days can provide the same connection without consuming a balance. diff --git a/.scratch/plan-statistics/issues/05-warn-about-weeks-with-one-workday.md b/.scratch/plan-statistics/issues/05-warn-about-weeks-with-one-workday.md index 7ac4eea..9a034e5 100644 --- a/.scratch/plan-statistics/issues/05-warn-about-weeks-with-one-workday.md +++ b/.scratch/plan-statistics/issues/05-warn-about-weeks-with-one-workday.md @@ -5,13 +5,13 @@ **Blocked by:** - 01 — Open plan statistics for calculated leave usage. -- [#61 — Saisir, sauvegarder et figer les jours déjà posés](https://gitlab.nessar.fr/nessar/vac-optimizer/-/issues/61), which carries fixed declared non-working days with the producing calculation and its outcomes. +- [#61 — Saisir, sauvegarder et figer les jours déjà posés](https://gitea.nessar.fr/nessar/vac-optimizer/issues/61), which carries fixed declared non-working days with the producing calculation and its outcomes. **Status:** ready-for-agent -**GitLab:** [#69](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/69) +**Gitea:** [#69](https://gitea.nessar.fr/nessar/vac-optimizer/issues/69) -Source: the agreed Plan Statistics Popup spec for [#3](https://gitlab.nessar.fr/nessar/vac-optimizer/-/issues/3) and [#29](https://gitlab.nessar.fr/nessar/vac-optimizer/-/issues/29), including the clarification that working only one day in a full week is undesirable. Follow the domain glossary and ADRs 0004, 0006, and 0007. +Source: the agreed Plan Statistics Popup spec for [#3](https://gitea.nessar.fr/nessar/vac-optimizer/issues/3) and [#29](https://gitea.nessar.fr/nessar/vac-optimizer/issues/29), including the clarification that working only one day in a full week is undesirable. Follow the domain glossary and ADRs 0004, 0006, and 0007. - [ ] Count Monday-to-Sunday calendar weeks whose five Monday-to-Friday dates all lie inside the submitted half-open horizon and that contain exactly one remaining working day after excluding French public holidays, leave placements, and declared non-working days. - [ ] Four weekdays off and one remaining workday qualify. Weeks with zero or two remaining workdays do not qualify, including two-workday weeks containing separate one-day work sequences. diff --git a/.scratch/regles-optimisation/issues/01-unifier-evaluation-et-comparaison-des-objectifs.md b/.scratch/regles-optimisation/issues/01-unifier-evaluation-et-comparaison-des-objectifs.md index c5ec832..05b4257 100644 --- a/.scratch/regles-optimisation/issues/01-unifier-evaluation-et-comparaison-des-objectifs.md +++ b/.scratch/regles-optimisation/issues/01-unifier-evaluation-et-comparaison-des-objectifs.md @@ -1,6 +1,6 @@ # 01 — Unifier l’évaluation et la comparaison des objectifs -**GitLab:** [#70](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/70) +**Gitea:** [#70](https://gitea.nessar.fr/nessar/vac-optimizer/issues/70) **What to build:** Le planificateur conserve ses résultats actuels pendant une préparation qui rend les six objectifs évaluables à partir de configurations de règles. Le contrat commun permet ensuite aux règles fournies et aux règles personnelles d’utiliser les mêmes mesures, sans dépendre de leur nom ou de leur identité. diff --git a/.scratch/regles-optimisation/issues/02-piloter-prevention-des-pertes-depuis-les-regles.md b/.scratch/regles-optimisation/issues/02-piloter-prevention-des-pertes-depuis-les-regles.md index 5347e9d..f05786c 100644 --- a/.scratch/regles-optimisation/issues/02-piloter-prevention-des-pertes-depuis-les-regles.md +++ b/.scratch/regles-optimisation/issues/02-piloter-prevention-des-pertes-depuis-les-regles.md @@ -1,6 +1,6 @@ # 02 — Piloter la prévention des pertes depuis les règles -**GitLab:** [#71](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/71) +**Gitea:** [#71](https://gitea.nessar.fr/nessar/vac-optimizer/issues/71) **What to build:** L’utilisateur crée une règle d’optimisation de prévention des pertes, l’enregistre, la déplace parmi ses préférences et constate son effet sur les congés placés et les soldes restants. La désactiver retire réellement sa priorité automatique. diff --git a/.scratch/regles-optimisation/issues/03-composer-regles-semaines-feriees-et-repos.md b/.scratch/regles-optimisation/issues/03-composer-regles-semaines-feriees-et-repos.md index 52d02ad..52fe7a0 100644 --- a/.scratch/regles-optimisation/issues/03-composer-regles-semaines-feriees-et-repos.md +++ b/.scratch/regles-optimisation/issues/03-composer-regles-semaines-feriees-et-repos.md @@ -1,6 +1,6 @@ # 03 — Composer les règles de semaines fériées et de repos -**GitLab:** [#72](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/72) +**Gitea:** [#72](https://gitea.nessar.fr/nessar/vac-optimizer/issues/72) **What to build:** L’utilisateur crée et règle les préférences « Compléter les semaines avec un jour férié » et « Profiter des week-ends et jours fériés », puis choisit laquelle prime dans le planning et dans ses explications. diff --git a/.scratch/regles-optimisation/issues/04-composer-regles-sequences-de-travail.md b/.scratch/regles-optimisation/issues/04-composer-regles-sequences-de-travail.md index 1cacbd2..939f5e2 100644 --- a/.scratch/regles-optimisation/issues/04-composer-regles-sequences-de-travail.md +++ b/.scratch/regles-optimisation/issues/04-composer-regles-sequences-de-travail.md @@ -1,6 +1,6 @@ # 04 — Composer les règles de séquences de travail -**GitLab:** [#73](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/73) +**Gitea:** [#73](https://gitea.nessar.fr/nessar/vac-optimizer/issues/73) **What to build:** L’utilisateur compose des préférences sur ses séquences de travail : réduire la plus longue séquence ou limiter le déficit des reprises courtes, avec un seuil configurable. Leur position parmi les autres préférences influence le planning. diff --git a/.scratch/regles-optimisation/issues/05-piloter-economie-des-jours-appoint.md b/.scratch/regles-optimisation/issues/05-piloter-economie-des-jours-appoint.md index c2accc5..4d16bed 100644 --- a/.scratch/regles-optimisation/issues/05-piloter-economie-des-jours-appoint.md +++ b/.scratch/regles-optimisation/issues/05-piloter-economie-des-jours-appoint.md @@ -1,6 +1,6 @@ # 05 — Piloter l’économie des jours d’appoint -**GitLab:** [#74](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/74) +**Gitea:** [#74](https://gitea.nessar.fr/nessar/vac-optimizer/issues/74) **What to build:** L’utilisateur ajoute une préférence « Économiser les jours d’appoint » et décide, par sa position, jusqu’où les améliorations du planning peuvent consommer des congés qui expirent après l’horizon. diff --git a/.scratch/regles-optimisation/issues/06-migrer-regles-sauvegardees-et-valider-ensemble.md b/.scratch/regles-optimisation/issues/06-migrer-regles-sauvegardees-et-valider-ensemble.md index a5229bd..5e1c59a 100644 --- a/.scratch/regles-optimisation/issues/06-migrer-regles-sauvegardees-et-valider-ensemble.md +++ b/.scratch/regles-optimisation/issues/06-migrer-regles-sauvegardees-et-valider-ensemble.md @@ -1,6 +1,6 @@ # 06 — Migrer les règles sauvegardées et valider le comportement fonctionnel -**GitLab:** [#75](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/75) +**Gitea:** [#75](https://gitea.nessar.fr/nessar/vac-optimizer/issues/75) Blocked by: #74 diff --git a/.scratch/remove-original-decision-trace/issues/01-remove-original-decision-trace.md b/.scratch/remove-original-decision-trace/issues/01-remove-original-decision-trace.md index 91efc6b..0cfa849 100644 --- a/.scratch/remove-original-decision-trace/issues/01-remove-original-decision-trace.md +++ b/.scratch/remove-original-decision-trace/issues/01-remove-original-decision-trace.md @@ -1,6 +1,6 @@ # 01 — Remove the original decision trace end to end -**GitLab:** [#76](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/76) +**Gitea:** [#76](https://gitea.nessar.fr/nessar/vac-optimizer/issues/76) ## What to build diff --git a/.scratch/remove-original-decision-trace/issues/02-verify-trace-free-planning.md b/.scratch/remove-original-decision-trace/issues/02-verify-trace-free-planning.md index 91d8973..98225c7 100644 --- a/.scratch/remove-original-decision-trace/issues/02-verify-trace-free-planning.md +++ b/.scratch/remove-original-decision-trace/issues/02-verify-trace-free-planning.md @@ -1,6 +1,6 @@ # 02 — Verify integrated planning after trace removal -**GitLab:** [#77](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/77) +**Gitea:** [#77](https://gitea.nessar.fr/nessar/vac-optimizer/issues/77) Blocked by: #76 @@ -24,4 +24,4 @@ The removal is agreed; its measured speedup is unresolved and is now evaluated i ## Blocked by -- #76 — Remove the original decision trace end to end (https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/76). +- #76 — Remove the original decision trace end to end (https://gitea.nessar.fr/nessar/vac-optimizer/issues/76). diff --git a/.scratch/remove-original-decision-trace/issues/03-verify-and-optimize-planning-benchmarks.md b/.scratch/remove-original-decision-trace/issues/03-verify-and-optimize-planning-benchmarks.md index 47fde21..4b06e09 100644 --- a/.scratch/remove-original-decision-trace/issues/03-verify-and-optimize-planning-benchmarks.md +++ b/.scratch/remove-original-decision-trace/issues/03-verify-and-optimize-planning-benchmarks.md @@ -1,6 +1,6 @@ # 03 — Verify and optimize planning to meet the benchmarks from #75 -**GitLab:** [#78](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/78) +**Gitea:** [#78](https://gitea.nessar.fr/nessar/vac-optimizer/issues/78) Blocked by: #75, #77 diff --git a/AGENTS.md b/AGENTS.md index b9dafad..0539ac5 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -2,7 +2,7 @@ ### Issue tracker -Issues and specs live in GitLab Issues; use `glab` for tracker operations. See `docs/agents/issue-tracker.md`. +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 @@ -14,11 +14,13 @@ This is a single-context repo using root `CONTEXT.md` and `docs/adr/`. See `docs ## GitFlow -- `develop` is the default integration branch; `main` contains releases. Start `feature/*` branches from the current `origin/develop` and target their MRs to `develop`. -- Rebase working branches onto the latest `origin/develop` before opening or merging an MR. If `develop` advances, rebase and rerun the MR pipeline before merging. -- Integrate through MRs with successful pipelines and Maintainer-only merges. 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 MR titles. -- Create `release/X.Y.Z` from `develop` and `hotfix/X.Y.Z` from `main`. Only `release/*` and `hotfix/*` MRs target `main`. Merge each release or hotfix into both `main` and `develop`, keeping its branch until both MRs are merged. +- `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. +CI conversion is pending in Gitea issue #268. Actions are disabled and protected branches require `gitlab-to-gitea/ci-conversion-required`; local checks do not satisfy this gate. See [Continuous integration](README.md#continuous-integration). + Before preparing a release or hotfix, creating a tag, or changing image publication, read [GitFlow and releases](README.md#gitflow-and-releases) for package versions, explicit stable tags, and image promotion. diff --git a/README.md b/README.md index 8af5e29..c9b2ca0 100644 --- a/README.md +++ b/README.md @@ -2,6 +2,8 @@ VacOptimizer is a personal leave planner for turning dated leave balances into a deterministic plan around weekends and French public holidays. It handles mandatory rules, ordered preferences, earned leave, expiring balances, and interrupted calculations without relying on a backend solver. +Source code, issues, and pull requests are hosted on [Gitea](https://gitea.nessar.fr/nessar/vac-optimizer). The [issue-tracker guide](docs/agents/issue-tracker.md) documents `tea-cli` access and tracker conventions. + The planner answers these questions: - Is the request valid? @@ -164,7 +166,7 @@ The trace explorer navigates original phases and atomic decisions, expands candi - Vitest through the Angular test builder - ESLint and Prettier - Angular server build hosted by Express -- GitLab CI and a multi-stage Docker image +- Gitea repository hosting and a multi-stage Docker image The `/benchmark` route and planner core are lazy-loaded, so the normal application does not execute the benchmark or bundle the planner core into its main entry point. @@ -236,37 +238,43 @@ The image builds the Angular application with Bun and Node, then runs the genera ## Continuous integration -GitLab CI runs independent validation, test, build, security, and image stages: +CI execution is frozen after the migration to Gitea, and Gitea Actions is disabled. [Issue #268](https://gitea.nessar.fr/nessar/vac-optimizer/issues/268) tracks conversion of the preserved CI configuration to Gitea Actions. There is no checked-in `.gitea/workflows/` workflow yet. + +The preserved `.gitlab-ci.yml` defines validation, test, build, security, and image stages: - ESLint, Prettier, and TypeScript checks; - Vitest with coverage artifacts; - an optimized production build; -- GitLab SAST and Trivy filesystem scanning; +- legacy GitLab SAST and Trivy filesystem scanning; - GitFlow, Conventional Commit, and release-version checks; -- Docker image publication for every successful branch push, including branches with an open MR. +- Docker image publication for successful branch pushes and same-project reviews. -Pipelines switch to MR pipelines when a branch has an open MR, avoiding duplicate builds. Docker publication from MR pipelines is limited to detached pipelines within this project. Tag pipelines promote the already-built commit image instead of rebuilding it. +These definitions are migration inputs; they do not execute on Gitea. The policy script also still expects GitLab `CI_*` variables. Triggers, required checks, runner requirements, secrets, security scanning, image publication, and merge-message templates must be reviewed as part of #268 before the owner enables the converted workflow. Historical CI logs, reports, and downloadable artifacts were not imported; administrator rollback backups retain them. -The required `test` job runs application tests with coverage, one worker and a 2 GiB Node heap limit. A separate automatic `benchmark` job uses the same environment outside coverage instrumentation, with the unchanged five-minute timeout and protocol assertions. +In the preserved configuration, the required `test` job runs application tests with coverage, one worker and a 2 GiB Node heap limit. A separate `benchmark` job uses the same environment outside coverage instrumentation, with the unchanged five-minute timeout and protocol assertions. -At the user's request, the benchmark job has `allow_failure: true` while #78 is open, so benchmark failure does not block functional delivery. #78 must restore the required benchmark gate after the protocol passes. A green pipeline during this exception does not establish benchmark acceptance. +At the user's request, the preserved benchmark job has `allow_failure: true` while [#78](https://gitea.nessar.fr/nessar/vac-optimizer/issues/78) is open. Carry that advisory status into the converted workflow; #78 must restore the required benchmark gate after the protocol passes. Passing functional checks during this exception does not establish benchmark acceptance. + +Both protected branches require the unsatisfied status `gitlab-to-gitea/ci-conversion-required` until conversion is reviewed. Local validation does not satisfy this status; owner review and replacement of the migration gate are required before merges resume. See #268 for the migration requirements. ### GitFlow and releases -`develop` is the default integration branch. Create `feature/*` branches from it, rebase them onto the current `origin/develop` before opening or merging their MR, and merge into `develop` with a merge commit (`--no-ff`). Existing working-branch names such as `feat/*` follow the same rules. Working branches cannot merge `develop` into themselves instead of rebasing. +`develop` is the default integration branch. Create `feature/*` branches from it, rebase them onto the current `origin/develop` before opening or merging their PR, and merge into `develop` with a merge commit (`--no-ff`). Existing working-branch names such as `feat/*` follow the same rules. Working branches cannot merge `develop` into themselves instead of rebasing. -Create `release/X.Y.Z` from `develop` when the release scope is ready. Set `package.json` to `X.Y.Z` on this branch, stabilize it, then merge it into `main` and back into `develop`. Keep the release branch until both MRs have merged. A `hotfix/X.Y.Z` starts from `main`, changes the package version, and follows the same two-target merge process. Do not rebase `main`, `develop`, or a frozen release onto ongoing development. +Create `release/X.Y.Z` from `develop` when the release scope is ready. Set `package.json` to `X.Y.Z` on this branch, stabilize it, then merge it into `main` and back into `develop`. Keep the release branch until both PRs have merged. A `hotfix/X.Y.Z` starts from `main`, changes the package version, and follows the same two-target merge process. Do not rebase `main`, `develop`, or a frozen release onto ongoing development. -Use Conventional Commits for new commits and MR titles, for example `feat(calendar): add planning periods`, `fix(planner): handle expired balances`, or `chore(release): prepare 1.6.0`. Scopes are optional; `!` marks a breaking change. GitLab generates merge messages from the validated MR title. Legacy history is not rewritten. +Use Conventional Commits for new commits and PR titles, for example `feat(calendar): add planning periods`, `fix(planner): handle expired balances`, or `chore(release): prepare 1.6.0`. Scopes are optional; `!` marks a breaking change. The merge commit subject must preserve the validated PR title. Gitea supports a [Git-based merge-message template](https://docs.gitea.com/usage/issues-prs/merge-message-templates/) at `.gitea/default_merge_message/MERGE_TEMPLATE.md`, using `${PullRequestTitle}` and `${PullRequestReference}`. Its introduction and an example expanded message are part of #268; legacy history is not rewritten. + +The image tag contract to preserve during CI conversion is: | Trigger | Published image tags | | --- | --- | -| Successful push to any branch | `branch-` and `sha-` | +| Successful push to any branch | `branch-` and `sha-` | | Explicit release tag `vX.Y.Z` | `vX.Y.Z` and `latest`, using the existing SHA image | -For example, `feature/calendar` publishes `branch-feature-calendar`; integration publishes `branch-develop`. GitLab normalizes ref slugs to lowercase and truncates them to 63 bytes, so choose branch names with distinct slugs. Only valid release tags can update `latest`. +For example, `feature/calendar` uses `branch-feature-calendar`; integration uses `branch-develop`. Preserve the previous slug normalization: lowercase the branch name, replace characters other than `a-z` and `0-9` with `-`, truncate to 63 bytes, and remove leading/trailing `-`. Choose branch names with distinct slugs. Only valid release tags can update `latest`. Automatic image publication and tag promotion remain frozen until #268 is complete. -After the MR into `main` and its full pipeline have succeeded, tag the published main commit: +After CI conversion is complete, the PR into `main` has merged, and its full checks and SHA image publication have succeeded, tag the published main commit: ```bash git fetch origin @@ -274,11 +282,13 @@ git tag -a v1.6.0 origin/main -m "Release 1.6.0" git push origin v1.6.0 ``` -The tag must match the checked-out `package.json` version, use stable `vMAJOR.MINOR.PATCH` syntax, and point to a commit reachable from `main`. Wait for the main pipeline before tagging: the release job requires its `sha-` image. Tags do not increment the version automatically. +The tag must match the tagged commit's `package.json` version, use stable `vMAJOR.MINOR.PATCH` syntax, and point to a commit reachable from `main`. Wait for the main checks and image publication before tagging: promotion requires its `sha-` image. Tags do not increment the version automatically. -GitLab project settings must use `develop` as the default branch, the **Merge commit** method, squashing disabled, and **Pipelines must succeed** with skipped pipelines disallowed. Protect `main` and `develop` with no direct or forced pushes and Maintainer-only merges. Set the merge commit template to `%{title}` followed by the MR reference, preserving Conventional Commit subjects. The CI permits only `release/*` and `hotfix/*` into `main`; working MRs target `develop`. Rebase checks validate the target head at pipeline time: if `develop` advances afterward, rebase and rerun the MR pipeline before merging. +The Gitea repository policy requires `develop` as the default branch and **Merge commit** as the merge method, with squash and rebase merge methods disabled. Configure [branch protection](https://docs.gitea.com/usage/access-control/protected-branches/) for `main` and `develop` to disable direct and forced pushes, restrict the merge allowlist to designated maintainers, require successful status checks, and block outdated PRs. Administrators must follow the protection rules. Replace the migration gate with the reviewed check contexts only after #268 is complete. These are required settings; the migration does not establish that every setting has already been applied. -Run the policy integration check locally with `node scripts/ci-policy.test.mjs`. +Only `release/*` and `hotfix/*` PRs may target `main`; working PRs target `develop`. The converted CI must retain these rules and the rebase checks. If `develop` advances after validation, rebase and rerun the PR checks before merging. + +Run the preserved policy integration check locally with `node scripts/ci-policy.test.mjs`. It verifies the legacy policy adapter; it does not validate a Gitea workflow or satisfy the migration gate. ## Domain and design references diff --git a/docs/adr/0006-user-selected-horizons-and-cancellable-calculations.md b/docs/adr/0006-user-selected-horizons-and-cancellable-calculations.md index 24be004..beb0e60 100644 --- a/docs/adr/0006-user-selected-horizons-and-cancellable-calculations.md +++ b/docs/adr/0006-user-selected-horizons-and-cancellable-calculations.md @@ -1,6 +1,6 @@ # User-Selected Horizons and Cancellable Calculations -Accepted for [issue #12](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/12). Fixed, saved planning horizons are implemented by [issue #57](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/57); user cancellation with a retained valid plan and original trace is implemented by [issue #58](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/58); removal of the automatic calculation deadline and heartbeat-based worker liveness are implemented by [issue #59](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/59). The indicative duration estimate is implemented by [issue #60](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/60); its initial model, session-local refinement and calendar-rendering measurement are documented in [planning-duration.md](../planning-duration.md). +Accepted for [issue #12](https://gitea.nessar.fr/nessar/vac-optimizer/issues/12). Fixed, saved planning horizons are implemented by [issue #57](https://gitea.nessar.fr/nessar/vac-optimizer/issues/57); user cancellation with a retained valid plan and original trace is implemented by [issue #58](https://gitea.nessar.fr/nessar/vac-optimizer/issues/58); removal of the automatic calculation deadline and heartbeat-based worker liveness are implemented by [issue #59](https://gitea.nessar.fr/nessar/vac-optimizer/issues/59). The indicative duration estimate is implemented by [issue #60](https://gitea.nessar.fr/nessar/vac-optimizer/issues/60); its initial model, session-local refinement and calendar-rendering measurement are documented in [planning-duration.md](../planning-duration.md). `deadlineMs` remains an opt-in contract for technical callers: a finite non-negative planning-work budget with no ten-second cap. An omitted value is unlimited. It starts after calendar preparation and excludes trace capture, observer callbacks, and post-outcome artifact work. The calendar and benchmark omit it. A one-second worker heartbeat renews the coordinator's thirty-second inactivity timer during cooperative preparation and search; total elapsed time never triggers that timer while activity continues. Worker errors and unavailable execution retain their explicit outcomes, and monitoring ends when the outcome arrives so delayed trace delivery cannot invalidate it. diff --git a/docs/adr/0007-declared-days-and-reported-balances.md b/docs/adr/0007-declared-days-and-reported-balances.md index 2c54e77..b837b61 100644 --- a/docs/adr/0007-declared-days-and-reported-balances.md +++ b/docs/adr/0007-declared-days-and-reported-balances.md @@ -4,7 +4,7 @@ status: accepted # Declared Non-Working Days and Reported Leave Balances -For [issue #13](https://gitlab.nessar.fr/nessar/vac-optimizer/-/issues/13), users declare fixed non-working dates among normal working days, with a CP, RTT, or Other type; Other covers every other reason for not working. Reported balances already account for booked leave, so these declarations consume no remaining balance and cannot receive another placement; they count towards compatible planning rules, including rules that earn leave. +For [issue #13](https://gitea.nessar.fr/nessar/vac-optimizer/issues/13), users declare fixed non-working dates among normal working days, with a CP, RTT, or Other type; Other covers every other reason for not working. Reported balances already account for booked leave, so these declarations consume no remaining balance and cannot receive another placement; they count towards compatible planning rules, including rules that earn leave. Declared dates can form time-off periods without new leave placements, interrupt work sequences, and guide further optimization. Each calculation uses today's Europe/Paris calendar date, with reported balances assumed current as of that date: the planner adds only entitlements available strictly afterward, while earlier entitlements are already represented in the reported balances. This keeps existing bookings useful without debiting them again or asking users to manually add prospective gains; it relies on the user keeping reported balances current as the employer's system credits earned leave. diff --git a/docs/agents/issue-tracker.md b/docs/agents/issue-tracker.md index 95e49cb..8c366d5 100644 --- a/docs/agents/issue-tracker.md +++ b/docs/agents/issue-tracker.md @@ -1,46 +1,57 @@ -# Issue tracker: GitLab +# Issue tracker: Gitea -Issues and specs for this repo live as GitLab issues. Use the [`glab`](https://gitlab.com/gitlab-org/cli) CLI for all operations. +Issues and specs live in [nessar/vac-optimizer on Gitea](https://gitea.nessar.fr/nessar/vac-optimizer). Use the configured [`tea-cli`](https://gitea.com/gitea/tea) login for supported operations. + +## Access and command version + +The installed binary is `tea-cli` 0.9.2. Its commands below use the pre-1.0 interface; other installations may call the binary `tea`. Check `tea-cli --help` and subcommand help before using commands from another version. This version supports YAML, TSV, CSV, simple, and table output; it has no JSON output, issue-edit command, or `api` command. + +Run inside the clone so the CLI discovers the repository and login from `origin`. Use `--repo nessar/vac-optimizer` and `--login ` when an explicit selection is needed. Options go before positional issue or PR numbers. Existing authentication can be checked with `tea-cli whoami`; for a new login, use interactive `tea-cli login add` and select `https://gitea.nessar.fr`. ## Conventions -- **Create an issue**: `glab issue create --title "..." --description "..."`. Use a heredoc for multi-line descriptions. Pass `--description -` to open an editor. -- **Read an issue**: `glab issue view --comments`. Use `-F json` for machine-readable output. -- **List issues**: `glab issue list -F json` with appropriate `--label` filters. -- **Comment on an issue**: `glab issue note --message "..."`. GitLab calls comments "notes". -- **Apply / remove labels**: `glab issue update --label "..."` / `--unlabel "..."`. Multiple labels can be comma-separated or by repeating the flag. -- **Close**: `glab issue close `. `glab issue close` does not accept a closing comment, so post the explanation first with `glab issue note --message "..."`, then close. -- **Merge requests**: GitLab calls PRs "merge requests". Use `glab mr create`, `glab mr view`, `glab mr note`, etc. — the same shape as `gh pr ...` with `mr` in place of `pr` and `note`/`--message` in place of `comment`/`--body`. +- **Create an issue**: `tea-cli issues create --title "..." --description "..." --labels "needs-triage"`. Multiple labels or assignees are comma-separated. For multiline text, prepare a draft and pass its contents as one quoted description argument. +- **Read an issue**: `tea-cli issues --comments `. Detail views render for display even with `--output yaml`; use list output or the REST operations below for structured data. +- **List issues**: `tea-cli issues --state open --labels "needs-triage" --fields index,title,body,state,labels,assignees,url --output yaml`. Use `--page` and `--limit` to read all pages; the server may cap the requested page size. +- **Comment**: `tea-cli comment "..."`; this works for issues and PRs. +- **Apply / remove labels, edit a body, or assign**: use the Gitea UI or the REST operations below; this CLI version does not support these edits. Preserve unrelated labels and assignees. +- **Close**: post the explanation with `tea-cli comment "..."`, then run `tea-cli issues close `. +- **Create a pull request**: `tea-cli pulls create --base develop --title "docs: update Gitea documentation" --description "..."`. Read with `tea-cli pulls --comments `; list with `tea-cli pulls --state open --output yaml`. +- **List milestones**: `tea-cli milestones --state all --fields id,title --output tsv`. Issue numbers were preserved during migration, but milestone IDs changed; V1 stats is [milestone 13](https://gitea.nessar.fr/nessar/vac-optimizer/milestone/13). -Infer the repo from `git remote -v` — `glab` does this automatically when run inside a clone. +## REST operations for CLI gaps -## Merge requests as a triage surface +The instance's [API explorer](https://gitea.nessar.fr/api/swagger) and [schema](https://gitea.nessar.fr/swagger.v1.json) describe the supported endpoints. Paths below are relative to `https://gitea.nessar.fr/api/v1`; authenticate with an existing authorized Gitea API token without displaying or committing it. Check the installed CLI help first when it is upgraded. -**MRs as a request surface: no.** _(Set to `yes` if this repo treats external merge requests as feature requests; `/triage` reads this flag.)_ +- **Read full issue data or comments as JSON**: `GET /repos/nessar/vac-optimizer/issues/` and `GET /repos/nessar/vac-optimizer/issues//comments`. Paginate comment lists. +- **Find label IDs**: `GET /repos/nessar/vac-optimizer/labels`; paginate and match exact names from `triage-labels.md`. +- **Add labels**: `POST /repos/nessar/vac-optimizer/issues//labels` with `{"labels":[]}`. **Remove one label**: `DELETE /repos/nessar/vac-optimizer/issues//labels/`. These operations preserve other labels. +- **Edit a body or assign**: `PATCH /repos/nessar/vac-optimizer/issues/` with `{"body":"..."}` or `{"assignees":[""]}`. Read current assignees before updating the list. +- **Read a PR diff**: `GET /repos/nessar/vac-optimizer/pulls/.diff`. -When set to `yes`, MRs run through the same labels and states as issues, using the `glab mr` equivalents: +## Pull requests as a triage surface -- **Read an MR**: `glab mr view --comments` and `glab mr diff ` for the diff. -- **List external MRs for triage**: `glab mr list -F json`, then keep only MRs whose author is not a project member/owner (a contributor's MR, not a maintainer's in-flight work). -- **Comment / label / close**: `glab mr note`, `glab mr update --label`/`--unlabel`, `glab mr close`. +**PRs as a request surface: no.** _(Set to `yes` if this repo treats external pull requests as feature requests; `/triage` reads this flag.)_ -Unlike GitHub, GitLab numbers issues and MRs separately, so `#42` is unambiguous once you know which surface the maintainer means. +When enabled, use `tea-cli pulls --comments ` to read and `tea-cli pulls --state open --fields index,title,body,author,labels,url --output yaml` to list. Keep only external contributors' requests, checking repository collaborators or organization membership rather than guessing from the author's name. Comment with `tea-cli comment`, edit labels through the issue-label API, and close with `tea-cli pulls close `. + +For a bare `#`, check the resource kind: `tea-cli issues --kind all --fields index,kind,title,url --output yaml`, or inspect the issue API's `pull_request` field. PR URLs use `/pulls/`; issue URLs use `/issues/`. ## When a skill says "publish to the issue tracker" -Create a GitLab issue. +Create a Gitea issue with `tea-cli issues create`. ## When a skill says "fetch the relevant ticket" -Run `glab issue view --comments`. +Run `tea-cli issues --comments ` and read its labels and assignees. ## Wayfinding operations Used by `/wayfinder`. The **map** is a single issue with **child** issues as tickets. -- **Map**: a single issue labelled `wayfinder:map`, holding the Notes / Decisions-so-far / Fog body. `glab issue create --label wayfinder:map`. (On GitLab tiers with native epics, an epic may hold the map instead; a labelled issue works everywhere.) -- **Child ticket**: an issue carrying `Part of #` at the top of its description and labels `wayfinder:` (`research`/`prototype`/`grilling`/`task`). Once claimed, the ticket is assigned to the driving dev. -- **Blocking**: GitLab's **native blocking link** — the canonical, UI-visible representation. Add it with the `/blocked_by #` quick action, posted as a note (`glab issue note --message "/blocked_by #"`). Native blocking links are a Premium/Ultimate feature; on the free tier (or where unavailable) fall back to a `Blocked by: #, #` line at the top of the description. A ticket is unblocked when every blocker is closed. -- **Frontier query**: `glab issue list -F json` scoped to the map's children, drop any with an open blocker — a native `blocked_by` link to an open issue (`glab api projects/:id/issues/:iid/links`), or an open issue in the `Blocked by` line — or an assignee; first in map order wins. -- **Claim**: `glab issue update --assignee @me` — the session's first write. -- **Resolve**: `glab issue note --message ""`, then `glab issue close `, then append a context pointer (gist + link) to the map's Decisions-so-far. +- **Map**: create an issue labelled `wayfinder:map`, holding the Notes / Decisions-so-far / Fog body, with `tea-cli issues create --title "..." --description "..." --labels "wayfinder:map"`. +- **Child ticket**: an issue carrying `Part of #` at the top of its description and labels `wayfinder:` (`research`/`prototype`/`grilling`/`task`). Maintain the ordered child links in the map's body. Once claimed, the ticket is assigned to the driving dev. +- **Blocking**: use Gitea's native dependencies. `POST /repos/nessar/vac-optimizer/issues//dependencies` with `{"owner":"nessar","repo":"vac-optimizer","index":}` makes the child depend on that blocker. Read blockers with `GET` on the same path; use `DELETE` with the same body to remove a dependency. Where dependencies are unavailable, retain a `Blocked by: #, #` line at the top of the description. A ticket is unblocked when every blocker is closed. +- **Frontier query**: list the map's open children with `tea-cli issues --state open --fields index,title,body,assignees,labels --output yaml`, reading all pages. Drop tickets with an assignee or an open native dependency or description-line blocker; first in map order wins. +- **Claim**: assign the authenticated username through the issue `PATCH` endpoint or Gitea UI — the session's first write. +- **Resolve**: `tea-cli comment ""`, then `tea-cli issues close `, then append a context pointer (gist + link) to the map's Decisions-so-far through the issue `PATCH` endpoint or Gitea UI. diff --git a/docs/benchmark/README.md b/docs/benchmark/README.md index c0dccfd..90a5618 100644 --- a/docs/benchmark/README.md +++ b/docs/benchmark/README.md @@ -7,9 +7,9 @@ the benchmark fixtures. The latest full functional coverage run passes 652 tests across 34 files under the 2 GB Node heap limit, excluding the separate benchmark. This does not establish a passing performance protocol. -MR pipeline 320 passed all 652 functional tests in 109.43 seconds, then the -seven-scenario protocol timed out at its unchanged 300-second limit without an -out-of-memory failure. In an earlier diagnostic run, the loaded-year warm-up took +Before the Gitea migration, GitLab pipeline 320 passed all 652 functional tests +in 109.43 seconds, then the seven-scenario protocol timed out at its unchanged +300-second limit without an out-of-memory failure. In an earlier diagnostic run, the loaded-year warm-up took 184.36 seconds and its first measured repetition began about 251.78 seconds into the protocol. Those diagnostic timings precede the final period-projection cache and the planned original-decision-trace removal, and are not a result for either. @@ -19,12 +19,15 @@ verification. #78 owns benchmark verification and implementation of further optimizations when needed, after #76 removes tracing and #77 verifies the retained behavior. All seven scenarios, one warm-up and two measured repetitions per scenario, the 2 GB heap limit and the 300-second timeout remain required for #78. -At the user's request, CI runs the benchmark in a separate job with -`allow_failure: true` while #78 is open. Functional coverage tests and all other -required checks remain blocking. #78 must restore the required benchmark gate +At the user's request, the preserved CI configuration defines the benchmark in a +separate job with `allow_failure: true` while #78 is open. Functional coverage +tests and all other required checks remain blocking. #78 must restore the required benchmark gate after the unchanged protocol passes. A green pipeline during this exception does not establish a passing benchmark. No automatic elapsed-time planning -cutoff is introduced. +cutoff is introduced. CI execution is frozen and Gitea Actions is disabled pending +[issue #268](https://gitea.nessar.fr/nessar/vac-optimizer/issues/268); the separate +advisory benchmark job must be carried into the converted workflow. See the +[CI migration status](../../README.md#continuous-integration). The results below document earlier implementations and protocols. They are historical measurements rather than the performance result for composable rules. diff --git a/docs/planner-cancellation.md b/docs/planner-cancellation.md index 6945daf..442ebeb 100644 --- a/docs/planner-cancellation.md +++ b/docs/planner-cancellation.md @@ -1,6 +1,6 @@ # Cancelling a planning calculation -Issue [#58](https://gitlab.nessar.fr/nessar/vac-optimizer/-/work_items/58) implements the cancellation portion of ADR 0006. Issue #59 removes the automatic deadline while keeping the same cancellation and original-trace protocol. The duration estimate remains in issue #60. +Issue [#58](https://gitea.nessar.fr/nessar/vac-optimizer/issues/58) implements the cancellation portion of ADR 0006. Issue #59 removes the automatic deadline while keeping the same cancellation and original-trace protocol. The duration estimate remains in issue #60. `PlanningCalculationContext.cancel()` requests user cancellation once while its outcome is pending. `CalendarYear` keeps an accessible Cancel button visible during preparation, obligation search, and optimization. It announces the request, disables duplicate cancellation, and moves keyboard focus to the result heading when the outcome arrives. Cancellation never triggers Calculate. A subsequent explicit Calculate creates a fresh immutable calculation snapshot. diff --git a/docs/statistics.md b/docs/statistics.md index c05dd90..8139fc4 100644 --- a/docs/statistics.md +++ b/docs/statistics.md @@ -1,6 +1,6 @@ # Plan Statistics Popup -Local development draft for [issue #3](https://gitlab.nessar.fr/nessar/vac-optimizer/-/issues/3) and [issue #29](https://gitlab.nessar.fr/nessar/vac-optimizer/-/issues/29), within [milestone %3: V1 stats](https://gitlab.nessar.fr/nessar/vac-optimizer/-/milestones/3). The behavior below consolidates the decisions confirmed during grill-with-docs; proposals and remaining presentation choices are identified separately. +Local development draft for [issue #3](https://gitea.nessar.fr/nessar/vac-optimizer/issues/3) and [issue #29](https://gitea.nessar.fr/nessar/vac-optimizer/issues/29), within [milestone V1 stats](https://gitea.nessar.fr/nessar/vac-optimizer/milestone/13). The behavior below consolidates the decisions confirmed during grill-with-docs; proposals and remaining presentation choices are identified separately. ## Problem Statement