Stability checkpoint — allow_failure deploy shields docs (phase 2) - chore(ci): document allow_failure:true pattern on deploy:* jobs (phase 2) Aligns iris-ui with the same allow_failure documentation discipline applied to iris-service-java and iris-service-python in the same session window. Each deploy:* job now carries an inline comment per ADR-0049 explaining the dated-TODO exit-ticket condition (no permanent shields). CI : - ✅ Main pipeline #586 green — https://gitlab.com/iris-7/iris-ui/-/pipelines/2525501062 (post-merge on main 67738fe) - ✅ All gating stages green : validate / lint / test:unit / test:unit:node20 / build / deploy-preview / e2e:kind (allow_failure) - ✅ No deploy job actually fires on UI (preview deploys are environment-gated) Local test pass : - ⏭ npm run build -- --configuration production — N/A : CI pipeline #586 build:production stage green on this SHA - ⏭ npm test (Vitest) — N/A : CI unit-tests + unit-tests:node20 stages green ; 53 spec files / 367 tests carried forward from stable-v1.2.6 - ⏭ npx playwright test — N/A : e2e:kind still under allow_failure shield (5/5 green main runs criterion from ADR-0033 ongoing) ; no UI code change to validate via E2E in this rev - ⏭ Manual mobile-viewport check (375 / 390 / 1280 px) — N/A : no UI code changes (.gitlab-ci/** only) Regression check vs previous tag : - ✅ stable-v1.2.6 known limitations carried forward (Angular 21 zoneless + signals + standalone + mobile-responsive — all unchanged) - ✅ e2e:kind still on allow_failure (per ADR-0033) — bounded ; tracking 5/5 green main runs criterion before shield removal - ✅ SERVICE_REPO URL post-Iris-rebrand fix (from stable-v1.2.6) still in place — no regression - ⏭ N/A — no LLM / agent-facing UI changes. Frontend remains client of polyrepo MCP servers (iris-java + iris-python in-process tools) ; UI displays AI-driven enrichment, no in-process LLM in UI itself (ADR-0062, intentional). - ⏭ N/A — no authn/authz / CSP / dependency changes. Auth0 OIDC + token refresh + route guards + CSP headers all unchanged. - ⏭ N/A — no UI feature changes. Customer + Order/Product/OrderLine screens + dashboards unchanged. - ⏭ N/A — no deploy target changes. Submodule infra/common (ecb8e29) unchanged from stable-v1.2.6. - ⏭ N/A — no telemetry / RUM changes. - ⏭ N/A — no test surface change. Coverage gate intact. - allow_failure shields on deploy:* jobs now documented per ADR-0049 — inline comments cite the dated-TODO exit condition for each shield (no permanent shields, scope-out vs shield pattern enforced) - e2e:kind shield remains pending 5/5 green main runs (ADR-0033) — separate criterion - No new ADRs accepted this rev - Feature-slicing (ADR-0008) + polyrepo flat α (ADR-0060) unchanged - Angular 21 zoneless + signals + standalone components + mobile-responsive (375 / 390 / 1280 px) — all unchanged - Bundle budgets intact ; no source code touched - Repo aligned with java + python on allow_failure documentation discipline (all 3 consumers consistent post-session) - e2e:kind on allow_failure: true pending 5/5 green main runs per ADR-0033 — exit ticket : flip to gating once SERVICE_REPO URL fix validates over 5 consecutive main pipeline successes - Bundle size budget headroom narrowing as features land — track ; not yet at the limit - stable-v1.2.8 candidate after one of these lands : - 5/5 green main runs criterion met → e2e:kind shield removed (ADR-0033 closeout) - First UI feature ships (new screen, new dashboard widget, etc.) - Mobile-responsive refresh or new viewport tier