Refresh 36blocks website and workspace investigation journeys

.github/workflows/v0-behavior.yml

@@ -0,0 +1,25 @@
+name: V0 behavior checks
+on:
+  pull_request:
+  workflow_dispatch:
+permissions:
+  contents: read
+jobs:
+  behavior:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: '22'
+          cache: npm
+      - name: Install locked dependencies without lifecycle hooks
+        run: npm ci --ignore-scripts --legacy-peer-deps --no-audit --no-fund
+      - name: Run focused behavior and HTTP routing tests
+        run: npm run test:v0
+      - name: Generate local environment modules without credentials
+        env:
+          CI: 'false'
+        run: node tools/set-env
+      - name: Check application types and templates
+        run: node_modules/.bin/ngc --noEmit -p apps/36-blocks/tsconfig.app.json

AGENTS.md

@@ -0,0 +1,13 @@
+# Working on proxy-ui
+
+Owns the Angular public website, operator dashboard and embeddable authentication widget. Backend APIs, persistence and session policy belong to sibling `user-proxy`; connected applications own business authorization.
+
+Start with the canonical [work state](../user-proxy/docs/WORK-STATE.md), [architecture](../user-proxy/docs/ARCHITECTURE.md), [capabilities](../user-proxy/docs/CAPABILITIES.md), [development](../user-proxy/docs/DEVELOPMENT.md), [security](../user-proxy/docs/SECURITY-OPERATIONS.md) and [design](../user-proxy/docs/DESIGN.md). Preserve existing README contribution rules and DESIGNGUIDE.md. Read widget integration/event guides before changing the custom element contract.
+
+- Branch workflow: use `production` as the frontend base and PR target. Before pushing a feature branch or opening its PR, fetch and merge the latest `origin/production` into that feature branch. Keep release branches unchanged until PR review.
+- PR disclosure requirement: when a change introduces or changes required environment variables/secrets, removes a configuration fallback, changes authentication/security behavior, requires migrations or deployment ordering, invalidates sessions/tokens, or otherwise affects rollout/backward compatibility, explicitly notify the user when raising or updating the PR. Add a prominent `Deployment impact` section to the PR description naming the affected service/environment, exact configuration names (never secret values), behavior if prerequisites are missing, required setup/migration/restart order, compatibility/session effects, and what was or was not verified. Repeat critical prerequisites in the user-facing PR handoff; a note only in repository documentation or the PR body is insufficient. This is a notification requirement, not an additional approval gate.
+- Inspect status/diff; preserve unrelated changes. New application code uses TypeScript and existing standalone Angular patterns. Use Angular CLI scaffolding when practical; never change architecture solely to satisfy scaffolding.
+- Install from lock using `npm ci --ignore-scripts --legacy-peer-deps`; generate ignored env modules with `node tools/set-env`. Review environment base URLs before starting: local config defaults to a remote test API.
+- Run `node --test tools/tests/*.test.cjs`, affected builds and `git diff --check`. Existing Nx/Jest targets have known gaps: report exact commands and limitations in canonical work state.
+- Keep error, denied, empty and loading states distinct; provide retry. Never render request data as HTML or log/store tokens. Client visibility does not replace server authorization.
+- Update the single backend-owned capability matrix and work state alongside changes. Product/architecture guidance is linked, not duplicated here. Public claims require evidence; do not invent SLAs, guarantees or future functional controls.

DESIGNGUIDE.md

@@ -1,20 +1,8 @@
 # Proxy UI Design Guide
 
-##   Setup Guide
+## Setup
 
-1. Clone https://github.com/Walkover-Web-Solution/proxy-UI.git.
-
-2. This project requires Node version 14+, install Node from [here](https://nodejs.org/en/).
-
-3. Go inside the cloned directory `proxy-UI` in any terminal and run these following commands in the terminal to install dependency and start local serve.
-
-4. Run `npm i` for installation of dependencies.
-
-5. Serving the project locally: 
-    * For proxy: Run `npm start` to local serve the project.
-    * For Admin Panel: Run `npm run start:admin` to local serve the project.
-    * For chat-widget: Run `npm run start:chat-widget` to local serve the project.
-    * For otp-provider: Run `npm run start:otp-provider` to local serve the project.
+Use the current [README](README.md) and canonical [development guide](../user-proxy/docs/DEVELOPMENT.md) for runtime, install and startup commands. Legacy admin/chat/OTP application commands formerly listed here no longer describe the supplied workspace. The following styling guidance remains reference material; use the canonical [design standards](../user-proxy/docs/DESIGN.md) for product behavior.
 
 ## Prerequisites
 It is important to have a thorough understanding of **HTML**, **CSS** and its pre-processor **SASS** to contribute to this project. If unaware of any of the above then go through their documention first.

README.md

@@ -6,13 +6,23 @@
 
 1. Clone https://github.com/Walkover-Web-Solution/proxy-ui.git.
 
-2. This project requires Node version 14+, install Node from [here](https://nodejs.org/en/).
+2. This is Angular 21.2 / Nx 21.6 / TypeScript 5.9. Use a compatible Node runtime; see the [canonical development guide](../user-proxy/docs/DEVELOPMENT.md). Node 14 is unsupported.
 
 3. Go inside the cloned directory `proxy-ui` in any terminal and run these following commands in the terminal to install dependency and start local serve.
 
-4. Run `npm i` for installation of dependencies.
+4. Run `npm ci --ignore-scripts --legacy-peer-deps` to install the locked dependencies. Review the development guide before enabling install hooks.
 
-5. Run `npm start` to local serve the project.
+5. Configure approved local environment values, run `node tools/set-env`, then `npm start`. The checked-in local API URL points to a remote test service; change it before exercising mutations.
+
+Read [AGENTS.md](AGENTS.md), [current work state](../user-proxy/docs/WORK-STATE.md), [architecture](../user-proxy/docs/ARCHITECTURE.md) and the authoritative [capability matrix](../user-proxy/docs/CAPABILITIES.md). The API is the sibling `user-proxy` repository. `node --test tools/tests/*.test.cjs` runs focused behavior tests; legacy Nx/Jest targets have known gaps recorded in the work state.
+
+The existing contribution and style guidance below remains applicable. Use the canonical development and design guides where obsolete runtime/module instructions conflict with the current standalone Angular architecture.
+
+## Isolated design review
+
+Product and API guidance lives at [developers.36blocks.com](https://developers.36blocks.com). `/docs` is a legacy handoff page, not another documentation site.
+
+Run `npm run review:build`, then `npm run review:serve` for the local review at `http://127.0.0.1:4360`. It renders the real routes using synthetic fixtures and a separate bootstrap. All mutations are rejected; no live API calls or credentials are issued. `review-version.json` identifies the source fingerprint. Release configurations continue to use `src/main.ts`. This review does not verify live authentication or providers.
 
 ## Contributing Guide
 
@@ -344,3 +354,9 @@ We have a server [Marlin](marlin.phone91.com) [for Prod] & [sailfish](sailfish.p
 
 If client origin is widget (origin = `chat`) [will implement for all in v2], we have an option to start meet from `client-card-component`.
 For selected client we use `call-session-creds` API to fetch `room` & `jwt` to init socket connection and Jitsi meet room with Jitsi Options. [Jitsi Reference Doc](https://developer.8x8.com/jaas/docs/iframe-api-integration)
+
+## Production integration — 29 October 2026
+
+The V0 changes are reconciled with production commit `2b1deb17`. Production deliberately uses a browser-only build and removed `ProjectGuard`; this merge preserves both decisions and the newer production navigation, OAuth/client-secret features, and compact website spacing. The original feature branch's SSR and project-guard changes/tests are therefore not part of this production integration.
+
+Validation: 23 applicable `npm run test:v0` checks, Angular type/template checking, and `npm run build:prod` passed, including the widget bundle and post-build packaging. Build warnings remain; this does not certify configured Firebase/provider login. Activity and Login as require the companion backend API/migrations from [user-proxy PR #1476](https://github.com/Walkover-Web-Solution/user-proxy/pull/1476) before live use. See the canonical [work state](../user-proxy/docs/WORK-STATE.md) for remaining integration gates.

apps/36-blocks/project.json

@@ -127,6 +127,20 @@
                     "optimization": false,
                     "extractLicenses": false,
                     "sourceMap": true
+                },
+                "review": {
+                    "browser": "apps/36-blocks/src/main.review.ts",
+                    "tsConfig": "apps/36-blocks/tsconfig.review.json",
+                    "outputPath": "dist/review",
+                    "optimization": false,
+                    "extractLicenses": false,
+                    "sourceMap": false,
+                    "fileReplacements": [
+                        {
+                            "replace": "apps/36-blocks/src/environments/environment.ts",
+                            "with": "apps/36-blocks/src/environments/environment.review.ts"
+                        }
+                    ]
                 }
             },
             "defaultConfiguration": "production"

apps/36-blocks/src/app/core/ngrx/effects/root/root.effect.ts

@@ -82,7 +82,7 @@ export class RootEffects {
             switchMap((req) => {
                 return this.rootService.getProjects().pipe(
                     map((res) => {
-                        if (res.hasError) {
+                        if (res.hasError || !Array.isArray(res.data?.data)) {
                             this.showError(res.errors);
                             return rootActions.getAllProjectsError();
                         }

apps/36-blocks/src/app/core/ngrx/store/reducer/root.reducer.ts

@@ -18,6 +18,7 @@ export interface IRootState {
     //All project
     allProjects: IPaginatedResponse<IProjects[]>;
     projectInProcess: boolean;
+    projectLoadFailed: boolean;
 }
 
 export const initialState: IRootState = {
@@ -33,6 +34,7 @@ export const initialState: IRootState = {
     clientsInProcess: false,
     switchClientSuccess: false,
     projectInProcess: false,
+    projectLoadFailed: false,
     allProjects: null,
 };
 
@@ -121,20 +123,23 @@ const _rootReducer = createReducer(
         return {
             ...state,
             projectInProcess: true,
+            projectLoadFailed: false,
         };
     }),
     on(rootActions.getAllProjectSuccess, (state, { response }) => {
         return {
             ...state,
             allProjects: response,
             projectInProcess: false,
+            projectLoadFailed: false,
         };
     }),
     on(rootActions.getAllProjectsError, (state) => {
         return {
             ...state,
             allProjects: null,
             projectInProcess: false,
+            projectLoadFailed: true,
         };
     })
 );

apps/36-blocks/src/app/core/ngrx/store/selectors/root.selector.ts

@@ -32,3 +32,10 @@ export const selectProjectInProcess = createSelector(
     selectRootState,
     (rootState: IRootState) => rootState.projectInProcess
 );
+
+/** One selector keeps project data and its request outcome consistent for guards. */
+export const selectProjectAccessState = createSelector(selectRootState, (state: IRootState) => ({
+    projects: state.allProjects,
+    loading: state.projectInProcess,
+    failed: state.projectLoadFailed,
+}));