Loading
docs(plans): batch-fill the monolith plan status tables (2026-09-15)
What this records
The batch fill of the Status tables under docs/plans/monolith/, as of
2026-09-15. Fifty step rows across twelve plans gain an MR link; every filled
cell names a merged merge request. Seven plans' tables were already
complete and are untouched.
This is the single-writer recording pass the Status-table guardrail asks for. It edits nothing but the MR column.
Per plan
| Plan | Rows | Recorded after this MR | Added here |
|---|---|---|---|
2026-06-24-vue-app-shell |
8 | 8 | — |
2026-07-02-ar-ruby-client |
3 | 3 | — |
2026-07-07-graphql-foundation |
3 | 3 | — |
2026-07-17-repository-crud |
8 | 8 | — |
2026-07-28-repositories-list |
10 | 9 | 1 |
2026-08-03-repository-detail |
14 | 14 | 4 |
2026-08-04-activation-and-deactivation |
18 | 18 | — |
2026-08-06-s02-gitlab-api-namespace-client |
3 | 3 | 3 |
2026-08-11-version-list |
25 | 25 | — |
2026-08-14-unconfigured-ar-base-url |
1 | 1 | — |
2026-08-18-version-detail |
22 | 17 | 17 |
2026-08-20-repository-crud-remote |
12 | 12 | 2 |
2026-08-20-repository-detail-remote |
14 | 11 | 4 |
2026-08-20-s02-service-token-credential |
1 | 1 | 1 |
2026-08-25-charts-artifact-registry-appconfig |
4 | 3 | 3 |
2026-08-26-s02-per-user-token-exchange |
1 | 1 | 1 |
2026-09-01-artifact-delete-surface |
19 | 9 | 9 |
2026-09-07-permission-gated-controls |
11 | 3 | 3 |
2026-09-10-repository-detail-virtual |
8 | 2 | 2 |
| Total | 185 | 151 | 50 |
Forty-seven distinct gitlab-org/gitlab merge requests are newly cited. Three
rows of the charts plan cite the other two repositories that plan's steps are
scoped to: gitlab-org/charts/gitlab!5294 for the chart block, and
gitlab-com/gl-infra/k8s-workloads/gitlab-com!5787 and !5827 for the staging
and production values.
How a row was matched to an MR
Merged merge requests were enumerated from
gitlab-org/gitlab under Category:Artifact Registry, then widened by title
search and by per-author scan, because part of this work carries no category
label.
A row is filled on one of four kinds of evidence, in this order of preference:
- A step marker in the MR title:
AR versions sort argument (monolith/S14 plan: 8/25),AR delete surface/Step 7: Manifest and container tag delete mutations. - A step id in the source branch:
zcuddy-s06-step18-files-pagination,602638-repositories-list-step-7,narendran-kannan/s05-step2-detail-fields. - A step claim in the MR description: "This is step 1 of 11 of monolith/S15", "This MR implements Steps 11 and 11a of the monolith/S07 Phase 2 plan".
- A title-to-step correspondence, read against the step's Scope and
Acceptance text and against the surface the MR describes. Two rows rest
on this:
repository-detail's Step 14, where gitlab!252898 binds the detail connections and moves a null connection to the not-found state the step's Acceptance names; andrepository-detail-remote's Step 12, where gitlab!253595 adds the Delete cache entry item to each remote artifact row.
Two rows share one MR where one MR delivered both steps, which the table already
does elsewhere: Steps 11 and 11a of repository-crud-remote, and Steps 11 and
12 of artifact-delete-surface. Two rows cite two MRs each, where the step
landed in halves: Steps 14 and 15 of version-detail.
Rows left blank, and why
Thirty-four rows stay empty. No merged MR was found for any of them.
| Plan | Rows | Why |
|---|---|---|
repositories-list |
8 (Recent searches) | No merged MR. The step is a leaf that nothing depends on. |
version-detail |
7, 8, 19, 20, 22 | No merged MR. The GraphQL statistics and npm metadata fields, the npm Manifest tab and its dist-tag badges, and the schema binding are all unlanded. |
repository-detail-remote |
11 (Eviction failure handling) | No MR matches the row. gitlab!253450 renders an alert on a rejected eviction, but not the 503 retry this step defines, so it is recorded against Step 10 alone. |
repository-detail-remote |
13 (Connect the remote eviction path to the schema) | No MR performs the step. Both eviction surfaces landed schema-bound, so no @client directive remained to drop. |
repository-detail-remote |
14 (Withheld Downloads and the stacked sidebar) | No merged MR. |
charts-artifact-registry-appconfig |
3 (Correct the self-managed install document) | Unlanded. Section 16 of docs/dev/self-managed-install.md still reads "(not yet active)" and still cites gitlab#606085. |
artifact-delete-surface |
4, 5, 9, 10, 14, 19 | The deferred bulk slice. |
artifact-delete-surface |
15, 16, 17, 18 | No merged MR. Each waits on an external gate the step's Depends on names. |
permission-gated-controls |
4-11 | No merged MR. Steps 1 to 3 are the client and detail-read layer; the type and Vue gating layers are unlanded. |
repository-detail-virtual |
3-8 | No merged MR. Steps 1 and 2 are the client read and the kind gate. |
An empty cell means "not yet recorded", not "not started" — and for these thirty-four it also means no merged MR was found, which is the stronger claim worth stating once here rather than in each table.
Not in scope
No row of an already-complete table was revisited, and no step text, note, or
prose was edited. The docs(plans) single-writer rule covers the MR column; a
correction to a step's own text belongs in its own MR.