docs(docker): use the published -full image tag

[w-up]

Summary / 摘要

Fixes #255.

The README described the browser-preloaded Docker image as :full, but GHCR does not publish that tag. The release workflow publishes latest-full and versioned -full tags such as 0.2.1-full.

README 把预装浏览器的 Docker 镜像写成了不存在的 :full。实际发布标签是 latest-full，以及 0.2.1-full 这类版本化 -full 标签。

Changes / 改动

• Replace the nonexistent published :full reference with ghcr.io/knockoutez/wigolo:latest-full.

• Document the versioned -full naming convention.

• Add a runnable published-image example to the installation guide.

• Keep the local build command docker build --target full -t wigolo:full . and explicitly distinguish it from registry tags.

• Add a regression test that checks both public docs advertise latest-full and the stale README wording does not return.

• 将不存在的远端 :full 改为 ghcr.io/knockoutez/wigolo:latest-full。

• 说明版本化镜像统一使用 -full 后缀。

• 在安装文档中增加可直接运行的 published image 示例。

• 保留本地 docker build --target full -t wigolo:full .，并明确它是 local build tag，不是 GHCR tag。

• 增加文档回归测试，防止旧写法再次出现。

Evidence / 证据

The GHCR Registry API currently reports:

latest-full: present
0.2.0-full: present
0.2.1-full: present
full: absent

The repository workflow also generates full-image tags with suffix=-full in .github/workflows/docker-publish.yml.

Verification / 验证

npx vitest run tests/unit/documentation/docker-image-tags.test.ts
Test Files  1 passed
Tests       2 passed

npm run lint
passed

npm run build
passed

git diff --check
passed

The full suite was also run with the inherited NODE_ENV=production removed:

Test Files  9 failed | 709 passed | 3 skipped
Tests       28 failed | 8,344 passed | 11 skipped | 7 todo

None of the failures touched the new documentation test or changed files. They were in existing REPL/readline, browser-pool timeout, health port collision (19999 is already used on this machine), init/TUI timeout, perf-threshold, and live research integration paths.

Scope / 范围

• Documentation and one documentation regression test only.
• No dependency, runtime, Docker workflow, or image changes.
• Contributor agrees to CONTRIBUTING.md and its CLA terms.

Summary by CodeRabbit

• Documentation

  • Clarified Docker image naming for full-featured builds, including latest-full and versioned -full tags.
  • Added installation examples for running the browser-preloaded image without a volume.
  • Documented how to build the full image locally.

• Tests

  • Added checks to ensure Docker documentation references valid full-image tags and avoids invalid tags.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 2d54acec-ee95-4b8b-a217-63c8351920a4

📥 Commits

Reviewing files that changed from the base of the PR and between 74a530f and a4720de.

📒 Files selected for processing (1)

• tests/unit/documentation/docker-image-tags.test.ts

🚧 Files skipped from review as they are similar to previous changes (1)

• tests/unit/documentation/docker-image-tags.test.ts

---

📝 Walkthrough

Walkthrough

Docker documentation now describes published -full image tags, a no-volume run command, and the local full build target. A Vitest suite verifies the latest-full references and rejects the obsolete :full tag.

Changes

Docker image tag documentation

Layer / File(s)	Summary
Document and validate full image tags README.md, docs/installation.md, tests/unit/documentation/docker-image-tags.test.ts	The documentation now uses latest-full and versioned -full tags, documents a no-volume run command, and identifies the local full build target. Tests verify the published tag and reject the obsolete :full tag.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the primary Docker documentation change to use the published -full image tag.
Linked Issues check	✅ Passed	The changes update all identified Docker documentation and add regression coverage for the corrected published tags required by issue #255.
Out of Scope Changes check	✅ Passed	All changes support the linked documentation issue and its regression coverage; no unrelated runtime, dependency, workflow, or image changes are present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@tests/unit/documentation/docker-image-tags.test.ts`:
- Around line 15-18: Update the test case around readme to assert that the
published ghcr.io/knockoutez/wigolo:full registry identifier is absent from both
the README content and docs/installation.md. Keep the local wigolo:full build
target valid and avoid relying only on the prose fragment about preinstalling
the browser engine.
- Line 5: Update the directory resolution used by the test around repoRoot to
avoid relying on import.meta.dirname across all advertised Node.js 20 versions;
derive the path from import.meta.url instead, unless you explicitly raise the
documented and package engine minimum to Node.js 20.11+ consistently.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: fabd6851-c7d1-48de-b6fe-512384956f06

📥 Commits

Reviewing files that changed from the base of the PR and between b3ccf92 and 74a530f.

📒 Files selected for processing (3)

• README.md
• docs/installation.md
• tests/unit/documentation/docker-image-tags.test.ts

[KnockOutEZ]

Hi @w-up — thank you for this PR, and I'm sorry it's been sitting here without a proper review.

I've been heads-down building some pretty big features and improvements for wigolo, and as a solo dev, shipping that while also reviewing and maintaining every issue and PR has been genuinely hard. This one isn't forgotten — it just hasn't had the attention it deserves yet.

I'd really appreciate your patience here. I'm going to work through the open PRs and issues properly over the next few weeks (sooner if I can free up), and I'll follow up right here.

In the meantime, the wigolo Discord is open if you'd like to follow what's being built, ask questions, or nudge me directly: https://discord.gg/BkUUgz2bNF

Thanks again for contributing, and for understanding — it genuinely means a lot. 🙏