Link back to citecue.com, and cut 1.2.1

[henry-mosh]

The plugin named the service constantly and linked to it nowhere a customer would look.

The finding that shaped this

The live directory page has 90 anchors and not one points to citecue.com. wp.org does not auto-link a bare URL, so the https://citecue.com in "External services", plus the terms and privacy URLs, have been rendering as dead plain text. Markdown links do render there (verified against Yoast's page, whose description carries 27 working links), so the only way onto that page is readme text written as links.

Neither Plugin URI nor Author URI produces a visible link on the modern directory page — "By citecue" goes to the wp.org profile. So the readme is the whole story for that page.

readme.txt — the directory page

• First sentence of the description now links CiteCue. Most prominent prose on the page.
• The account-prerequisite sentence is a link rather than parenthesised plain text.
• Installation states the prerequisite before step 1 rather than at step 3.
• A closing description line naming the service.
• "External services" URLs, including terms and privacy, converted from plain text to links.

Admin screens

• Not-yet-connected settings screen: a line under the Connect button saying an account is a precondition, linked.
• Connected settings screen: a line under the status card attributing the served pages to CiteCue, linked.
• Plugins list: a CiteCue.com link in the plugin's row meta.
• Author URI moves from app.citecue.com (the login app) to citecue.com — the link behind "By CiteCue" on the wp-admin Plugins screen.
• Plugin URI stays on the source repository.
• Citecue_Settings::SITE_URL holds the URL — deliberately not overridable the way DEFAULT_API_BASE is, since a self-hosted deployment moves the API, not the website.

Version

Cut as 1.2.1. v1.2.0 was tagged and released on GitHub but never pushed to the directory — wp.org serves 1.1.2 and tags/1.1.2/ is the only tag in SVN — and main has since moved past that tag with the #15/#16 copy work. Publishing 1.2.1 takes wp.org from 1.1.2 to 1.2.1 in one update with the 1.2.0 features intact, without rewriting a tag that already has a public release asset.

Verification

• php -l clean; vendor/bin/phpcs passes on all 4 files.
• bin/build-plugin-zip.sh HEAD builds cleanly at 1.2.1, 16 files, no tests or CI config swept in.
• vendor/bin/phpunit not run — fails at bootstrap with db_connect_fail locally. CI covers it.
• The markdown links can only be confirmed rendered once published; the syntax is verified working on the platform.

🤖 Generated with Claude Code