chore: rename to @ora-ai/ax-nextjs and prepare for npm publishing - #26
Merged
Merged
Conversation
The planned name @ora-ai/ax was claimed on npm (2026-08-14) by the Ora team's own CLI (eralabs-ai/ora-cli), so the package is now @ora-ai/ax-nextjs; the CLI bin stays `ax`. Golden reports regenerated: the longer generated-by marker shifts twin byte/token counts. Publish readiness on top of the rename: - package.json: repository/homepage/bugs/keywords (repository is required for npm provenance), Next peer narrowed to >=15 (the only major CI builds against) - MIT LICENSE (Era Labs) at the root and in the package dir; README copied into packages/ax so the npm page and tarball carry one - release.yml: changesets version-PR/publish flow from CI with provenance; RELEASING.md documents the NPM_TOKEN setup and the canary -> latest promotion - changesets pre-release mode entered with tag `canary`, so the pending changesets produce 0.1.0-canary.0 under the canary dist-tag - scripts/tarball-e2e.mjs + CI jobs: pack the tarball, publint + attw it, then install it into a scratch Next app with plain npm and run a real build on Node 18.18/20/22 to back the engines claim - ci.yml: `--filter ax` -> `--filter @ora-ai/ax-nextjs` (name-based filters stopped matching after the rename) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Conflicts: README.md and the 17 fixture report goldens. README resolved to main's rewrite (regular-dependency install, toolkit framing) with the @ora-ai/ax-nextjs rename re-applied throughout; packages/ax/README.md and RELEASING.md's install line updated to match. Goldens regenerated from the merged source (pnpm reports:regen) rather than hand-merged, so they carry both main's declared-entry-auth report section and the renamed generated-by marker; reports:verify passes on all 17. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The report directory now matches the tool's name: REPORT_OUTPUT_PATH moves to .ax/report.json, with the wizard labels, help text, scripts, CI comments, gitignore, and READMEs following. The `ora` check-language surface (report.ora.checks, ora-checks.ts, oraCheckNotes) is unchanged — that names Ora's scoring vocabulary, not a path. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Brings in the /404.md wayfinding-guide feature (PR #31). Conflicts were the 17 report goldens (both sides regenerated them); resolved by regenerating from the merged source, so the goldens and the new twins.golden/404.md files carry the renamed generated-by marker and the 404-guide content together. One stale marker assertion in generate.test.ts updated to the renamed package. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Add a "Try it before release" section so reviewers can install the plugin from a pnpm-packed tarball before it's published to npm. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Brings in the flagship fixture-corpus consolidation (PR #32). Old fixtures deleted on main resolved as deletions; the surviving goldens were regenerated from the merged source (8 snapshots now, down from 17). The new corpus and mutation harness were authored against the pre-rename names, so the sweep re-applied @ora-ai/ax-nextjs across the new fixtures and fixed scripts/mutation-tests.mjs reading .ora/report.json (4 spots) — all mutation probes pass after the fix. dogfood-middleware.mjs keeps main's flagship retarget plus the renamed import path. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
@ora-ai/ax— the name resolved in PLAN.md open question #7 — was claimed on npm on 2026-08-14 by the Ora team's own CLI (published fromeralabs-ai/ora-cli). This PR renames the package to@ora-ai/ax-nextjs(the CLI bin staysax), renames the report directory to match the tool, and does the remaining work to make the repo npm-publishable — the first canary is one merged Version-Packages PR away.What's in here
Package rename (
@ora-ai/ax→@ora-ai/ax-nextjs)generated-bymarkers (including regex-escaped forms)pnpm reports:regen) — the longer marker shifts twin byte/token countsReport directory rename (
.ora/report.json→.ax/report.json)REPORT_OUTPUT_PATHplus wizard labels, help text, scripts, CI comments, gitignore, READMEsoracheck-language surface is untouched —report.ora.checks,ora-checks.ts,oraCheckNotesname Ora's scoring vocabulary, not a pathPublish metadata
repository(required for provenance) /homepage/bugs/keywordsLICENSE(Era Labs) at root and inpackages/ax/; README shipped in the package dir>=15— the only major CI builds againstRelease engineering
release.yml: changesets flow — merging the auto-maintained "Version Packages" PR builds and publishes from CI with npm provenance; safe to land withoutNPM_TOKEN(the token is only exercised on actual publish)RELEASING.md: one-timeNPM_TOKENsetup and canary → latest promotioncanarytag): pending changesets produce0.1.0-canary.0under thecanarydist-tag, so a plainnpm install @ora-ai/ax-nextjsresolves nothing untillatestis promotedPublish-critical tests (new CI jobs)
package: pack the tarball,publint+@arethetypeswrong/cli(esm-only profile)tarball-e2e: install the packed tarball into a scratch Next app with plain npm and run a real build + postbuild on Node 18.18 / 20 / 22 — backing theenginesclaim and catchingfiles-allowlist gaps, deps misfiled as devDeps, and bin-shim breakageMerges from main (kept current throughout): declared-entry-auth (#25), README rewrite (#28–#30), 404 wayfinding guide (#31), and the flagship fixture-corpus consolidation (#32) — each resolved by regenerating goldens from the merged source and re-applying the renames to newly-landed code (incl.
scripts/mutation-tests.mjsreading the old.ora/path).Verification
publintclean;attwgreen (esm-only).ax/report.jsonpathFollow-ups (not in this PR)
NPM_TOKENrepo secret (see RELEASING.md) and confirm "Allow GitHub Actions to create and approve pull requests" is enabled — release.yml needs it to open the Version Packages PRreportVersionto.ax/report.jsonroute-tree,find-config-file,validation-errors,config-schema,server-card-record,ajv-instancegenerated-bymarkers are no longer recognized)🤖 Generated with Claude Code