task 27: primary exists now; main still stale
This commit is contained in:
parent
81196d1ab9
commit
5faae0fdb3
1 changed files with 8 additions and 3 deletions
|
|
@ -67,9 +67,14 @@ finding 6 happened, and nothing isolates the next one.
|
|||
working branch `experimental/session-trust-phase1` is **not in the trigger
|
||||
list at all** — a push there runs no CI and publishes nothing, silently.
|
||||
`main` is the repo's *default* branch and has not moved since 2026-05-22, so
|
||||
a fresh clone gets two-month-old code. Either create `primary` or drop it;
|
||||
and point `main` at what actually ships. (`culver` is consistent by
|
||||
contrast: default `primary`, CI triggers on `primary`.)
|
||||
a fresh clone gets two-month-old code. (`culver` is consistent by contrast:
|
||||
default `primary`, CI triggers on `primary`.)
|
||||
|
||||
**Half-fixed 2026-07-25:** `primary` now exists at `9d8bce2` and the local
|
||||
checkout tracks it, so the documented model — dev on `primary`, promote to
|
||||
`public`, publish gated to `public` — is real and the trigger no longer names
|
||||
a ghost. Still open: `main` remains the *default* branch and still points at
|
||||
May's `1cf98ef5`. Either move it or retire it.
|
||||
|
||||
2. **`kernel.yml` has never once passed.** 11 runs, 11 failures, none since
|
||||
Jul 14 — eleven days with nobody retrying. `kernel-latest` is a 404.
|
||||
|
|
|
|||
Loading…
Reference in a new issue