Commit Graph

1167 Commits

Author SHA1 Message Date
diegosouzapw
bb6535bd6b feat(release): refresh-derived verifies the generated files after it writes
Agreed between the phase-1 and phase-4/5 owners of the plan 2026-11-13 and approved by the owner on 2026-11-15: release:refresh-derived ends with a verify-generated step that runs check:generated-artifacts (README SVGs, e2e-timings.json) and check:agent-skills-sync (generated SKILL.md) in release mode once the refresh has written. A generated file that still differs from its generator fails the step (exit 2). The step is skipped in --check (nothing reached the disk) and when --only leaves it out (a partial refresh leaves the other artifacts alone). refreshDerived() takes an injectable runNode for the tests.
2026-11-15 19:40:50 -03:00
Diego Rodrigues de Sa e Souza
99cd4883a6 Merge pull request #20277 from cheaper-inference/feat/omni-queue-cutover
feat(ci): omni-queue cut-over part 1 (status door, owner landing, bless, base check, hang handling)
2026-11-15 12:44:13 -03:00
Diego Rodrigues de Sa e Souza
df68e43042 fix(scripts): restore derived files byte for byte in the strip pass (#20267)
* fix(scripts): restore derived files byte for byte in the strip pass

The strip pass read merge-base and head contents through a helper that
trims its output, so every restored file lost its final newline. The
"restored" blob still differed from the merge base and the PR kept
conflicting on it (stryker.conf.json in the first batch).

Read blobs with a dedicated readBlob() that keeps the exact bytes, and
add a regression test that builds the restore commit from a real git
repository and compares blob ids with the merge base.

* fix(scripts): restore a claim with the base's own text in the strip pass

restoreClaims wrote the parsed base value back as an ASCII number. A
translated mirror that writes the count in native digits (Persian
README: "۲۳۳ مهاجرت") got "233" instead, so the line still differed from
the merge base and the PR kept conflicting on that mirror.

Use the base's exact substring for the claim span. Regression test with
a Persian-digit claim fails on the old code and passes now.
2026-11-15 09:39:55 -03:00
diegosouzapw
2b048650d9 fix(ci): omni-queue refs ruleset covers candidate refs at every depth 2026-11-15 08:39:13 -03:00
diegosouzapw
bf0f18028e fix(ci): omni-queue ruleset template flags must be false, and the blocker hint follows the runbook
The status rule validator accepted do_not_enforce_on_create: true and refused
a strict policy only when it was exactly true, so a non-boolean passed. Both
flags must now be exactly false. Tests cover the three refusals no test
exercised: a status rule without parameters, an unexpected parameter, and a
template that pins an integration_id itself. The hint printed when another
ruleset would reject the landing push now says what the runbook says: remove
those rulesets, the status door replaces them.
2026-11-15 07:48:37 -03:00
diegosouzapw
b39e63862d fix(ci): omni-queue git processes never receive the queue's two tokens
createGit spread process.env into every git child, so OMNI_QUEUE_TOKEN and
OMNI_QUEUE_LAND_TOKEN reached every git process, although credentials travel
through GIT_CONFIG_* already. Both are now removed from the base environment
and from any per-call environment.
2026-11-15 07:46:01 -03:00
diegosouzapw
1f458906d1 fix(ci): omni-queue land status context stays inside omni-queue/ and off the approval contexts
The candidate verdict ignores statuses by the omni-queue/ prefix: a land
status outside it would let a withdrawn (failure) status turn a candidate
red, and one equal to an approval context would make a label approval a
blessing. config.mjs now refuses both; the Zod mirror and the differential
table carry the same rule.
2026-11-15 07:44:06 -03:00
diegosouzapw
2c29e1ba1a fix(ci): omni-queue shadow bisection records a would-land segment as a green base
A shadow bisection composes the next segment on the would-land commit, but
that commit was never recorded green, so a red segment stacked on it paid a
full base check of a commit that had just passed. A would-land inside a
bisection now records its candidate green, as live mode records the landed
tip.
2026-11-15 07:42:26 -03:00
diegosouzapw
893490e2df fix(ci): omni-queue never leaves a success land status on a batch it abandons
Withdrawing the land status was all-or-nothing and could be skipped: a
refused write stopped revokeLanding and skipped the pause, and a tick that
died after blessing left no record, so the next tick recomposed with the
status still in success.

revokeLanding now attempts every commit, never throws, and records a failed
withdrawal in an error event, a note and the rethrown error. The in-flight
stage "landing" is saved before the App blesses (the gate: only a batch at
that stage pays a status read), and at the end of every live tick a batch
stored or marked at that stage that was neither landed nor kept there has
each newest land status read and turned into failure where it is success. A
manual pause puts such a batch back to the testing stage, so its status is
withdrawn until it lands after the resume.
2026-11-15 07:40:19 -03:00
diegosouzapw
9cc93e77ed fix(ci): omni-queue lands only a candidate that is the composition of its stored batch
The tick blessed and landed whatever the stored in-flight record named: a
record with no PR, or a candidate with an extra commit, got the land status.
Before the would-land and the bless, land.verifyComposition now requires a
non-empty batch, the base as an ancestor of the candidate, a first-parent
chain made only of queue merge commits that the stored PRs consume in order
at their heads, and stacked PRs (no merge commit of their own) exactly where
composeCandidate puts them; squash-api also checks the stored tree. A
mismatch blesses and lands nothing, records no would-land, and pauses the
queue with reason "error".
2026-11-15 07:34:25 -03:00
diegosouzapw
15d6eb39c2 fix(ci): omni-queue bless needs both the dispatcher and the triggering actor to be approvers
A re-run keeps the original dispatcher's inputs (sha, reason) and changes only
github.triggering_actor, so an approver re-running a non-approver's failed bless
used to write the land status. The tick now refuses a bless unless GITHUB_ACTOR
and GITHUB_TRIGGERING_ACTOR are both approvers, refuses when either is missing,
and names both in the status and the event when they differ. The workflow passes
github.actor next to github.triggering_actor.
2026-11-15 07:27:56 -03:00
diegosouzapw
56b92d0226 fix(ci): omni-queue hang evidence is scoped and counted from every run
A hang signature recorded on a base check now matches only a hang of
the candidate on the same check: a base that times out a job never
excuses an ordinary keyless failure of that job (base-red pause before,
pr-red now).

The hang path requires every run of the candidate to have been only job
timeouts. The in-flight retry carries timedOutRuns while that holds;
validateState accepts it as a count, and a document written without it
keeps the old behaviour (pause with reason infra). The hang-suspected
detail and the culprit comment state the real number of timed-out runs.

The culprit comment says the base passes the job only on a green base
verdict, and says nothing about the base without a verdict. The fake
classifier follows the real precedence for timeout and hang verdicts.
2026-11-15 05:35:58 -03:00
diegosouzapw
95c72638ec fix(ci): omni-queue bisects a repeated job timeout instead of pausing
A job that hits its time limit on every attempt is a hanging test, not
the machine. When the infra retries are used up and every failure is
hang-shaped (timed_out, or cancelled with the maximum-execution-time
annotation; never runner loss, startup_failure or a plain cancel), the
tick records hang-suspected and classifies the hang signatures like any
red batch: base check when the base has no verdict, base-red pause when
the bare base fails the same job, otherwise bisection with hang: true,
whose timed-out segments are not retried. The culprit comment names the
job that timed out.

A base check that never produces a verdict (no CI run, or no result
after checksTimeoutMinutes) and has no retry left no longer pauses the
queue: it is recorded as a timeout verdict and the parked batch is
settled (pr-red, the check cannot be redone for the same SHA). The
verdict lookup for a later red batch accepts timeout, so no base check
is started again for that SHA.

A job timeout on the bare base is recorded as a hang signature of the
base check even next to other failures, so a batch that hangs on the
same job is matched to the base instead of being blamed.
2026-11-15 05:21:04 -03:00
diegosouzapw
974140b31a fix(ci): omni-queue checks the bare base for every unverified tip 2026-11-15 05:01:46 -03:00
diegosouzapw
e9cddb6f81 feat(ci): omni-queue environment, land token and manual bless 2026-11-15 04:41:00 -03:00
diegosouzapw
c26aeaf8fb feat(ci): omni-queue status door ruleset and queue refs ruleset 2026-11-15 04:19:23 -03:00
diegosouzapw
43d55480f2 Merge release/v3.8.54 into feat/omni-queue-cutover 2026-11-15 04:09:40 -03:00
diegosouzapw
aa0f7d5ac7 fix(ci): omni-queue withdraws a land status blessed partway 2026-11-15 03:58:18 -03:00
diegosouzapw
7cf4ca4add feat(ci): omni-queue blesses the candidate and lands as the owner 2026-11-15 02:20:36 -03:00
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
9e605a3127 feat(ci): omni-queue landing actor, identity and land status context 2026-11-15 00:52:09 -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