Point RELEASE.md at the CodeTruss organisation (#36)

The CLI repository moved to the `CodeTruss` organisation on 2026-08-07 and
the npm trusted publisher was reconfigured to match, but docs/RELEASE.md
still named the pre-transfer `DeliriumPulse` account in two places, so both
instructions it printed were wrong.

The attestation command in the "GitHub release" section failed outright:

    $ gh attestation verify codetruss-cli-0.2.43.tgz --repo DeliriumPulse/codetruss-cli
    Error: verifying with issuer "sigstore.dev"      # exit 1

    $ gh attestation verify codetruss-cli-0.2.43.tgz --repo CodeTruss/codetruss-cli
    exit 0

`packages/cli/scripts/release-metadata.mjs` already records that the
transferred `--repo DeliriumPulse/…` slug returns HTTP 404 and must never be
advertised, and test-release-verifier.mjs asserts the generator never emits
it. That guard covers the generated manifest but not this hand-written page,
which contradicted it.

The npm trusted-publisher step named the wrong organisation too. Published
provenance for 0.2.41 records the publisher as
`https://github.com/CodeTruss/codetruss-cli`, workflow `publish-npm.yml` on
`refs/heads/main`, so anyone auditing npm settings against this page would
have looked for an account that no longer owns the repository.

Documentation only: no workflow, generator, or release logic is touched.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

Author: DeliriumPulse

docs/RELEASE.md

@@ -19,7 +19,7 @@ account, npm token, package access, or npm environment approval.
 4. Verify the downloaded archive independently:
 
    ```bash
-   gh attestation verify codetruss-cli-0.2.30.tgz --repo DeliriumPulse/codetruss-cli
+   gh attestation verify codetruss-cli-0.2.30.tgz --repo CodeTruss/codetruss-cli
    shasum -a 256 -c codetruss-cli-0.2.30.tgz.sha256
    ```
 
@@ -38,7 +38,7 @@ publication:
    permits only protected branches. The workflow itself also requires a
    `refs/heads/main` dispatch.
 2. Confirm npm package settings name the GitHub Actions trusted publisher with:
-   organization or user `DeliriumPulse`, repository `codetruss-cli`, workflow
+   organization or user `CodeTruss`, repository `codetruss-cli`, workflow
    filename `publish-npm.yml`, environment `npm`, and allowed action
    `npm publish`. Publishing access must remain `mfa=publish`, which requires
    2FA and disallows conventional publish tokens while permitting the trusted