docs: record the 0.7.0 ClawHub listing landing on a retry

[modusensus]

Summary

• AGENTS.md's ### ClawHub registry recorded "the 0.7.0 push never landed". That was true when written and is now superseded — both slugs read pass | clean | 0.7.0.
• Records the retry that went through (Update submitted for euthyna@0.7.0 and the same for euthyna-en, first attempt, no flag added, nothing forced) and the seven settle reads: read 1 still 0.6.0, reads 2–5 fail | card.missing with the English edition additionally security=suspicious, reads 6–7 pass | clean | 0.7.0. The existing "a push is not a listing" fact is now measured with numbers instead of asserted.
• States one attribution limit rather than smoothing it over: a one-shot local re-push scheduled minutes before the retry has consumed itself, and listing reads lag a queued submission by several minutes, so which submission moved latest is not determinable from the evidence on hand. The invariant the fail-closed pre-read guard protects is unaffected — both submissions carried the same version and the same flags.
• The 0.7.0 npm bullet now points at the resolved state instead of leaving the reader with a stale "did not publish".

Documentation only: no code, no workflow, no version, no release touched. npm was not re-published and the tag, provenance, and GitHub release were already correct.

Test plan

• npm test on the branch → 246 tests, 245 pass, 0 fail, 1 skip (the bsdtar-keyed exploit case, same as every Git Bash run on this machine, where GNU tar 1.35 precedes System32's tar.exe)
• Both slugs re-read after the push: pass | clean | 0.7.0 for euthyna and euthyna-en
• AGENTS.md is English-only by convention — confirmed no CJK survives in the added lines, and the added text keeps the file's ~90-column prose wrap
• CI green (test matrix × Node 20/22/24, live licence check, golden bench round)

Summary by Sourcery

Record the successful resolution of the ClawHub 0.7.0 listings and replace the stale publication-failure account with the observed registry outcome.

Enhancements:

• Update the project records to document that the ClawHub 0.7.0 listings eventually settled successfully after a registry-side retry, including the observed propagation delay and attribution limits.

Documentation:

• Correct the 0.7.0 publication status in AGENTS.md and record the measured listing-settlement behavior for both package slugs.

[sourcery-ai]

Sorry @modusensus, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 4 days and 12 hours by commenting @sourcery-ai review. Upgrade to get a review now.

[sourcery-ai]

Reviewer's Guide

Documentation-only update to AGENTS.md replaces the stale 0.7.0 ClawHub failure record with measured evidence of a successful retry and delayed listing convergence, while explicitly preserving the attribution limitation and fail-closed publishing invariant.

Sequence diagram for ClawHub retry and listing convergence

sequenceDiagram
    participant Retry as clawhub-repush.sh
    participant Registry as ClawHub registry
    participant Verify as clawhub-verify.sh

    Retry->>Registry: Update submitted for euthyna@0.7.0
    Retry->>Registry: Update submitted for euthyna-en@0.7.0
    Verify->>Registry: Read listing state 1
    Registry-->>Verify: pass | clean | 0.6.0
    loop Reads 2-5
        Verify->>Registry: Read listing state
        Registry-->>Verify: fail | card.missing
        Registry-->>Verify: euthyna-en additionally security=suspicious
    end
    loop Reads 6-7
        Verify->>Registry: Read listing state
        Registry-->>Verify: pass | clean | 0.7.0
    end

Loading

File-Level Changes

Change	Details	Files
Updates the historical ClawHub registry record to document that the 0.7.0 retry submitted both listings successfully and that they eventually settled at a clean 0.7.0 state.	Replaces the stale claim that the 0.7.0 push never landed with the observed registry failure and later recovery. Records the retry output for both slugs, including unchanged flags and no forced publish. Documents seven three-minute verification reads, including the transient stale and failing states before both listings reached `pass	clean

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.