npm: publish as scoped @your_conscience/dotagents

[yourconscience]

Summary by Sourcery

Publish dotagents as the scoped @your_conscience/dotagents npm package and align release checks and installation documentation with the new name.

Enhancements:

• Publish the npm package under the scoped name @your_conscience/dotagents and update installation guidance accordingly.

CI:

• Update release checks to detect previously published versions of the scoped npm package.

Documentation:

• Update README and website installation commands to use the scoped npm package name.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

The PR migrates npm publishing and installation guidance from the unscoped dotagents package to @your_conscience/dotagents, keeping release duplicate detection and all documented install commands consistent with the new package name.

File-Level Changes

Change	Details	Files
Rename the npm package to the scoped @your_conscience/dotagents package and update release-time existence checks.	Change npm package metadata to the scoped name. Check and report the scoped package/version during GitHub release publishing. Update npm installation commands in user-facing documentation.	npm/package.json .github/workflows/release.yml README.md docs/site/index.html

---

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.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="npm/package.json" line_range="2" />
<code_context>
 {
-  "name": "dotagents",
+  "name": "@your_conscience/dotagents",
   "version": "0.0.0-dev",
   "description": "Dotfiles for your AI agents: one ~/.agents repo synced to every coding agent.",
</code_context>
<issue_to_address>
**issue (broader_impact):** After the package is renamed to `@your_conscience/dotagents`, the CLI's postinstall recovery message still instructs users to run `npm rebuild -g dotagents`; that command targets the old unscoped package and does not reliably rebuild the installed scoped package.

**Triggers:** When the postinstall download fails or the installed binary is missing.

**Suggested fix:** Update the recovery command to `npm rebuild -g @your_conscience/dotagents` and update any other user-facing references to the old package name.
</issue_to_address>

Sourcery assessment

Needs a human reviewer. 1 finding to address first, and if the scope or package identity is wrong, the release workflow can publish versions under a name that users cannot install as expected, and those published artifacts are not removed by reverting this change. The issue is bounded and repairable by deprecating or republishing the affected package versions.

Blocking findings: npm/package.json:2

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue (broader_impact): After the package is renamed to @your_conscience/dotagents, the CLI's postinstall recovery message still instructs users to run npm rebuild -g dotagents; that command targets the old unscoped package and does not reliably rebuild the installed scoped package.

Triggers: When the postinstall download fails or the installed binary is missing.

Suggested fix: Update the recovery command to npm rebuild -g @your_conscience/dotagents and update any other user-facing references to the old package name.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c96c14670c

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Update stale operational commands to the scoped name

After this rename, two user-facing commands still target the unscoped package: npm/bin/dotagents.js:13 recommends npm rebuild -g dotagents when the downloaded binary is missing, and scripts/release.sh:41 uses npm view dotagents version to verify a release. The local npm 11.4.2 help defines both arguments as package specs, so these commands act on a different package and cannot rebuild or verify @your_conscience/dotagents; update both as part of the rename.

AGENTS.md reference: AGENTS.md:L50-L50

Useful? React with 👍 / 👎.