Several human-facing links still point at vana-com, which is the old home of this project. The most visible one is the "Add your own" action on Home (src/pages/home/components/available-sources-list.tsx:281):
https://github.com/vana-com/data-connect?tab=readme-ov-file#creating-a-connector
That link is broken twice over. The repo it points at is archived, and the #creating-a-connector anchor does not exist in that README, so even following the redirect drops you at the top of an archived page. It should go to PDP-Connect/data-connectors, whose README does have a ## Building a new connector section.
The rest are in src/config/links.ts (the public DataConnect and data-connectors links), README.md:43,68,166, ecosystem/submit-data-app.md:31,36,85,87,91, and docs/260310-adding-a-new-connector.md:36. DataConnect links should point at PDP-Connect/data-connect and connector links at PDP-Connect/data-connectors.
Now the important part. Only touch human-facing navigation and documentation. There are still many vana-com strings in this repo, and most of them must not change:
src-tauri/src/commands/updates.rs intentionally uses the PDP-Connect connector index URL and PDP-Connect index signature identity, while still trusting the legacy Vana artifact certificate identity for previously published connector artifacts. Do not remove that mixed trust policy as part of a link cleanup.src-tauri/tauri.conf.json still has the app updater endpoint, and src-tauri/tauri-config.test.ts asserts it.src/hooks/app-update/* and scripts/build-updater-manifest.test.mjs have URLs backed by asserting tests.src/lib/telemetry/contract.ts points at a private repo that is the declared source of truth.
These look like the same kind of string and are not. If a URL is involved in app updates, connector index trust, artifact signing, package identity, telemetry provenance, or tests that define those contracts, leave it. The docs under docs/plans/, docs/solutions/, and docs/_archive/ are dated archival records, so leave those too.
If you are unsure which bucket something falls in, ask on the issue rather than guessing. Getting this wrong can break update or connector verification, which is why the safe list above is explicit.
I will check that every link you changed resolves, and that no distribution, updater, connector verification, package identity, or provenance URL moved.
Several human-facing links still point at
vana-com, which is the old home of this project. The most visible one is the "Add your own" action on Home (src/pages/home/components/available-sources-list.tsx:281):https://github.com/vana-com/data-connect?tab=readme-ov-file#creating-a-connectorThat link is broken twice over. The repo it points at is archived, and the
#creating-a-connectoranchor does not exist in that README, so even following the redirect drops you at the top of an archived page. It should go toPDP-Connect/data-connectors, whose README does have a## Building a new connectorsection.The rest are in
src/config/links.ts(the public DataConnect and data-connectors links),README.md:43,68,166,ecosystem/submit-data-app.md:31,36,85,87,91, anddocs/260310-adding-a-new-connector.md:36. DataConnect links should point atPDP-Connect/data-connectand connector links atPDP-Connect/data-connectors.Now the important part. Only touch human-facing navigation and documentation. There are still many
vana-comstrings in this repo, and most of them must not change:src-tauri/src/commands/updates.rsintentionally uses the PDP-Connect connector index URL and PDP-Connect index signature identity, while still trusting the legacy Vana artifact certificate identity for previously published connector artifacts. Do not remove that mixed trust policy as part of a link cleanup.src-tauri/tauri.conf.jsonstill has the app updater endpoint, andsrc-tauri/tauri-config.test.tsasserts it.src/hooks/app-update/*andscripts/build-updater-manifest.test.mjshave URLs backed by asserting tests.src/lib/telemetry/contract.tspoints at a private repo that is the declared source of truth.These look like the same kind of string and are not. If a URL is involved in app updates, connector index trust, artifact signing, package identity, telemetry provenance, or tests that define those contracts, leave it. The docs under
docs/plans/,docs/solutions/, anddocs/_archive/are dated archival records, so leave those too.If you are unsure which bucket something falls in, ask on the issue rather than guessing. Getting this wrong can break update or connector verification, which is why the safe list above is explicit.
I will check that every link you changed resolves, and that no distribution, updater, connector verification, package identity, or provenance URL moved.