docs: add UTM tracking to aictrl.dev links

[byapparov]

Closes #106

Problem

Traffic from this repository to aictrl.dev cannot currently be attributed in analytics.

Behavior

The README link now includes the shared GitHub referral campaign and utm_content=readme. There is no runtime behavior change.

Scope

• Uses utm_medium=referral, utm_source=github, utm_campaign=cli, and utm_content=readme on the README link.
• Keeps the LICENSE copyright notice unchanged so legal-text matching remains stable.

Rollout and risks

Documentation-only change. The destination is unchanged; rollback is removing the README query parameters.

Verification

• bun turbo typecheck (pre-push hook) — 6/6 tasks successful.
• Current-head GitHub CI verify, CodeQL analyses, and Aictrl AI Review — passed.
• Initial KG Extract review — passed and identified one license-text finding, fixed in 6c572e5bb.
• Current-head KG Extract re-review — external task runner failed before producing findings; GitHub retry endpoints are unavailable for the third-party app.
• git diff --check origin/main...HEAD — passed.
• Tracked-file URL scan — the README URL contains the expected UTM parameters and the legal notice is unchanged.
• No additional local tests were run; GitHub CI executed the repository test suite successfully.

[aictrl-dev]

Code review

Verdict: Address the major findings before merging. · 🔴 0 · 🟠 1 · 🟡 0 · ⚪ 0 · 0/1 resolved

• 🟠 LICENSE:4 — UTM tracking params added to LICENSE copyright line

🤖 Fix all 1 open findings with your agent

Fix the following code review findings on aictrl-dev/cli PR #107 (head branch).
Run the relevant tests/linters after each change.

1. LICENSE:4 — UTM tracking params added to LICENSE copyright line
   Detail: The LICENSE copyright notice is a legal document and conventionally stays byte-for-byte stable; embedding marketing UTM parameters into the copyright holder's URL is a purpose conflict, and some packaging pipelines, distro importers, and SPDX/license-matching tools compare or hash LICENSE text, so this edit can cause spurious mismatches. Tracking belongs in README (or other docs) links only.
   Suggested fix: Revert the LICENSE line to `Copyright (c) 2026 Aictrl (https://aictrl.dev)` and keep the UTM-tagged link only in README.md.

📋 Out-of-diff findings (1)

Sev	Location	Finding
🟠	LICENSE:4	UTM tracking params added to LICENSE copyright line

Reviewed 2 files · 0 inline · view all 1 findings ↗

---

aictrl · AI code review for fast-moving teams · aictrl.dev

[byapparov]

Review response — PR #107

Kept referral tracking in repository documentation while restoring the legal notice to its canonical text.

Issues addressed (pushed to this PR)

• UTM tracking params added to LICENSE copyright line — LICENSE: restored the untagged copyright URL so legal-text matching remains stable (commit 6c572e5bb).

Review claims verified false (no change needed)

• None.

Not addressed here

• None.

[aictrl-dev]

🟡 UTM rollout: other product links in repo remain untagged.

🤖 Fix with your agent

Fix this code review finding (aictrl-dev/cli PR #107, README.md:125):

Problem: UTM rollout: other product links in repo remain untagged
Detail: PR title and issue #106 describe UTM tracking for aictrl.dev "links", but this edits the repo's only aictrl.dev hyperlink while every other user-facing product link remains untagged on the bare https://aictrl.ai domain: github/README.md:3 (GitHub Action marketplace readme), sdks/vscode/README.md:3 and :7 (VS Code marketplace readme), packages/sdk/README.md:64 (rendered as the npm readme of @aictrl/sdk), packages/cli/package.json:11 (homepage), and install:23/:458 (install script output). If aictrl.ai and aictrl.dev feed the same analytics property, issue #106's attribution goal misses all of these higher-traffic surfaces; if they are separate properties, the repo now promotes two canonical product domains and this PR deepens the split. Domain equivalence could not be confirmed from the repo alone.
Suggested fix: Either extend the same campaign (utm_medium=referral&utm_source=github&utm_campaign=cli with a per-surface utm_content, e.g. action-readme / vscode-readme / sdk-readme) to the product links in github/README.md, sdks/vscode/README.md, and packages/sdk/README.md, or rescope the PR title/description to the single README link and file the aictrl.dev vs aictrl.ai domain split as a follow-up issue.

Implement the fix on the PR head branch and add a regression test that fails before the fix and passes after.

Why this matters

PR title and issue #106 describe UTM tracking for aictrl.dev "links", but this edits the repo's only aictrl.dev hyperlink while every other user-facing product link remains untagged on the bare https://aictrl.ai domain: github/README.md:3 (GitHub Action marketplace readme), sdks/vscode/README.md:3 and :7 (VS Code marketplace readme), packages/sdk/README.md:64 (rendered as the npm readme of @aictrl/sdk), packages/cli/package.json:11 (homepage), and install:23/:458 (install script output). If aictrl.ai and aictrl.dev feed the same analytics property, issue #106's attribution goal misses all of these higher-traffic surfaces; if they are separate properties, the repo now promotes two canonical product domains and this PR deepens the split. Domain equivalence could not be confirmed from the repo alone.

Aictrl is a fork of the [OpenCode](https://opencode.ai) project and is licensed under the MIT License.

---

[aictrl.dev](https://aictrl.dev/?utm_medium=referral&utm_source=github&utm_campaign=cli&utm_content=readme)

[aictrl-dev]

Code review

Verdict: Looks good — only minor / nit comments below. · 🔴 0 · 🟠 0 · 🟡 1 · ⚪ 0 · 0/1 resolved

• 🟡 README.md:125 — UTM rollout: other product links in repo remain untagged

🤖 Fix all 1 open findings with your agent

Fix the following code review findings on aictrl-dev/cli PR #107 (head branch).
Run the relevant tests/linters after each change.

1. README.md:125 — UTM rollout: other product links in repo remain untagged
   Detail: PR title and issue #106 describe UTM tracking for aictrl.dev "links", but this edits the repo's only aictrl.dev hyperlink while every other user-facing product link remains untagged on the bare https://aictrl.ai domain: github/README.md:3 (GitHub Action marketplace readme), sdks/vscode/README.md:3 and :7 (VS Code marketplace readme), packages/sdk/README.md:64 (rendered as the npm readme of @aictrl/sdk), packages/cli/package.json:11 (homepage), and install:23/:458 (install script output). If aictrl.ai and aictrl.dev feed the same analytics property, issue #106's attribution goal misses all of these higher-traffic surfaces; if they are separate properties, the repo now promotes two canonical product domains and this PR deepens the split. Domain equivalence could not be confirmed from the repo alone.
   Suggested fix: Either extend the same campaign (utm_medium=referral&utm_source=github&utm_campaign=cli with a per-surface utm_content, e.g. action-readme / vscode-readme / sdk-readme) to the product links in github/README.md, sdks/vscode/README.md, and packages/sdk/README.md, or rescope the PR title/description to the single README link and file the aictrl.dev vs aictrl.ai domain split as a follow-up issue.

📋 Out-of-diff findings (1)

Sev	Location	Finding
🟡	README.md:125	UTM rollout: other product links in repo remain untagged

Reviewed 1 files · 0 inline · view all 1 findings ↗

---

aictrl · AI code review for fast-moving teams · aictrl.dev