chore: update package name

[NamanGarg20]

Greptile Overview

Greptile Summary

Updates the npm package name from agi to @agi_inc/agi-js and refreshes the lockfile metadata (including optional platform binary versions).

Main merge blocker: package.json still contains a smoke test script that embeds an AGI_API_KEY literal; this should be removed so credentials are only supplied via environment/CI secrets.

Confidence Score: 3/5

• This PR is mostly safe to merge but includes a credential leak that should be fixed first.
• Changes are limited to package metadata, but a hardcoded API key in the test script is a real secret-management issue that should be removed before merging.
• package.json

Important Files Changed

Filename	Overview
package.json	Renames the package to @agi_inc/agi-js; repo still contains a hardcoded AGI_API_KEY in the smoke test script that should be removed.
package-lock.json	Updates lockfile package name and bumps optional platform binary packages to 0.4.0; no functional issues found in the lockfile changes.

Sequence Diagram

sequenceDiagram
  participant Dev as Developer/CI
  participant NPM as npm
  participant Pkg as package.json
  participant Test as vitest

  Dev->>NPM: npm run test:smoke
  NPM->>Pkg: read scripts.test:smoke
  Pkg-->>NPM: provide command string
  NPM->>Test: run smoke test
  Test-->>Dev: pass/fail

Loading

[JacobFV]

lgtm

[greptile-apps]

_{2 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Additional Comments (1)

package.json
Hardcoded API key

test:smoke sets AGI_API_KEY to a literal value in the script, which will leak to anyone with read access and can be inadvertently used in CI. Please change the script to rely on a user/CI-provided env var (or omit setting it) and have the smoke test instruct/fail when AGI_API_KEY isn’t set.

Prompt To Fix With AI

This is a comment left during a code review.
Path: package.json
Line: 26:26

Comment:
**Hardcoded API key**

`test:smoke` sets `AGI_API_KEY` to a literal value in the script, which will leak to anyone with read access and can be inadvertently used in CI. Please change the script to rely on a user/CI-provided env var (or omit setting it) and have the smoke test instruct/fail when `AGI_API_KEY` isn’t set.

How can I resolve this? If you propose a fix, please make it concise.