Merge current main and reconcile historical checkpoint board

Signed-off-by: Lihua <1017343802@qq.com>

Author: LIHUA919

.github/workflows/dco.yml

@@ -2,6 +2,8 @@ name: DCO
 
 on:
   pull_request:
+  # A required check must also report on merge-queue candidates.
+  merge_group:
 
 permissions:
   contents: read
@@ -19,12 +21,15 @@ jobs:
 
       - name: Require DCO trailers on contribution commits
         env:
-          BASE_REF: ${{ github.event.pull_request.base.ref }}
-          HEAD_SHA: ${{ github.event.pull_request.head.sha }}
+          BASE_REF: ${{ github.event.pull_request.base.ref || github.event.merge_group.base_ref }}
+          HEAD_SHA: ${{ github.event.pull_request.head.sha || github.event.merge_group.head_sha }}
           GH_TOKEN: ${{ github.token }}
         shell: bash
         run: |
           set -euo pipefail
+          # merge_group reports the base as a full ref (refs/heads/main).
+          BASE_REF="${BASE_REF#refs/heads/}"
+          test -n "${BASE_REF}" && test -n "${HEAD_SHA}"
 
           # The event's base SHA can predate upstream commits already in the PR.
           # Refresh the exact target branch before selecting PR-only commits.

.github/workflows/full-public-smokes.yml

@@ -31,6 +31,9 @@ concurrency:
   group: full-public-smokes-${{ github.ref }}
   cancel-in-progress: true
 
+env:
+  LOOPX_USAGE_PING: "0"
+
 jobs:
   full-public-smokes:
     if: github.repository == 'loopx-project/loopx'

.github/workflows/python-tests.yml

@@ -3,6 +3,8 @@ name: Python Tests
 on:
   pull_request:
     types: [opened, synchronize, reopened, ready_for_review, labeled, unlabeled]
+  # Inert until the main ruleset enables a merge queue; queue runs are full.
+  merge_group:
   workflow_dispatch:
   push:
     branches:
@@ -30,6 +32,9 @@ concurrency:
   group: python-tests-${{ github.ref }}
   cancel-in-progress: true
 
+env:
+  LOOPX_USAGE_PING: "0"
+
 jobs:
   changes:
     runs-on: ubuntu-latest
@@ -102,20 +107,43 @@ jobs:
           cache-dependency-path: apps/presentation/dashboard/package-lock.json
       - run: python scripts/chat_bundle.py build --install
       - run: python scripts/chat_bundle.py verify --source
-      - name: Qualify the actual compiled UI before saving the artifact
-        working-directory: apps/presentation/dashboard
-        run: |
-          ./node_modules/.bin/playwright install --with-deps chromium
-          npm run smoke:personal-workspace-packaged
-          npm run smoke:chat-turn-acceptance-retry
-          npm run smoke:chat-upgrade
+      # Publish as soon as the bundle is built and verified so consumers start
+      # in parallel with browser qualification; `checks` still requires it.
       - uses: actions/upload-artifact@v7
         with:
           name: chat-bundle-${{ github.sha }}
           path: loopx/web/chat/
           if-no-files-found: error
           retention-days: 7
 
+  chat-bundle-browser:
+    needs: [changes, chat-bundle]
+    if: needs.changes.outputs.core_tests == 'true'
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    steps:
+      - uses: actions/checkout@v7
+      - uses: actions/download-artifact@v7
+        with:
+          name: chat-bundle-${{ github.sha }}
+          path: loopx/web/chat/
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.11"
+      - uses: actions/setup-node@v6
+        with:
+          node-version: "24"
+          cache: npm
+          cache-dependency-path: apps/presentation/dashboard/package-lock.json
+      - name: Qualify the actual compiled UI
+        working-directory: apps/presentation/dashboard
+        run: |
+          npm ci --ignore-scripts
+          ./node_modules/.bin/playwright install --with-deps chromium
+          npm run smoke:personal-workspace-packaged
+          npm run smoke:chat-turn-acceptance-retry
+          npm run smoke:chat-upgrade
+
   kernel-static-checks:
     needs: [changes, chat-bundle]
     if: needs.changes.outputs.core_tests == 'true'
@@ -317,19 +345,21 @@ jobs:
   checks:
     # Preserve the required check name while exposing independent failure lanes.
     if: always() && needs.changes.outputs.core_tests == 'true'
-    needs: [changes, kernel-static-checks, typescript-coverage, dashboard-acceptance]
+    needs: [changes, kernel-static-checks, typescript-coverage, dashboard-acceptance, chat-bundle-browser]
     runs-on: ubuntu-latest
     timeout-minutes: 2
     steps:
       - name: Require kernel and Dashboard qualification
         env:
+          BROWSER_RESULT: ${{ needs.chat-bundle-browser.result }}
           DASHBOARD_RESULT: ${{ needs.dashboard-acceptance.result }}
           KERNEL_RESULT: ${{ needs.kernel-static-checks.result }}
           TYPESCRIPT_RESULT: ${{ needs.typescript-coverage.result }}
         run: |
           test "$KERNEL_RESULT" = success
           test "$TYPESCRIPT_RESULT" = success
           test "$DASHBOARD_RESULT" = success
+          test "$BROWSER_RESULT" = success
 
   node-minimum-compatibility:
     needs: changes
@@ -360,7 +390,7 @@ jobs:
     needs: changes
     # The unsharded full suite outlasts a PR's qualification window, so the
     # non-blocking probe runs on main and on demand where it can finish.
-    if: github.event_name != 'pull_request' && needs.changes.outputs.core_tests == 'true'
+    if: (github.event_name == 'push' || github.event_name == 'workflow_dispatch') && needs.changes.outputs.core_tests == 'true'
     continue-on-error: true
     runs-on: ubuntu-latest
     # This runs the full core conformance suite. Allow forward-runtime/runner
@@ -500,6 +530,8 @@ jobs:
 
   sonar:
     needs: pytest
+    # Queue refs are temporary; analyse PRs and main, not gh-readonly-queue/*.
+    if: github.event_name != 'merge_group'
     uses: ./.github/workflows/sonarcloud.yml
     secrets:
       SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
@@ -704,7 +736,7 @@ jobs:
       - uses: actions/setup-python@v6
         with:
           python-version: "3.11"
-      - name: Verify the source-bound, browser-qualified Dashboard artifact
+      - name: Verify the source-bound Dashboard artifact
         run: python scripts/chat_bundle.py verify --source
 
   merge-gate:

AGENTS.md

@@ -36,6 +36,21 @@ dependency and why the boundary improves verification or rollback. Reuse or
 update an existing successor; do not create ceremonial follow-up tasks for a
 completed request. Real authorization, cost and operational stop gates remain.
 
+When a change introduces or extends a state classification, protocol literal,
+Enum, `Literal`, named closed set, or TypeScript `as const` vocabulary, answer
+whether it reuses an existing owner, extends a registered vocabulary, remains
+local, or creates a new shared contract. Before the full-tree semantic check,
+run the development-time advisory over the current diff:
+
+```bash
+uv run python scripts/generate_semantic_inventory.py --changed-from HEAD
+```
+
+Pass each intentional untracked source with `--include-untracked loopx/path.py`;
+the probe never scans untracked or ignored files automatically. Findings are
+review prompts, not a gate or proof of semantic equivalence, and an empty result
+does not cover dynamic construction or unsupported syntax.
+
 For multi-Agent changes, qualify the relationship the user needs: dependency
 artifacts, receiver adoption, claim/lease handling, independent acceptance and
 result return as applicable. Sending a message or registering workers does not
@@ -245,6 +260,11 @@ gates.
 
 Apply the whole-viewport attention review in `docs/development/design.md`
 ("Earn The User's Attention") before implementation and in PR visual evidence.
+For production-bound interactive UI changes, carry one ordinary user task through
+`docs/development/frontend-delivery.md`: compare the shortest authorized journey
+before coding, validate the packaged interaction and owning state, and distinguish
+proposed changes from installed behavior. For documentation and prototypes, name
+the simulated boundary without claiming packaged or installed readback.
 
 Before changing or reproducing any LoopX UI, read and follow the repository-root
 `docs/development/design.md`. This includes websites, dashboards, desktop applications,

CONTRIBUTING.md

@@ -56,6 +56,28 @@ large or behavior-changing work whose outcome is not yet agreed.
 
 Small docs typo fixes and obviously safe cleanups can go straight to a PR.
 
+### Check New Semantic Vocabulary While Developing
+
+If a change adds or extends an Enum, `Literal`, named closed set, TypeScript
+`as const` array, or another state/protocol vocabulary, run the diff-scoped
+advisory before the full-tree semantic check:
+
+```bash
+uv run python scripts/generate_semantic_inventory.py --changed-from HEAD
+```
+
+The command compares the named Git baseline with committed, staged, and working
+tree source changes, and reads the Git index and the working tree as separate
+snapshots so a staged addition survives a restored working file. It does not
+discover untracked files; include each intended
+new source explicitly, for example
+`--include-untracked loopx/control_plane/new_contract.ts`. It reports supported
+candidate carriers, registered-vocabulary reuse hints, and the disposition
+question to answer in review. Findings exit successfully because this is an
+advisory prompt, while invalid revisions, unreadable inputs, and tool failures
+exit non-zero. An empty report is not evidence that dynamic or unsupported
+semantic forms were analyzed.
+
 
 ## Public And Private Boundaries
 

apps/presentation/dashboard/README.md

@@ -33,10 +33,9 @@ run in the full development and packaged personal-workspace browser smokes.
 
 ## Fresh Clone Public Preview
 
-No private LoopX state is required for the first dashboard preview. The
-app bundles `examples/status.example.json` as its public-safe example source,
-so a fresh checkout can validate and open the UI before starting any local
-status server:
+No private LoopX state is required to validate the dashboard. The app bundles
+`examples/status.example.json` as its public-safe example source, and
+`smoke:demo-readiness` checks it without a local status server:
 
 ```bash
 cd apps/presentation/dashboard
@@ -45,15 +44,14 @@ npm run smoke:demo-readiness -- --skip-browser
 npm run dev:web
 ```
 
-Then open `http://127.0.0.1:5173/`. Use the bundled example source for a public
-demo, or switch to a loopback status URL only after you have started
-`loopx serve-status` locally. Do not commit `status.local.json` or live
-status exports; they can contain local registry/runtime paths and private
-project summaries.
-
-`npm run dev:web` starts only the Vite UI with the bundled example. `npm run dev`
-also starts the loopback status and Chat services and therefore requires a
-Python 3.11+ interpreter; see the development section below.
+`npm run dev:web` starts only the Vite UI at `http://127.0.0.1:5173/`. The
+workspace reads `/status.json` through the Vite proxy from `loopx serve-status`
+on port 8766 and the Chat APIs from `loopx chat` on port 8767, so without those
+services it opens on a status-load error. Start them locally, or use
+`npm run dev`, which also starts the loopback status and Chat services and
+therefore requires a Python 3.11+ interpreter; see the development section
+below. Do not commit `status.local.json` or live status exports; they can
+contain local registry/runtime paths and private project summaries.
 
 Personal Workspace owns Goal, Task, Chat, output, and report workflows. Run
 `loopx dashboard` for the installed local workspace; see the