Commit Graph

1147 Commits

Author SHA1 Message Date
diegosouzapw
9788940f44 Merge PR #20253 (fix/release-v3.8.54-ci-job-ceilings) into merge train 3b
# Conflicts:
#	.github/workflows/ci.yml
2026-11-15 02:03:10 -03:00
diegosouzapw
5907c9028d Merge PR #20166 (feat/omni-queue) into merge train 3b 2026-11-15 02:02:01 -03:00
diegosouzapw
21a5f16608 Merge PR #20169 (feat/db-timestamp-migrations) into merge train 3b 2026-11-15 02:01:59 -03:00
diegosouzapw
a3fc79c9ab fix(ci): raise the unit shard and Coverage job ceilings
Both jobs were failing gates on time, with every test green.

Unit shard, 25 -> 35 min: over 72 green shard jobs on 2026-11-14 the mean
was 19 min and the slowest 24, and 19 of them (26%) ended within 3 min of
the limit. A shard whose steps had all passed was cancelled at 25 min
(run 43651743993) and failed Gate / CI until a re-run.

Coverage, 45 -> 60 min: two pull requests died at exactly 45 min on the
same day (runs 43619286507 and 43625515181); the re-run that passed took
39m45s.

The Release-Green observer comment that quotes the shard ceiling follows.
2026-11-15 00:42:32 -03:00
diegosouzapw
376e057697 Merge PR #20173 (feat/derived-strip-open-prs) into merge train 3 2026-11-14 19:36:13 -03:00
diegosouzapw
b8d756003e docs(db): credit 241_seen_models to #16864, not #18359
The LEGACY_MIGRATION_MAX comment said 241_seen_models.sql came from
#18359. It came from #16864, renumbered from 240 to 241 in merge train 2;
#18359 was stacked on #18353 and carries no migration of its own. The
commit that raised the freeze to 241 (d0ec9e8b) has the same slip in its
message.
2026-11-14 19:32:53 -03:00
diegosouzapw
8860c9a81c Merge branch 'feat/derived-i18n-release-mode' into feat/derived-generated-baselines
# Conflicts:
#	docs/architecture/QUALITY_GATES.md
#	tests/unit/docs/readme-cli-terminal-svg.test.ts
#	tests/unit/docs/readme-comparison-table-svg.test.ts
#	tests/unit/docs/readme-free-tier-budget-svg.test.ts
#	tests/unit/docs/readme-hero-svg.test.ts
#	tests/unit/docs/readme-promise-pillars-svg.test.ts
#	tests/unit/docs/readme-strategies-grid-svg.test.ts
#	tests/unit/docs/readme-tier-cascade-svg.test.ts
2026-11-14 18:40:27 -03:00
diegosouzapw
5f4f104b85 Merge commit 'd84062cc' into feat/derived-i18n-release-mode
# Conflicts:
#	docs/architecture/QUALITY_GATES.md
2026-11-14 18:38:33 -03:00
diegosouzapw
0733ec8463 Merge remote-tracking branch 'origin/chore/derived-p2-counts-out-of-instructions' into feat/derived-strip-open-prs 2026-11-14 18:36:06 -03:00
diegosouzapw
d84062cc9a Merge remote-tracking branch 'origin/feat/derived-p1-gate-modes' into chore/derived-p2-counts-out-of-instructions 2026-11-14 18:35:57 -03:00
diegosouzapw
a36f922c78 Merge remote-tracking branch 'origin/refactor/derived-p0-stryker-description' into feat/derived-p1-gate-modes
# Conflicts:
#	scripts/check/check-docs-counts-sync.mjs
2026-11-14 18:28:49 -03:00
diegosouzapw
4f086b0ad6 Merge remote-tracking branch 'origin/chore/derived-p2-counts-out-of-instructions' into feat/derived-strip-open-prs 2026-11-14 18:21:43 -03:00
diegosouzapw
ae8eae780e Merge remote-tracking branch 'origin/feat/derived-p1-gate-modes' into chore/derived-p2-counts-out-of-instructions 2026-11-14 18:21:04 -03:00
diegosouzapw
def9c8ce24 Merge branch 'feat/derived-i18n-release-mode' into feat/derived-generated-baselines
# Conflicts:
#	docs/diagrams/README.md
2026-11-14 18:16:50 -03:00
diegosouzapw
600d5811fd Merge remote-tracking branch 'origin/release/v3.8.54' into feat/db-timestamp-migrations 2026-11-14 18:13:59 -03:00
diegosouzapw
8f325a2bf7 Merge remote-tracking branch 'origin/release/v3.8.54' into feat/derived-p1-gate-modes 2026-11-14 18:12:46 -03:00
diegosouzapw
f27a2fba8b Merge remote-tracking branch 'origin/release/v3.8.54' into feat/derived-i18n-release-mode 2026-11-14 18:12:38 -03:00
diegosouzapw
410c8db3ae fix(ci): an omni-queue resume clears only the pause it saw
Follow-up to the review of the pause/resume confirmation. `resume` reported success as soon
as the base was unpaused, also when it already was, while its dispatch could still be
pending in the tick's concurrency group and later clear a pause recorded in between (a
safety pause). Now the CLI sends nothing for a base that is not paused, and a resume carries
the pause it saw (`expect-pause:<since>`); the tick clears only that pause. A second
dispatch of the same request is therefore harmless, which also covers a retry made after
another request's run was mistaken for ours. The existing test that pinned an empty resume
reason now pins the new format.
2026-11-14 15:50:15 -03:00
diegosouzapw
331616ff1f Merge remote-tracking branch 'origin/release/v3.8.54' into feat/omni-queue 2026-11-14 14:12:45 -03:00
diegosouzapw
90fbcaba31 Merge remote-tracking branch 'origin/release/v3.8.54' into refactor/derived-p0-stryker-description
# Conflicts:
#	stryker.conf.json
2026-11-14 14:03:37 -03:00
diegosouzapw
b5f13c6658 fix(ci): OpenAPI breaking-change gate resolves the base of an omni-queue candidate
The gate pins its comparison to the event's commits. A push that creates a branch has no
`before`, and every omni-queue candidate is such a push, so the gate ended INCOMPLETE
("Missing immutable event base") and the candidate went red: found by the real-repository
dry run of the candidate profile (run 43614500902). On refs/heads/omni-queue/** the base is
now the one the candidate names itself (Omni-Queue-Base, or the commit itself for a
base check), through candidate-base.resolveCandidateBase, which fails closed when the ref
does not name the commit. Every other push keeps event.before.
2026-11-14 13:39:55 -03:00
diegosouzapw
becdd677a1 fix(ci): omni-queue shadow mode skips the non-approver comment too
Shadow mode writes nothing on a pull request, but the approval job still posted its
"not an approver" comment. In shadow a label from a non-approver is now only logged.
The main() test that pins that comment hands main a live config (setup only; the
assertions are unchanged). The protected-surface comment and two doc comments now say
"protected surfaces": the list also covers workflows and the queue's own code and config.
2026-11-14 13:07:37 -03:00
diegosouzapw
3862c62bf4 Merge branch 'fix/oq-pre-tick' into feat/omni-queue 2026-11-14 13:03:08 -03:00
diegosouzapw
c18808c5ca fix(ci): omni-queue saves its state only when it changed, plus an hourly heartbeat
Every tick called store.save, and a save stamps `updatedAt`, so the
document always differed: one commit on `omni-queue-state` per tick, at
least 288 a day per base from the cron alone, although most ticks change
nothing (idle queue, candidate checks still pending).

The tick now compares the document it loaded with the one it ends with,
`updatedAt` aside, and skips the save when they are equal. An unchanged
state is still written as a heartbeat at most once per
STATE_HEARTBEAT_MINUTES (60, exported from tick.mjs), so the age of
`updatedAt` keeps telling an idle queue from a dead one. A missing
document is always written, and so is one whose `updatedAt` cannot be
read or lies in the future.

Why a skipped save is safe:

- Compare-and-swap. The CAS exists so that a write never overwrites a
  concurrent one. A tick with nothing to write cannot lose an update, and
  the version it loaded is thrown away with it; the next tick loads its
  own. A tick that does change the state saves with the version it
  loaded, exactly as before, and still fails on a conflict.
- Side effects. What an unchanged tick does on GitHub (dashboard upsert,
  eligibility comments and label removals, deletion of stray candidate
  refs) already ran before the save in every tick and is not recorded in
  the state. A save conflict never undid it; it only made main() redo the
  tick. With the skip, a concurrent change is picked up by the next tick.
- Ref cleanup. cleanupRefs runs before the save and keeps both the loaded
  in-flight refs and the refs of the new state. deleteSuperseded runs
  after it and deletes the loaded refs that the new state no longer
  names. With an identical document those two sets are equal, so it
  deletes nothing: no ref is removed on the strength of a save that did
  not happen.

The dashboard is still rendered and upserted on every tick (it already
PATCHes only when its body changes). No existing assertion changed.
2026-11-14 12:50:08 -03:00
diegosouzapw
56a327c727 fix(ci): judge an omni-queue candidate against its base, like a pull request
A push to omni-queue/** has no github.event.pull_request, so the gates that
are base-relative (or advisory) on a pull request ran a candidate in their
absolute / strict mode. A base that drifted mid-cycle would red every
candidate and the queue would blame innocent pull requests. Measured on the
release tip: the strict i18n drift check exits 1 (33 sources, 66 mirrors).

On a candidate these now compare with needs.changes.outputs.candidateBase:

- ci.yml lint: boundary ratchet (--base-ref).
- quality.yml fast-gates: file-size, complexity-ratchets, dead-code, boundary
  and the TS7 diagnostics ratchet (which was skipped without a base).
- ci.yml docs-sync-strict: the i18n docs drift takes the pull-request path
  (base checkout of the candidate base + advisory comparison); the strict
  step no longer runs on a candidate.

Pushes to main, merge_group and workflow_dispatch evaluate to the same
values as before; pull requests keep github.event.pull_request.base.sha.

newCodeMode.resolveMergeBase: on a merge-commit HEAD it compares with HEAD^1
(the live base tip of refs/pull/N/merge). A batch candidate is the base plus
one merge commit per pull request, so that rule judged only the last pull
request of the batch. The two new-code gates now pass the pushed ref, and a
refs/heads/omni-queue/** ref compares with the given base. Every other ref
keeps the first-parent rule. GITHUB_REF joins the runner-owned variables of
check-env-doc-sync (the gates read it; it is not OmniRoute configuration).

Existing assertions changed on purpose (same strictness, new expression):
- tests/unit/build/check-boundary-ratchet.test.ts: the two exact matches of
  the PR_BASE_SHA binding (ci.yml lint, quality.yml fast-gates) now expect
  "github.event.pull_request.base.sha || needs.changes.outputs.candidateBase".
- tests/unit/quality-rail-gate-membership.test.ts: the PR_BASE_SHA regex of
  the TS7 ratchet expects the same expression.
2026-11-14 12:45:19 -03:00
diegosouzapw
8ff7367c8b fix(ci): omni-queue shadow mode is inert for real pull requests
Shadow mode is meant to observe while Mergify keeps landing the same PRs.
It still acted on them:

- the tick removed the queue label and commented when it isolated a
  culprit, when a PR conflicted with the base, when its head was already
  in the base, and on every eligibility action (head changed after the
  label, conflicting, not an approver, protected surface, frozen base);
- the approval job wrote a `failure` status "approval withdrawn" on every
  `unlabeled`, a red status on a healthy PR that the other merge path may
  refuse to merge;
- a PR of the in-flight batch merged by Mergify during the candidate CI
  made the green batch be dropped as "already merged" and recomposed, so
  shadow rarely recorded `would-land`.

In shadow mode only (live mode is unchanged):

- tick.mjs writes to a pull request through two methods, removeLabel and
  the new commentPr, and both are no-ops in shadow. Comments on issues the
  queue owns (base-red notice, divergence, dashboard) keep going through
  comment().
- What live mode would have done is recorded instead. A culprit keeps the
  `culprit-found` event, with "shadow mode: label kept, no comment". A
  base conflict, a head already in the base and an eligibility label
  removal become a new `would-dequeue` event (PR, head, reason).
- A culprit, a base conflict and an already-in-base head are remembered
  per head SHA in state.shadow.processed, like a validated head, so they
  are not batched again (eligibility reason `shadow-processed`). A PR the
  eligibility rules reject is recorded once per head and not marked: it
  stays out by its own reason, and a new approval of that head can still
  queue it.
- A PR that another path merged at the tested head during the candidate
  CI no longer discards a green batch: `would-land` is recorded with
  "merged meanwhile by another path: #N". A PR merged at another head, or
  dropped for any other reason, is handled as before.
- approve.mjs writes nothing for `unlabeled`. This is safe: checked in
  eligibility.approvalFor, the older `success` never counts by itself.
  Without the label the PR is `no-label`; a label put back by a
  non-approver is `label-not-by-approver`; after an approver's new label
  only a status created no earlier than 60 s before that label approves
  the head. A characterization test pins this.

Not changed: the approval job still answers a non-approver's label with
one comment in shadow mode (the runbook says so).

Existing assertions changed on purpose:
- tick.test.mjs "shadow bisection composes later segments…": the culprit
  #3 now keeps its label (was `[]`) and is in shadow.processed (keys were
  1, 2, 4); the test also asserts the culprit-found event and that no
  label removal or comment was written.
Existing tests whose setup (not assertions) changed, because they ran the
committed shadow config while pinning live behaviour:
- approve.test.mjs uses the committed config with mode "live";
- tick.test.mjs "main: the client counts only the App's own comment
  markers" passes a live config through OMNI_QUEUE_CONFIG.
2026-11-14 12:45:03 -03:00
diegosouzapw
727cacafd3 fix(ci): omni-queue counts only the candidate's own push runs in its verdict
The candidate SHA is public. Anybody can publish that commit in a fork, or
on a branch of this repository, and open a pull request whose head is the
candidate. The PR's CI then reports check runs on the same SHA, and the
tick read them as the candidate's:

- readChecks kept every run whose check suite had no head_branch (fork
  PRs) or whose head_branch was the candidate ref (a same-repository PR
  from a branch with that name);
- by cancelling or re-pushing, the PR's author could make the candidate
  red or "infra" (retry, then a paused base), and a later run with the
  same name superseded the candidate's own result in checks.latestByName.

The verdict of a candidate ref now counts only the check runs of the check
suites of push-event workflow runs on that ref for that SHA
(GET /actions/runs?branch=<ref>&event=push&head_sha=<sha>, token already
has actions: read). Every listed run is re-checked for event, branch and
SHA. Anything else on the SHA is ignored: the base's own push, the other
ref of an infra retry, pull_request suites, workflow_dispatch runs, and
check runs of other apps (commit statuses are unchanged). Unknown fails
closed: with no ref, or no push run listed yet, no run counts, the verdict
stays pending and the existing no-CI timeout applies.

Why not strict `headBranch === ref`: checked on the release tip of the
real repository, a check suite carries the branch but not the event, so
the suites of a pull_request run and of a push run on the same branch
look alike. Each workflow run has its own check suite, and
workflow_run.check_suite_id equals check_run.check_suite.id.

github.mjs: check runs carry checkSuiteId; workflow runs carry headBranch
and checkSuiteId.

Tests: the new tick, client and end-to-end tests fail on the previous
code. Existing assertions changed, all additive, because the normalized
shapes gained fields: github.test.mjs expects checkSuiteId on
normalizeCheckRun and headBranch/checkSuiteId on listWorkflowRuns. One
tick test that injects raw check runs now attributes them to the push run
of the candidate ref in its setup; its assertions are untouched.
2026-11-14 12:34:17 -03:00
diegosouzapw
d0ec9e8ba6 fix(db): freeze the old migration series at 241 after 240 and 241 landed
While this PR was open, merge train 2 merged
240_provider_node_custom_json_config.sql (#18353) and 241_seen_models.sql
(#18359) into release/v3.8.54. With the series frozen at 239, the gate
rejected both base files and the compatibility tests' synthetic 240 slot
collided with the real one, so CI went red on the merge ref.

A merged migration is never renamed, so the freeze moves to the highest
old number on the base: LEGACY_MIGRATION_MAX is now 241, and its comment
says to raise it in the same merge if another NNN_ file lands before this
PR does. The tests no longer hard-code the free slot: the timestamp
compatibility test takes the first old number above every real file, and
the numbering tests derive the top and the number above it from
LEGACY_MIGRATION_MAX. The pinned value test now pins 241. The database
guide and the changelog fragment say 001-241, and the conversion recipe
lists 237 to 241 as slots that always need a compatibility entry.
2026-11-14 09:40:09 -03:00
diegosouzapw
553d565ee9 Merge remote-tracking branch 'origin/chore/derived-p2-counts-out-of-instructions' into feat/derived-strip-open-prs 2026-11-14 09:38:41 -03:00
diegosouzapw
b1c084ceed Merge remote-tracking branch 'origin/feat/derived-p1-gate-modes' into chore/derived-p2-counts-out-of-instructions
# Conflicts:
#	AGENTS.md
#	docs/i18n/am/llm.txt
#	docs/i18n/ar/llm.txt
#	docs/i18n/az/llm.txt
#	docs/i18n/bg/llm.txt
#	docs/i18n/bn/llm.txt
#	docs/i18n/bs/AGENTS.md
#	docs/i18n/bs/llm.txt
#	docs/i18n/cs/llm.txt
#	docs/i18n/da/llm.txt
#	docs/i18n/de/llm.txt
#	docs/i18n/el/llm.txt
#	docs/i18n/es/llm.txt
#	docs/i18n/et/llm.txt
#	docs/i18n/fa/llm.txt
#	docs/i18n/fi/llm.txt
#	docs/i18n/fr/llm.txt
#	docs/i18n/ga/llm.txt
#	docs/i18n/gu/llm.txt
#	docs/i18n/ha/llm.txt
#	docs/i18n/he/llm.txt
#	docs/i18n/hi/llm.txt
#	docs/i18n/hr/llm.txt
#	docs/i18n/hu/llm.txt
#	docs/i18n/hy/llm.txt
#	docs/i18n/id/llm.txt
#	docs/i18n/ig/llm.txt
#	docs/i18n/it/llm.txt
#	docs/i18n/ja/llm.txt
#	docs/i18n/ka/llm.txt
#	docs/i18n/km/llm.txt
#	docs/i18n/kn/llm.txt
#	docs/i18n/ko/llm.txt
#	docs/i18n/lt/llm.txt
#	docs/i18n/lv/llm.txt
#	docs/i18n/ml/llm.txt
#	docs/i18n/mr/llm.txt
#	docs/i18n/ms/llm.txt
#	docs/i18n/mt/llm.txt
#	docs/i18n/my/llm.txt
#	docs/i18n/ne/llm.txt
#	docs/i18n/nl/llm.txt
#	docs/i18n/no/llm.txt
#	docs/i18n/or/llm.txt
#	docs/i18n/pa/llm.txt
#	docs/i18n/phi/llm.txt
#	docs/i18n/pl/llm.txt
#	docs/i18n/pt-BR/llm.txt
#	docs/i18n/pt/llm.txt
#	docs/i18n/ro/llm.txt
#	docs/i18n/ru/llm.txt
#	docs/i18n/si/llm.txt
#	docs/i18n/sk/llm.txt
#	docs/i18n/sl/llm.txt
#	docs/i18n/sr/llm.txt
#	docs/i18n/sv/llm.txt
#	docs/i18n/sw/llm.txt
#	docs/i18n/ta/llm.txt
#	docs/i18n/te/llm.txt
#	docs/i18n/th/llm.txt
#	docs/i18n/tr/llm.txt
#	docs/i18n/uk-UA/llm.txt
#	docs/i18n/ur/llm.txt
#	docs/i18n/uz/llm.txt
#	docs/i18n/vi/llm.txt
#	docs/i18n/yo/llm.txt
#	docs/i18n/zh-CN/llm.txt
#	docs/i18n/zh-TW/llm.txt
#	llm.txt
#	open-sse/services/AGENTS.md
#	skills/README.md
#	skills/omni-auth/SKILL.md
#	skills/omni-providers/SKILL.md
#	src/shared/constants/agentSkills.ts
2026-11-14 09:35:10 -03:00
diegosouzapw
64b0a92987 fix(ci): reconcile-changelog counts a PR landed by omni-queue once
merge-ff keeps every contributor commit where a squash leaves one, so the "Commits in the
cycle" figure and the Top 25 ranking would favour a 30-commit PR over five squashed ones.
landingUnits() counts a queue PR once; rankAuthors() and renderSection() use it, and the
table names how many PRs the queue landed. Squash-only cycles render exactly as before;
the scope line keeps the literal non-merge commit count.
2026-11-14 09:25:39 -03:00
diegosouzapw
2bcd5bf783 Merge remote-tracking branch 'origin/release/v3.8.54' into feat/derived-p1-gate-modes
# Conflicts:
#	package.json
#	scripts/docs/gen-readme-cli-terminal.mjs
#	scripts/docs/gen-readme-comparison-table.mjs
#	scripts/docs/gen-readme-hero.mjs
#	scripts/docs/gen-readme-promise-pillars.mjs
#	scripts/docs/gen-readme-strategies-grid.mjs
#	scripts/docs/gen-readme-tier-cascade.mjs
#	scripts/quality/validate-release-green.mjs
2026-11-14 09:15:41 -03:00
diegosouzapw
e23db27829 Merge remote-tracking branch 'origin/release/v3.8.54' into feat/db-timestamp-migrations 2026-11-14 09:14:07 -03:00
diegosouzapw
a331fd7254 Merge remote-tracking branch 'origin/release/v3.8.54' into feat/omni-queue 2026-11-14 09:12:02 -03:00
diegosouzapw
29a1825f77 Merge remote-tracking branch 'origin/release/v3.8.54' into refactor/derived-p0-stryker-description
# Conflicts:
#	package.json
#	stryker.conf.json
2026-11-14 09:09:23 -03:00
diegosouzapw
899603b2a1 Merge release/v3.8.54 into test/video-live-receipts-20261009 2026-11-14 07:53:37 -03:00
diegosouzapw
9ddd54c536 Merge branch 'feat/derived-i18n-release-mode' into feat/derived-generated-baselines 2026-11-14 05:05:27 -03:00
diegosouzapw
e48fd302af fix(i18n): pr-mode skip reasons name the contexts that really run release mode
With #20161 the Release-Green HARD items run with OMNIROUTE_GATE_MODE=pr and the strict comparison moves to the release:refresh-derived --check drift item, so the skip text now says: the release PR, pushes to main, local runs.
2026-11-14 04:37:33 -03:00
diegosouzapw
d7ce4a458d Merge remote-tracking branch 'origin/chore/derived-p2-counts-out-of-instructions' into feat/derived-strip-open-prs 2026-11-14 04:25:49 -03:00
diegosouzapw
d8c9817d4f Merge remote-tracking branch 'origin/feat/derived-p1-gate-modes' into chore/derived-p2-counts-out-of-instructions 2026-11-14 04:25:16 -03:00
diegosouzapw
7834d4f095 feat(release): refresh prunes and re-queues UI keys, e2e timings step, i18n gates in pr mode on the train
Contract with the phase-4/5 session (2026-11-14):

- ui-keys: syncUiKeys is called with pruneExtra (keys en.json dropped leave the other catalogs)
  and rewrittenSinceRef (English values rewritten since the last release go back to translation;
  --rewritten-since=<ref>, default origin/main, skipped when unresolvable). The backend translates
  only when OMNIROUTE_TRANSLATION_* is configured, never in --check. The CLI fallback passes
  --rewritten-since when the script supports it.
- e2e-timings: new step that runs syncE2eTimings (phase 5) when the tree ships it; skipped
  otherwise.
- merge-train.sh: i18n:check-keys, i18n:check-keys:cli and i18n:check-ratio run in pr mode — the
  train judges the catalogs its PRs changed against the merge base, and a key that exists only in
  en.json is completed by the release refresh instead of reddening the train.
2026-11-14 04:23:25 -03:00
diegosouzapw
e7d603a641 feat(release): one-time pass that strips derived values from open PRs
Plan 2026-11-13 (derived numbers resolved only at release), section 8. PRs opened before phases 1
and 2 still write values the release refresh now owns, and the counts gate fails them in pr mode.
scripts/ad-hoc/strip-derived-from-pr.mjs restores, in each PR, only the lines it changed to update
such values back to the PR's merge-base text: the llm.txt mirrors, the Stryker list and the facts
snapshot as whole files; managed values in docs claim by claim (gate extractors); digit-only line
edits in agent-instruction files; the package description value.

Dry-run by default (PR heads fetched into refs/derived-strip/*, removed at the end). --apply
--prs=<list> builds ONE commit on top of each PR head with plumbing (no checkout) and pushes it as
a plain fast-forward to the head branch — never a force-push, never a rewrite of the
contributor's commits; it re-checks the PR (open, same head) right before the push and skips forks
without maintainer edits.
2026-11-14 04:08:13 -03:00
diegosouzapw
57a4c5ec2c Merge PR #19328 (feat/system-one-complements-1108) into merge train 2
# Conflicts:
#	README.md
#	docs/diagrams/comparison-table.svg
#	docs/diagrams/readme-hero.svg
#	docs/i18n/am/llm.txt
#	docs/i18n/ar/llm.txt
#	docs/i18n/az/llm.txt
#	docs/i18n/bg/llm.txt
#	docs/i18n/bn/llm.txt
#	docs/i18n/bs/llm.txt
#	docs/i18n/cs/llm.txt
#	docs/i18n/da/llm.txt
#	docs/i18n/de/llm.txt
#	docs/i18n/el/llm.txt
#	docs/i18n/es/llm.txt
#	docs/i18n/et/llm.txt
#	docs/i18n/fa/llm.txt
#	docs/i18n/fi/llm.txt
#	docs/i18n/fr/llm.txt
#	docs/i18n/ga/llm.txt
#	docs/i18n/gu/llm.txt
#	docs/i18n/ha/llm.txt
#	docs/i18n/he/llm.txt
#	docs/i18n/hi/llm.txt
#	docs/i18n/hr/llm.txt
#	docs/i18n/hu/llm.txt
#	docs/i18n/hy/llm.txt
#	docs/i18n/id/llm.txt
#	docs/i18n/ig/llm.txt
#	docs/i18n/it/llm.txt
#	docs/i18n/ja/llm.txt
#	docs/i18n/ka/llm.txt
#	docs/i18n/km/llm.txt
#	docs/i18n/kn/llm.txt
#	docs/i18n/ko/llm.txt
#	docs/i18n/lt/llm.txt
#	docs/i18n/lv/llm.txt
#	docs/i18n/ml/llm.txt
#	docs/i18n/mr/llm.txt
#	docs/i18n/ms/llm.txt
#	docs/i18n/mt/llm.txt
#	docs/i18n/my/llm.txt
#	docs/i18n/ne/llm.txt
#	docs/i18n/nl/llm.txt
#	docs/i18n/no/llm.txt
#	docs/i18n/or/llm.txt
#	docs/i18n/pa/llm.txt
#	docs/i18n/phi/llm.txt
#	docs/i18n/pl/llm.txt
#	docs/i18n/pt-BR/llm.txt
#	docs/i18n/pt/llm.txt
#	docs/i18n/ro/llm.txt
#	docs/i18n/ru/llm.txt
#	docs/i18n/si/llm.txt
#	docs/i18n/sk/llm.txt
#	docs/i18n/sl/llm.txt
#	docs/i18n/sr/llm.txt
#	docs/i18n/sv/llm.txt
#	docs/i18n/sw/llm.txt
#	docs/i18n/ta/llm.txt
#	docs/i18n/te/llm.txt
#	docs/i18n/th/llm.txt
#	docs/i18n/tr/llm.txt
#	docs/i18n/uk-UA/llm.txt
#	docs/i18n/ur/llm.txt
#	docs/i18n/uz/llm.txt
#	docs/i18n/vi/llm.txt
#	docs/i18n/yo/llm.txt
#	docs/i18n/zh-CN/llm.txt
#	docs/i18n/zh-TW/llm.txt
#	docs/reference/FEATURE_FLAGS.md
#	llm.txt
#	scripts/docs/gen-readme-comparison-table.mjs
#	scripts/docs/gen-readme-hero.mjs
#	src/i18n/messages/am.json
#	src/i18n/messages/ar.json
#	src/i18n/messages/az.json
#	src/i18n/messages/bg.json
#	src/i18n/messages/bn.json
#	src/i18n/messages/bs.json
#	src/i18n/messages/cs.json
#	src/i18n/messages/da.json
#	src/i18n/messages/de.json
#	src/i18n/messages/el.json
#	src/i18n/messages/en.json
#	src/i18n/messages/es.json
#	src/i18n/messages/et.json
#	src/i18n/messages/fa.json
#	src/i18n/messages/fi.json
#	src/i18n/messages/fr.json
#	src/i18n/messages/ga.json
#	src/i18n/messages/gu.json
#	src/i18n/messages/ha.json
#	src/i18n/messages/he.json
#	src/i18n/messages/hi.json
#	src/i18n/messages/hr.json
#	src/i18n/messages/hu.json
#	src/i18n/messages/hy.json
#	src/i18n/messages/id.json
#	src/i18n/messages/ig.json
#	src/i18n/messages/it.json
#	src/i18n/messages/ja.json
#	src/i18n/messages/ka.json
#	src/i18n/messages/km.json
#	src/i18n/messages/kn.json
#	src/i18n/messages/ko.json
#	src/i18n/messages/lt.json
#	src/i18n/messages/lv.json
#	src/i18n/messages/ml.json
#	src/i18n/messages/mr.json
#	src/i18n/messages/ms.json
#	src/i18n/messages/mt.json
#	src/i18n/messages/my.json
#	src/i18n/messages/ne.json
#	src/i18n/messages/nl.json
#	src/i18n/messages/no.json
#	src/i18n/messages/or.json
#	src/i18n/messages/pa.json
#	src/i18n/messages/phi.json
#	src/i18n/messages/pl.json
#	src/i18n/messages/pt-BR.json
#	src/i18n/messages/pt.json
#	src/i18n/messages/ro.json
#	src/i18n/messages/ru.json
#	src/i18n/messages/si.json
#	src/i18n/messages/sk.json
#	src/i18n/messages/sl.json
#	src/i18n/messages/sr.json
#	src/i18n/messages/sv.json
#	src/i18n/messages/sw.json
#	src/i18n/messages/ta.json
#	src/i18n/messages/te.json
#	src/i18n/messages/th.json
#	src/i18n/messages/tr.json
#	src/i18n/messages/uk-UA.json
#	src/i18n/messages/ur.json
#	src/i18n/messages/uz.json
#	src/i18n/messages/vi.json
#	src/i18n/messages/yo.json
#	src/i18n/messages/zh-CN.json
#	src/i18n/messages/zh-TW.json
#	src/shared/constants/featureFlagDefinitions.ts
#	tests/unit/feature-flags-settings.test.ts
#	tests/unit/server-owned-tool-loop-flag.test.ts
2026-11-14 04:01:31 -03:00
diegosouzapw
c796cb0718 Merge branch 'feat/derived-i18n-release-mode' into feat/derived-generated-baselines
# Conflicts:
#	scripts/check/check-test-masking.mjs
#	tests/unit/check-test-masking.test.ts
2026-11-14 03:59:40 -03:00
diegosouzapw
8b7c930f2d Merge remote-tracking branch 'origin/release/v3.8.54' into feat/derived-i18n-release-mode 2026-11-14 03:56:54 -03:00
diegosouzapw
e48c88d72f fix(i18n): importing sync-ui-keys no longer loads the local .env into the importer
The .env loader ran at module load, so release:refresh-derived and the tests that import syncUiKeys() got the operator's .env (DATA_DIR, OMNIROUTE_TRANSLATION_*, ...) in their own process. loadDotEnv() is now exported and called by the CLI and by syncUiKeys() only on the translate path, before backendConfig(); the translate concurrency default is read after it, so a value in the .env still applies there.
2026-11-14 03:52:23 -03:00
diegosouzapw
62dc680b40 Merge remote-tracking branch 'origin/release/v3.8.54' into feat/omni-queue
# Conflicts:
#	.zizmor.yml
2026-11-14 03:48:47 -03:00
diegosouzapw
897578ee5c ci: derived-files guard runs advisory until the open-PR cleanup; mirror refresh checks in pr mode
Owner decision 2026-11-14: check:pr-derived-paths starts with --warn and, in GitHub Actions, adds one ::warning annotation per violation so the advisory result is visible on the PR. A one-line PR drops --warn after the one-time cleanup of the open PRs (plan section 8).

i18n-mirror-refresh.yml runs check:docs-all with OMNIROUTE_GATE_MODE="pr", byte-identical to the same line in feat/derived-p1-gate-modes (#20161), so the two branches merge without a conflict.
2026-11-14 03:48:47 -03:00
diegosouzapw
c7f9eafdc5 feat(quality): test-masking lists every gate-mode skip helper, not just releaseOnlyUnlessTouched
The locale-parity helpers (localeParityOptions, localeParityIsReleaseOnly, placeholderParityDeferred) and the mirror-freshness helper (announceMirrorPlan) skip in a feature PR what the release refresh rewrites. countSkips() cannot see them, so the gate now counts each helper (imports excluded) and names it with its effect in the report-only block. The helpers' own unit tests are left out of the list. Report-only, as approved by the owner on 2026-11-14.
2026-11-14 03:46:36 -03:00
diegosouzapw
f4dae1ec0f Merge branch 'fix/oq-cr-reconcile' into feat/omni-queue 2026-11-14 03:44:58 -03:00