chore(L5-130): replace stale 'Helioscope' references in helios-cli docs

[KooshaPari]

User description

Summary

Helioscope (KooshaPari/helioscope) was retired 2026-06-21 per the v12-20 closure
rationale documented in
findings/2026-06-21-helioscope-cancellation-rationale.md.
The canonical codex fork in the Phenotype fleet is now helios-cli (this repo).

Changes

• README.md: replace 'Helioscope' product-name reference with 'Helios CLI';
  add a tombstone callout pointing to the retirement rationale.
• CLAUDE.md: update the project description and 'Project-Specific
  Configuration' paragraph to refer to 'Helios CLI application management'.
• AGENTS.md: update the project description to refer to 'Helios CLI
  application management'.

Classification

Reference	Before	After
README.md L16	STALE — Helioscope applications	ACTIVE — Helios CLI applications
README.md L16	—	TOMBSTONE — > Note: retired 2026-06-21
CLAUDE.md L11, L72	STALE — Helioscope applications	ACTIVE — Helios CLI applications
AGENTS.md L13	STALE — Helioscope applications	ACTIVE — Helios CLI applications

Supersedes

KooshaPari/helioscope (RETIRED 2026-06-21)

Refs

• L5-130 (helioscope retirement follow-up audit)
• L5-130 worklog: worklogs/L5-130-helioscope-cleanup-2026-06-21.json
• L5-130 report: findings/2026-06-21-L5-130-helioscope-retirement-cleanup.md

---

CodeAnt-AI Description

Replace stale Helioscope references with Helios CLI naming

What Changed

• Updated the project description in the main docs to use “Helios CLI” instead of “Helioscope”
• Added a retirement note in the README that points to the closure rationale and marks helioscope as retired
• Kept the same project summary wording across the agent guidance files so the repo uses one canonical product name

Impact

✅ Clearer project naming
✅ Fewer outdated references in docs
✅ Easier to find the retirement rationale

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a0520cee34

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Point the tombstone at a final retirement record

For readers using this note to verify the status of KooshaPari/helioscope, the linked docs/rationalization/helioscope-absorption.md does not document that it “was retired 2026-06-21”; it still lists archiving as a separate ops PR that was “not done” and later as a follow-up to open archive PRs. This makes the README’s tombstone internally contradictory unless the link is changed to the final retirement rationale or the local rationale is updated.

Useful? React with 👍 / 👎.