Why: the project access and lifecycle units (U1 role narrowing to a single project-access boolean, U2 creator authority, U3 member history, U4 project work states) were implemented and pushed on feature/project-access-lifecycle-u3-backend but never landed here, so Dev's pinned Backend did not contain them. This merges that line into Backend main.
Evidence:
The merge is conflict-free against current origin/main; no manual conflict resolution was needed.
GOWORK=off go vet ./... && GOWORK=off go test -count=1 ./... green on the merge commit (SELF, go vet VET_OK, no FAIL lines).
Before this merge the tree was red: TestConversationWorkErrorCategorization failed at the delivery branch's own tip bd640df, not because of the merge. origin/main passed the same case.
Root cause of that red: the U3 change switched listConversations from the work gate to the read gate (s.projectWork → s.projectRead, an intentional semantic change so a removed member keeps read access to their own sessions) but also switched the error writer from writeWorkFailure(w, extension.WorkOperationConversation, err) to writeProjectErr(w, err). writeProjectErr writes err.Error() directly, and extension.WorkFailure.Error() renders as "<operation>: <reason>" with an empty operation here, so GET /api/projects/{id}/conversations degraded to the malformed body ": mapping-not-ready\n" — status code preserved, operation label lost.
Fix: keep s.projectRead, restore writeWorkFailure(w, extension.WorkOperationConversation, err). writeWorkFailure categorizes and re-adds the operation label, and falls through to writeProjectErr for errors that are not work failures, so the non-member 404 behaviour is preserved unchanged.
No test file was modified and no assertion was weakened; the existing main-line assertions pass as written.
Impact: Backend only. The RDM half of the same delivery lands separately. Dev advances its modules/backend gitlink only after this merges.
Why: the project access and lifecycle units (U1 role narrowing to a single project-access boolean, U2 creator authority, U3 member history, U4 project work states) were implemented and pushed on `feature/project-access-lifecycle-u3-backend` but never landed here, so Dev's pinned Backend did not contain them. This merges that line into Backend main.
Evidence:
- The merge is conflict-free against current `origin/main`; no manual conflict resolution was needed.
- `GOWORK=off go vet ./... && GOWORK=off go test -count=1 ./...` green on the merge commit (SELF, `go vet` VET_OK, no FAIL lines).
- Before this merge the tree was **red**: `TestConversationWorkErrorCategorization` failed at the delivery branch's own tip `bd640df`, not because of the merge. `origin/main` passed the same case.
- Root cause of that red: the U3 change switched `listConversations` from the work gate to the read gate (`s.projectWork` → `s.projectRead`, an intentional semantic change so a removed member keeps read access to their own sessions) but also switched the error writer from `writeWorkFailure(w, extension.WorkOperationConversation, err)` to `writeProjectErr(w, err)`. `writeProjectErr` writes `err.Error()` directly, and `extension.WorkFailure.Error()` renders as `"<operation>: <reason>"` with an empty operation here, so `GET /api/projects/{id}/conversations` degraded to the malformed body `": mapping-not-ready\n"` — status code preserved, operation label lost.
- Fix: keep `s.projectRead`, restore `writeWorkFailure(w, extension.WorkOperationConversation, err)`. `writeWorkFailure` categorizes and re-adds the operation label, and falls through to `writeProjectErr` for errors that are not work failures, so the non-member 404 behaviour is preserved unchanged.
- No test file was modified and no assertion was weakened; the existing main-line assertions pass as written.
Impact: Backend only. The RDM half of the same delivery lands separately. Dev advances its `modules/backend` gitlink only after this merges.
Refs: Dev PR #634.
Why: the cursor account hit its monthly usage limit (resets 2026-11-10);
attempts fail before useful work. Routing falls through to antigravity and
pi per the existing candidate order; re-enable when the quota resets.
Reason recorded on the U3 task card.
Impact: AGENT-EXECUTION.md only (rides the U3 PR, auditable).
Refs: plan 2026-10-19-1440 U3.
Why: the Gemini endpoint behind agy dropped the final streaming response
with EOF in three consecutive attempts, each after ~30 minutes of completed
work; routing falls through to pi. Re-enable when the endpoint recovers.
Reason recorded on the U3 task card.
Impact: AGENT-EXECUTION.md only.
Refs: plan 2026-10-19-1440 U3.
Why: compose the lifecycle line (role narrowing to a single project-access
boolean, U3b member-history read path) with Backend main (capability
association, explanation, super-admin). Per plan 2026-10-19-1440 R2/KTD2
the narrowed single-boolean write model supersedes the linked-cap expansion
and its association invariant; main non-conflicting work (explanation,
super-admin, tavily, O2 pins) is incorporated.
Impact: integration merge on the lifecycle branch; suites arbitrate.
Why: the project access and lifecycle units (U1 role narrowing to a single
project-access boolean, U2 creator authority, U3 member history, U4 project
work states) were implemented and pushed on this line but never landed on
Backend main, so Dev's pinned Backend does not contain them.
Evidence: merge is conflict-free against current origin/main; full
vet-and-test runs on the merge commit.
Impact: Backend only. RDM side is delivered separately.
Refs: Dev PR #634.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why: the project access and lifecycle units (U1 role narrowing to a single project-access boolean, U2 creator authority, U3 member history, U4 project work states) were implemented and pushed on
feature/project-access-lifecycle-u3-backendbut never landed here, so Dev's pinned Backend did not contain them. This merges that line into Backend main.Evidence:
origin/main; no manual conflict resolution was needed.GOWORK=off go vet ./... && GOWORK=off go test -count=1 ./...green on the merge commit (SELF,go vetVET_OK, no FAIL lines).TestConversationWorkErrorCategorizationfailed at the delivery branch's own tipbd640df, not because of the merge.origin/mainpassed the same case.listConversationsfrom the work gate to the read gate (s.projectWork→s.projectRead, an intentional semantic change so a removed member keeps read access to their own sessions) but also switched the error writer fromwriteWorkFailure(w, extension.WorkOperationConversation, err)towriteProjectErr(w, err).writeProjectErrwriteserr.Error()directly, andextension.WorkFailure.Error()renders as"<operation>: <reason>"with an empty operation here, soGET /api/projects/{id}/conversationsdegraded to the malformed body": mapping-not-ready\n"— status code preserved, operation label lost.s.projectRead, restorewriteWorkFailure(w, extension.WorkOperationConversation, err).writeWorkFailurecategorizes and re-adds the operation label, and falls through towriteProjectErrfor errors that are not work failures, so the non-member 404 behaviour is preserved unchanged.Impact: Backend only. The RDM half of the same delivery lands separately. Dev advances its
modules/backendgitlink only after this merges.Refs: Dev PR #634.