chore: point repository links at cacheplane/threadplane

Prepares the tracked references for the GitHub repository rename from
angular-agent-framework to threadplane: package metadata, website source
and content, README/CONTRIBUTING/SECURITY, library and example READMEs,
publish-workflow trusted-publisher notes, and PostHog dashboard copy.
Historical plans, specs and the CHANGELOG keep the old URL; GitHub
redirects them.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

Author: blove

.github/workflows/publish-middleware-npm.yml

@@ -13,7 +13,7 @@
 #      That initial upload creates the @threadplane/middleware package on npm.
 #   2. On npmjs.com → @threadplane/middleware → Settings → "Trusted Publisher",
 #      add this repo + workflow:
-#        Repository:  cacheplane/angular-agent-framework
+#        Repository:  cacheplane/threadplane
 #        Workflow:    publish-middleware-npm.yml
 #   3. After that, all releases use OIDC from this workflow — no secret needed.
 #

.github/workflows/publish-middleware-python.yml

@@ -8,7 +8,7 @@
 #   1. Log into PyPI under the **cacheplane** organization.
 #   2. Navigate to threadplane-middleware → Settings → "Trusted Publishers".
 #   3. Add a **Pending Publisher** with:
-#        Repository:   cacheplane/angular-agent-framework
+#        Repository:   cacheplane/threadplane
 #        Workflow:     publish-middleware-python.yml
 #        Environment:  (leave blank, or set to "pypi" if you create one)
 #   4. The FIRST-EVER publish must be bootstrapped locally by a maintainer

CONTRIBUTING.md

@@ -5,7 +5,7 @@ Threadplane is MIT-licensed and developed in the open. Contributions are welcome
 ## How to contribute
 
 1. **Found a bug or have a feature idea?** Open an issue at
-   <https://github.com/cacheplane/angular-agent-framework/issues> describing the
+   <https://github.com/cacheplane/threadplane/issues> describing the
    problem or proposal. Please search existing issues first.
 2. **Code changes:** fork the repository (or create a topic branch if you have
    access), make your change on a branch, and open a pull request against `main`.
@@ -148,11 +148,11 @@ Compare what was actually posted on the head SHA against what protection
 requires:
 
 ```bash
-gh api repos/cacheplane/angular-agent-framework/commits/<head-sha>/status --jq '[.statuses[].context]'
+gh api repos/cacheplane/threadplane/commits/<head-sha>/status --jq '[.statuses[].context]'
 ```
 
 ```bash
-gh api repos/cacheplane/angular-agent-framework/branches/main/protection --jq '.required_status_checks.checks'
+gh api repos/cacheplane/threadplane/branches/main/protection --jq '.required_status_checks.checks'
 ```
 
 Any required context missing from the posted list is the cause. Fix branch
@@ -162,7 +162,7 @@ the next one.
 Note that check *runs* (GitHub Actions) and commit *statuses* (external apps
 like Vercel) are different APIs. `CI — required` is a check run, so it appears
 in `gh pr checks` but not in the `/status` output above; use
-`gh api repos/cacheplane/angular-agent-framework/commits/<head-sha>/check-runs`
+`gh api repos/cacheplane/threadplane/commits/<head-sha>/check-runs`
 for those.
 
 ### Rollback reference

README.md

@@ -20,8 +20,8 @@
   <a href="https://langchain-ai.github.io/langgraph/">
     <img alt="LangGraph" src="https://img.shields.io/badge/LangGraph-SDK-6C8EFF?labelColor=080B14&style=flat-square" />
   </a>
-  <a href="https://scorecard.dev/viewer/?uri=github.com/cacheplane/angular-agent-framework">
-    <img alt="OpenSSF Scorecard" src="https://api.scorecard.dev/projects/github.com/cacheplane/angular-agent-framework/badge" />
+  <a href="https://scorecard.dev/viewer/?uri=github.com/cacheplane/threadplane">
+    <img alt="OpenSSF Scorecard" src="https://api.scorecard.dev/projects/github.com/cacheplane/threadplane/badge" />
   </a>
   <a href="https://www.bestpractices.dev/projects/13316">
     <img alt="OpenSSF Best Practices" src="https://www.bestpractices.dev/projects/13316/badge" />

SECURITY.md

@@ -14,7 +14,7 @@ fixes.
 ## Reporting a Vulnerability
 
 Please report security issues privately via GitHub's
-[private vulnerability reporting](https://github.com/cacheplane/angular-agent-framework/security/advisories/new).
+[private vulnerability reporting](https://github.com/cacheplane/threadplane/security/advisories/new).
 
 We aim to acknowledge reports within 5 business days and to provide a
 remediation timeline after triage. Please do not open public issues for

apps/website/content/blog/2026-05-28-human-in-the-loop-langgraph-agents-in-angular.mdx

@@ -19,7 +19,7 @@ Clone the repo, run `nx serve cockpit-langgraph-interrupts-angular`, and follow
   <Card title="Run the live demo" href="/docs/langgraph/guides/interrupts?mode=run">
     The refund agent running in the docs workspace. Walk the approve / edit / cancel flow yourself.
   </Card>
-  <Card title="View the source" external href="https://github.com/cacheplane/angular-agent-framework/tree/main/cockpit/langgraph/interrupts">
+  <Card title="View the source" external href="https://github.com/cacheplane/threadplane/tree/main/cockpit/langgraph/interrupts">
     The exact graph.py and Angular component from this post.
   </Card>
 </CardGroup>

apps/website/content/blog/2026-06-04-human-in-the-loop-ag-ui-agents-in-angular.mdx

@@ -21,7 +21,7 @@ Clone the repo, run `nx serve cockpit-ag-ui-interrupts-angular`, and follow alon
   <Card title="Run the live demo" href="/docs/ag-ui/guides/interrupts?mode=run">
     The refund agent running in the docs workspace. Walk the approve / edit / cancel flow yourself.
   </Card>
-  <Card title="View the source" external href="https://github.com/cacheplane/angular-agent-framework/tree/main/cockpit/ag-ui/interrupts">
+  <Card title="View the source" external href="https://github.com/cacheplane/threadplane/tree/main/cockpit/ag-ui/interrupts">
     The exact graph.py, server.py, and Angular component from this post.
   </Card>
 </CardGroup>
@@ -439,7 +439,7 @@ Your chat surface does not pick.
 
 Pointers:
 
-- The working example: [`cockpit/ag-ui/interrupts`](https://github.com/cacheplane/angular-agent-framework/tree/main/cockpit/ag-ui/interrupts) — Angular + Python, e2e-tested.
+- The working example: [`cockpit/ag-ui/interrupts`](https://github.com/cacheplane/threadplane/tree/main/cockpit/ag-ui/interrupts) — Angular + Python, e2e-tested.
 - The cross-adapter parity rendered in docs: [Choosing an adapter](https://threadplane.ai/docs/choosing-an-adapter).
 - The AG-UI interrupts guide for protocol-level detail: [/docs/ag-ui/guides/interrupts](https://threadplane.ai/docs/ag-ui/guides/interrupts).
 - The langgraph counterpart, if you want both sides side-by-side: [Human-in-the-Loop LangGraph Agents in Angular](/blog/2026-05-28-human-in-the-loop-langgraph-agents-in-angular).

apps/website/content/blog/2026-06-24-threadplane-earns-grade-a-hvtrust.mdx

@@ -121,7 +121,7 @@ The full breakdown — every dimension, the Scorecard checks, and the raw JSON 
 
 A trust grade is a starting point, not a finish line. The real way to evaluate a framework is to build something with it.
 
-So if you are curious: read the [listing](https://hvtracker.net/agents/threadplane/) and the [Agent Frameworks leaderboard](https://hvtracker.net/categories/agent-frameworks/), browse the [source on GitHub](https://github.com/cacheplane/angular-agent-framework) (all of it — it is almost all open), and ship your first streaming agent UI with the [quickstart](/docs/chat/getting-started/quickstart).
+So if you are curious: read the [listing](https://hvtracker.net/agents/threadplane/) and the [Agent Frameworks leaderboard](https://hvtracker.net/categories/agent-frameworks/), browse the [source on GitHub](https://github.com/cacheplane/threadplane) (all of it — it is almost all open), and ship your first streaming agent UI with the [quickstart](/docs/chat/getting-started/quickstart).
 
 We will keep the signals fresh, keep the framework open, and keep working on the one number I am not proud of yet.
 The rest, you can verify.

apps/website/content/blog/2026-08-31-we-measured-the-runtime-swap.mdx

@@ -84,7 +84,7 @@ It finalized as a success, with a tool call sitting there waiting for an approva
 The adapter's `interrupt` signal stayed undefined.
 It failed silently, which only means it took longer to notice.
 
-The fix was small once the cause was clear, and it landed in [#888](https://github.com/cacheplane/angular-agent-framework/pull/888).
+The fix was small once the cause was clear, and it landed in [#888](https://github.com/cacheplane/threadplane/pull/888).
 Both conventions are now recognized.
 Updated September 9, 2026: the adapter retains both forms in one session. Native batches take precedence in `auto` mode regardless of arrival order; the Mastra integration explicitly selects `mastra-command` so the resume includes its decision and suspended-tool correlation.
 
@@ -112,8 +112,8 @@ Send it nothing addressable and it raises an error.
 Four runtimes, three answers to the question of how a resume identifies itself.
 
 The adapter now derives the outgoing shape from how the interrupt arrived, which is the only signal available that is not a hardcoded runtime name.
-That work is in [#889](https://github.com/cacheplane/angular-agent-framework/pull/889).
-The protocol-package upgrade in [#891](https://github.com/cacheplane/angular-agent-framework/pull/891) is what made the standard top-level array sendable at all.
+That work is in [#889](https://github.com/cacheplane/threadplane/pull/889).
+The protocol-package upgrade in [#891](https://github.com/cacheplane/threadplane/pull/891) is what made the standard top-level array sendable at all.
 The application-facing call did not change.
 You still write `submit({ resume })` and the adapter decides what goes on the wire.
 
@@ -158,7 +158,7 @@ The platform kept serving the last image that booted.
 Nothing was red anywhere.
 The route had been returning a not-found for months.
 
-The fix in [#899](https://github.com/cacheplane/angular-agent-framework/pull/899) was two import statements.
+The fix in [#899](https://github.com/cacheplane/threadplane/pull/899) was two import statements.
 The deploy workflow now installs the exact dependency set, imports the server, and fails the job if it cannot boot.
 
 Verify the route, not the exit code.

apps/website/content/docs/choosing-an-adapter/index.mdx

@@ -145,16 +145,16 @@ Each demo backend ships its emitter in tree, roughly 200 to 430 lines per runtim
 Each runtime got a real server, started against the upstream AG-UI integration and driven with live model calls.
 The raw Server-Sent Events were captured off the wire, then replayed event-for-event through the pinned `@ag-ui/client` — schema parse plus `verifyEvents` — and through the adapter reducer itself.
 
-The captures for messages, tool calls, state, and interrupts are committed at [`libs/ag-ui/fixtures/runtime-transcripts/`](https://github.com/cacheplane/angular-agent-framework/tree/main/libs/ag-ui/fixtures/runtime-transcripts), verbatim from the wire, and the adapter test suite replays them on every run.
+The captures for messages, tool calls, state, and interrupts are committed at [`libs/ag-ui/fixtures/runtime-transcripts/`](https://github.com/cacheplane/threadplane/tree/main/libs/ag-ui/fixtures/runtime-transcripts), verbatim from the wire, and the adapter test suite replays them on every run.
 The subagent captures are committed as a `wire-capture-subagents.md` document alongside each backend under `cockpit/runtimes/<runtime>/`; the subagent transcript the suite replays is synthetic, built to the event shape those captures record.
 
 ### Runnable examples
 
 Each runtime has a standalone Angular example bound through `@threadplane/ag-ui`, with its own backend:
 
-- [`cockpit/runtimes/aws-strands`](https://github.com/cacheplane/angular-agent-framework/tree/main/cockpit/runtimes/aws-strands) — Python, hosted in the shared FastAPI deployment.
-- [`cockpit/runtimes/microsoft-agent-framework`](https://github.com/cacheplane/angular-agent-framework/tree/main/cockpit/runtimes/microsoft-agent-framework) — Python, hosted in that same FastAPI deployment, running beside the Strands and LangGraph topics in one process.
-- [`cockpit/runtimes/mastra`](https://github.com/cacheplane/angular-agent-framework/tree/main/cockpit/runtimes/mastra) — TypeScript, hosted by a Node AG-UI service, because the upstream Mastra integration ships an in-process bridge rather than an HTTP endpoint.
+- [`cockpit/runtimes/aws-strands`](https://github.com/cacheplane/threadplane/tree/main/cockpit/runtimes/aws-strands) — Python, hosted in the shared FastAPI deployment.
+- [`cockpit/runtimes/microsoft-agent-framework`](https://github.com/cacheplane/threadplane/tree/main/cockpit/runtimes/microsoft-agent-framework) — Python, hosted in that same FastAPI deployment, running beside the Strands and LangGraph topics in one process.
+- [`cockpit/runtimes/mastra`](https://github.com/cacheplane/threadplane/tree/main/cockpit/runtimes/mastra) — TypeScript, hosted by a Node AG-UI service, because the upstream Mastra integration ships an in-process bridge rather than an HTTP endpoint.
 
 In all three, the component binds the agent through `injectAgent()` and renders `<chat [agent]="agent" />`; the shared-state panels and approval cards around it are demo-specific, and each example wraps `provideAgent()` in a factory only because it resolves its endpoint at runtime.