Enhance UI, add features, and improve readiness and telemetry (more dogfooding)

.github/workflows/docs-pr-amend.yml

@@ -112,15 +112,48 @@ jobs:
           since: ${{ steps.base.outputs.since }}
           github-token: ${{ github.token }}
 
-      # Commit only the regenerated companions back onto the PR branch. The
-      # action no-ops when nothing changed (e.g. every changed package was
-      # skipped by the content-hash gate), which is what makes a re-triggered
-      # run terminate instead of looping. README.md is never touched.
+      # Regenerate the global command reference. Unlike the per-package
+      # READMEs above, this is a deterministic transform of the dispatcher +
+      # agent command descriptors (no LLM, no API keys), so it reuses the
+      # docs-autogen CLI the composite already built and needs no GitHub
+      # Models token. writeCommandReference only writes when the content
+      # changed, so a re-triggered run regenerates nothing and the amend loop
+      # still terminates. Advisory like the README step: a docs failure here
+      # must never block the code PR.
+      - name: Regenerate command reference
+        continue-on-error: true
+        working-directory: ts
+        run: node tools/docsAutogen/bin/docs-autogen.cjs --command-reference
+
+      # Regenerate the interactive Action Browser: a self-contained HTML
+      # catalog (plus its raw JSON) of every agent action, parameter, example
+      # phrasing, and system command. Like the command reference it is a
+      # static transform of the bundled agent manifests/schemas/grammar (no
+      # LLM, no API keys). Its tool is separate from docs-autogen, so build it
+      # here - tsc -b is incremental, so deps the composite already built are
+      # no-ops. Advisory: a docs failure must never block the code PR.
+      - name: Regenerate action browser
+        continue-on-error: true
+        working-directory: ts
+        run: |
+          pnpm --filter '@typeagent/action-browser...' build
+          node tools/actionBrowser/dist/cli.js --json
+
+      # Commit the regenerated companions, command reference, and action
+      # browser back onto the PR branch. The commit no-ops when nothing
+      # changed (e.g. every changed package was skipped by the content-hash
+      # gate and the generated docs were already current), which is what makes
+      # a re-triggered run terminate instead of looping. README.md is never
+      # touched.
       - name: Commit regenerated docs
         uses: stefanzweifel/git-auto-commit-action@v5
         with:
-          commit_message: "docs: regenerate README.AUTOGEN.md for changed packages"
+          commit_message: "docs: regenerate README.AUTOGEN.md, command reference, and action browser"
           commit_user_name: typeagent-bot
           commit_user_email: typeagent-bot[bot]@users.noreply.github.com
           commit_author: "typeagent-bot <typeagent-bot[bot]@users.noreply.github.com>"
-          file_pattern: "ts/packages/**/README.AUTOGEN.md"
+          file_pattern: |
+            ts/packages/**/README.AUTOGEN.md
+            ts/docs/overview/command-reference.md
+            ts/docs/overview/action-browser.html
+            ts/docs/overview/action-browser.json

ts/.prettierignore

@@ -37,6 +37,12 @@ packages/shell/playwright-report/*
 # Generated cache files
 examples/websiteAliases/cache
 
+# Generated Action Browser (committed HTML + JSON catalog, regenerated and
+# committed per-PR by docs-pr-amend.yml; not hand-edited, so exclude from
+# formatting to avoid churn with the generator's own output).
+docs/overview/action-browser.html
+docs/overview/action-browser.json
+
 # VS Studio Files
 .vs/**
 

ts/docs/.gitignore

@@ -20,6 +20,8 @@ log.txt
 /agents/*
 !/agents/index.md
 
-# --- Generated interactive Action Browser (built by tools/actionBrowser) ---
-/overview/action-browser.html
-/overview/action-browser.json
+# --- Interactive Action Browser (built by tools/actionBrowser) ---
+# Intentionally NOT ignored: docs-pr-amend.yml regenerates the generated HTML
+# + JSON and commits them onto the PR branch so the catalog is reviewable in
+# the same PR that changed the agents. The docs-site deploy builds its own
+# copy separately.