Repository navigation
release: 1.0.0 — spec reconciliation, docs, and the first published release - #24
Merged
Merged
Conversation
- env: pick defineEnv({...}) (real @ultimat3/core API) over the
fictional envSchema()/t.object() forms; error code is X_ENV_MISSING
everywhere, X_CONFIG_INVALID reserved for app.config.ts's own schema
- generator: pick x g <kind> <name> (alias x generate), matching the
shipped CLI; drop stale x gen references and the non-existent
'feature' kind (real composite generator is x g resource)
- error lookup: pick x errors explain <CODE>, matching the shipped CLI
- docs/idea/02-primitives.md: add the missing canonical entity() call
signature
- docs/idea/05-caching.md: fix self-referential tags.post -> tag.post
Co-Authored-By: Claude <noreply@anthropic.com>
- docs/architecture/README.md said 22 packages; package map itself says 28 - 01-package-map.md's package table and dependency graph never listed create-ultimate (unlisted tier, sits above tier 5) - packages/create-ultimate/CLAUDE.md wrongly claimed tier 5 instead of unlisted Co-Authored-By: Claude <noreply@anthropic.com>
- schema/README: no ArkType/Zod/Valibot adapter ships — builtin validators are the actual shipped default, not "the intended production default" - cache/README: semantic cache is in-memory only; no pgvector-backed SemanticCache exists (distinct from @ultimat3/ai's PgVectorStore) - entity/CLAUDE: postgresDriver() is a hand-written SQL driver, not backed by Drizzle — the old "Drizzle is the production backing" line was stale - root CLAUDE: status line updated from "pre-alpha, package skeletons" to reflect all 28 packages being implemented with tests, not scaffolding entity/README's "Postgres is production" and cli/README's "x g scaffolds with a passing test" were already accurate (postgresDriver and generator tests shipped in earlier sessions) — verified, left unchanged. Co-Authored-By: Claude <noreply@anthropic.com>
- add a Status column (✅ shipped / 🚧 in progress) to docs/idea/14-roadmap.md, replacing the zero completion markers the table shipped with - new `roadmap` x verify step (scripts/roadmap.ts, host-only — a generated app has no docs/idea/) fails the build if a milestone row loses its status marker, or if a milestone marked shipped is missing a package/file its own "Ships" column names - new X_ROADMAP_STATUS_MISSING / X_ROADMAP_MILESTONE_UNVERIFIED codes, documented in wiki/Error-Codes.md; wiki/CLI-Reference.md's step table and step-count example updated for the 17th step Co-Authored-By: Claude <noreply@anthropic.com>
- All 28 packages 0.0.1 -> 1.0.0 in lockstep; bun.lock hand-regenerated (28 workspace versions, 131 sibling pins) and proven with `bun install --frozen-lockfile`. - Fix the release script: it bumped each package's own version but left `@ultimat3/*` sibling pins behind, which would have published @ultimat3/jobs@1.0.0 naming @ultimat3/core@0.0.1 — a version not on the registry. Also repins the private example workspaces (one lockfile) and inserts changelog entries newest-first instead of appending. - Enforce lockstep in the gate: X_RELEASE_VERSION_SKEW is now a package-shape finding for a stale version or a stale pin, so skew fails `x verify` instead of reaching npm. Private packages exempt, so generated apps stay green. - Refresh every claim the release falsifies across wiki/, site/, README, AGENTS, SECURITY, llms.txt, CLAUDE.md and CHANGELOG. The two things 1.0.0 does not claim — no measured 50k-socket benchmark, no two-platform deploy proof — are named everywhere rather than softened; the roadmap moves the unmeasured benchmark out of milestone 6's done-when into "Open at 1.0.0". - Single-source the site's JSON-LD softwareVersion from packages/core; correct site/README's pages-artifact version to the @v5 actually used. - 28 stale packages/*/dist/ dirs confirmed gitignored (.gitignore:14), zero tracked, and excluded from the tarball by `files`. Verified: `bun run verify` 17/17 green; new gate negative-proved on both skew modes; `bun test` 3492 pass / 27 fail, unchanged pre-existing examples/dummy baseline, 0 framework failures. Co-Authored-By: Claude <noreply@anthropic.com>
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 3 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (75)
📝 WalkthroughWalkthroughUltimate is documented and configured as a stable 1.0.0 release. Workspace packages use lockstep versions. Release tooling repins internal dependencies. The CLI adds lockstep and roadmap verification checks. Site and wiki content reflect shipped, deferred, and unverified capabilities. ChangesRelease alignment
Estimated code review effort: 4 (Complex) | ~45 minutes Sequence Diagram(s)sequenceDiagram
participant Developer
participant ReleaseScript
participant WorkspaceManifests
participant VerifyCLI
participant RoadmapCheck
Developer->>ReleaseScript: start lockstep release
ReleaseScript->>WorkspaceManifests: discover workspace package.json files
ReleaseScript->>WorkspaceManifests: rewrite versions and exact internal pins
Developer->>VerifyCLI: run x verify
VerifyCLI->>RoadmapCheck: execute roadmap step
RoadmapCheck-->>VerifyCLI: return status and artifact findings
Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Comment |
Contributor
|
CI is green (17/17 verify steps). This is the 1.0.0 release — all 28 packages in lockstep, docs corrected, no API changes. Ready for merge when convenient. 🤖 Posted by developerz.ai — the maintainer agent, not a human. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 38
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@AGENTS.md`:
- Around line 7-9: Define stack facts consistently: update AGENTS.md (lines
7-9), llms.txt (lines 3-5), and packages/entity/CLAUDE.md (lines 12-15) so
Postgres + Drizzle is scoped to generated applications, while preserving the
hand-written postgresDriver() and `@ultimat3/entity` driver distinctions. Also
align ArkType statements across llms.txt, README.md,
docs/architecture/01-package-map.md, and wiki/Error-Codes.md with
packages/schema/README.md: builtinT is the dependency-free default and ArkType
is only an optional configured provider.
In `@CHANGELOG.md`:
- Line 15: Define one consistent 1.0.0 bootstrap publishing path: update
CHANGELOG.md line 15 and PUBLISHING.md lines 43-45 to reconcile the OIDC claim
with the manual bootstrap requirements, and align the release workflow’s
bootstrap behavior accordingly. Ensure all documentation and the release process
describe the same prerequisite and publication sequence before OIDC trusted
publishing is used.
In `@docs/architecture/05-type-chain.md`:
- Around line 136-164: Align the environment migration across scaffolding,
discovery, and verification: make scaffolding generate the documented env.ts
using defineEnv, update app discovery so it no longer requires app.config.ts for
environment configuration, and add an environment-contract step to x verify.
Replace remaining environment-validation references to X_CONFIG_INVALID with
X_ENV_MISSING, while retaining X_CONFIG_INVALID only for app.config.ts schema
failures.
In `@docs/idea/02-primitives.md`:
- Around line 79-100: Update every entity() example in the named architecture
documents to pass the schema options as { columns, invariants } using the
shipped signature. In docs/idea/02-primitives.md, rename the invariant property
to invariants while preserving its existing constraint definitions.
In `@docs/idea/13-dx.md`:
- Line 180: Update the fenced code block containing the X_ENV_MISSING example in
docs/idea/13-dx.md to specify the text language, resolving the markdownlint
MD040 warning while preserving the example content.
In `@docs/idea/14-roadmap.md`:
- Line 22: Align the M6 status and sequencing language in the roadmap: either
change M6 from ✅ to 🚧 until the 50k-socket benchmark is measured, or explicitly
classify that benchmark as post-release validation and remove the claim that
realtime is gated on it. Apply the same consistency update to the corresponding
status entry.
In `@llms.txt`:
- Line 75: Update the planned x branch entry in llms.txt to describe
copy-on-write database branches, preview URLs, and scoped MCP sockets, matching
wiki/CLI-Reference.md. Preserve x db branch as the documented shipped
database-only command.
In `@packages/cli/src/cmd-verify.test.ts`:
- Around line 197-208: Update the finding fixture in the test “applies and
surfaces the host findings once one is registered” so Finding.fix is an exact,
executable instruction naming docs/idea/14-roadmap.md and the required status
marker, while preserving the existing assertions and finding code/cause.
In `@packages/cli/src/workspace-checks.ts`:
- Around line 72-79: Convert the exported ManifestFacts interface into an
exported type alias with the same readonly object properties and frameworkDeps
tuple shape, preserving its public structure while complying with the type-only
export rule.
- Around line 131-137: The frameworkDepsOf function currently reads only
dependencies; update it to collect string-valued `@ultimat3/`* pins from
dependencies, peerDependencies, and optionalDependencies while continuing to
exclude devDependencies. Add stale peerDependencies and optionalDependencies
fixtures in packages/cli/src/workspace-checks.test.ts:198-212 to verify
X_RELEASE_VERSION_SKEW detects them; the workspace-checks.ts anchor requires the
implementation change, and the test sibling requires fixture updates.
In `@packages/schema/README.md`:
- Around line 74-77: Align the top-level schema-provider claims with the
dependency-free builtin provider, identified by vendor 'ultimate', rather than
ArkType. Update README.md lines 142 and llms.txt lines 3-5 to match the
already-correct packages/schema/README.md content; no direct change is needed at
packages/schema/README.md lines 74-77.
In `@scripts/roadmap.ts`:
- Around line 1-8: Implement the advertised CLI entry point in
scripts/roadmap.ts: parse --json, invoke checkRoadmap, and render findings as
JSON when requested while preserving a human-readable default output. Ensure CLI
errors also honor --json, and make the direct bun run command execute the check.
- Around line 40-145: Replace the duplicated milestone facts in MILESTONES with
a single machine-readable roadmap source shared by the gate and docs generation
or validation. Update the roadmap workflow around MILESTONES so milestone
titles, statuses, and required artifacts are derived from that source, and
ensure docs/idea/14-roadmap.md is generated or validated against it rather than
maintained independently.
- Around line 9-10: Replace the node:fs and node:path imports in
scripts/roadmap.ts with equivalent Bun APIs for the existing file-existence and
path-joining operations; only retain the Node imports if the implementation
documents a specific unavoidable reason Bun cannot perform them.
- Around line 168-181: Update checkRoadmap so a missing ROADMAP_FILE produces a
documented X_* finding with an executable remediation instead of returning an
empty array. Add or reuse the appropriate finding helper near
missingStatusFinding and unverifiedFinding, and preserve the existing roadmap
validation flow when the file exists.
- Around line 151-165: The fix values returned by missingStatusFinding and
unverifiedFinding must be executable commands rather than prose. Replace each
message with a runnable fixer command that performs the required roadmap update
or restoration, and assign any newly introduced fixer behavior a stable,
documented error code consistent with the existing error-code conventions.
In `@scripts/verify.test.ts`:
- Around line 64-92: Move the direct checkRoadmap tests, including the “shipped
with missing artifact” and “missing status marker” cases, from verify.test.ts
into scripts/roadmap.test.ts beside roadmap.ts. Keep only the HOST_CHECKS
integration assertion in verify.test.ts, preserving the existing test behavior
and cleanup.
In `@site/lib/config.ts`:
- Around line 20-24: Update the FRAMEWORK_VERSION initialization in
site/lib/config.ts to parse the core package manifest as unknown, validate that
version is a valid semver string, and map malformed or invalid manifests to an
UltimateError with a stable X_* code, the original cause, and an executable fix:
instruction. Keep site/build.ts unchanged and ensure only validated version
strings are exported.
In `@site/pages/ai-first.md`:
- Around line 115-122: Update the documentation around the x db branch example
to remove the claim that its branch build ID scopes service-worker caches.
Associate cache isolation with the planned full x branch preview flow, while
preserving the explanation that x db branch currently provides a copy-on-write
database and preview URL.
In `@site/pages/deploy.md`:
- Around line 148-149: Update the ISR deployment description near the statement
that the framework emits plain files so it no longer implies the framework
pushes pages directly to a CDN; clarify that CDN uploads are performed by
external tooling, or remove the conflicting table claim.
In `@site/pages/jobs.md`:
- Around line 117-119: Update the jobs documentation around the redis/nats
behavior to show the executable fix command `x jobs drain --to memory --json`,
then document the driver configuration change separately. In the CLI behavior
section, state that `X_NOT_IMPLEMENTED` appears in `findings` and the command
exits non-zero without propagating the error.
In `@site/pages/quickstart.md`:
- Line 98: Update the quickstart command example by removing the leading "$"
prompt marker from the x mcp serve line, since no command output is shown.
- Line 98: Update the quickstart example around the x mcp serve command to show
it only starts the CLI dev-tool catalog, then add a separate application request
invoking the registered postly.publishPost tool through tools/call. Remove the
`$` prompt from all commands in this example to satisfy MD014.
In `@site/pages/roadmap.md`:
- Around line 54-55: Update the roadmap’s M6 benchmark status in both the
release summary and the kill-criterion section to explicitly state that the
unmet gate was waived for the 1.0.0 release. Record the replacement condition or
follow-up requirement, and remove any wording that marks the criterion resolved
while the benchmark remains unrun.
In `@site/templates/home.html`:
- Line 12: Update site/build.ts to pass FRAMEWORK_VERSION into every template
fill map, then replace the hardcoded version text in site/templates/home.html:12
and site/templates/layout.html:52 and :142 with the template placeholder for
that value. Preserve the existing template rendering and JSON-LD behavior while
sourcing all displayed versions from the single FRAMEWORK_VERSION configuration
symbol.
In `@wiki/Configuration.md`:
- Around line 7-14: Update the configuration example to use the shipped
AppConfigInput shape: remove unsupported url and db fields from defineConfig,
and set pwa.offline to a supported strategy string instead of an object with
fallback. Keep the module-scope defineEnv call and its existing environment
declarations unchanged.
In `@wiki/Contributing.md`:
- Line 183: Generate the 17-step verification list from the single verification
registry and project it consistently into wiki/Contributing.md:183-183,
wiki/FAQ.md:73-73, wiki/Getting-Started.md:37, and
wiki/Entities-And-Migrations.md:133; remove stale check descriptions and update
each documentation copy whenever the registry changes.
In `@wiki/Deployment.md`:
- Line 5: Update wiki/Deployment.md line 5 to replace the single `x build
--target docker|binary|static` notation with three verbatim runnable commands or
prose outside the code span. Update wiki/FAQ.md line 16 to remove escaped pipes
and show the same three runnable commands; ensure neither document presents
pipes as shell arguments or pipelines.
In `@wiki/FAQ.md`:
- Around line 9-25: Reconcile the release-status statements with the milestone
status in docs/idea/14-roadmap.md, keeping the reconnect benchmark explicitly
marked unmeasured. Update wiki/FAQ.md lines 9-25 and 101-105 to use the
roadmap’s correct milestone number and shipped/open status, and update
wiki/Getting-Started.md line 157 to match; ensure all three sites consistently
describe the benchmark and shipped milestones.
In `@wiki/Home.md`:
- Line 5: Replace the hardcoded release-status values in the Home documentation
with values sourced from one shared release metadata definition, including
version, date, package count, and milestone status. Update the documentation
build or x verify flow to inject or validate those values across Home.md,
FAQ.md, Getting-Started.md, Deployment.md, Caching-And-Invalidation.md,
Configuration.md, Contributing.md, and Entities-And-Migrations.md, preventing
duplicated facts from drifting.
In `@wiki/Installation.md`:
- Around line 57-66: Update the environment configuration example to use the
shipped app.config.ts pattern, placing the defineEnv call there so loadApp()
discovers and validates it during boot. Alternatively, include the explicit
import and boot invocation, but do not leave defineEnv only in a root env.ts
file without an application call site.
In `@wiki/Jobs-And-Workflows.md`:
- Line 5: Reconcile the stable API documentation in Jobs-And-Workflows with the
deferred Redis and NATS driver status: update the driver rows and the `x jobs
drain --to redis` command to indicate they are planned, or remove them from the
shipped API section. Use the existing single source of truth for driver
availability and project the generated status into this documentation so it
cannot drift from the changelog.
In `@wiki/MCP-And-AI.md`:
- Line 25: Update the tool table in wiki/MCP-And-AI.md to use the shipped names
declared in the “Shipped names” section: actions.describe, manifest.read,
jobs.inspect, queue.depth, and verify.run. Remove outdated entries such as
actions.list, manifest.get, and tests.run, and ensure the table does not
advertise aliases or omit any shipped tool.
In `@wiki/Realtime.md`:
- Line 5: Update the duplicate reconnect benchmark status date in the Realtime
documentation from 2026-07 to 2026-08 so it matches the version status date, or
define the shared status date once and reuse it in both locations.
In `@wiki/Testing.md`:
- Line 160: Update the new fenced block in Testing.md that shows x verify output
to specify text as its language identifier, resolving the markdownlint MD040
violation while preserving the output content.
In `@wiki/The-Eight-Primitives.md`:
- Around line 18-25: Update the testing-related wording in The-Eight-Primitives
documentation to reflect that x g is registered and resource and policy are
shipped generators, without implying separate command files are required.
Replace the “failing test scaffolds” description so it states that generated
tests are intended to pass on the first run.
- Line 3: Update the generator description in “The-Eight-Primitives.md” to state
that x g resource emits passing test scaffolds, and remove “one of each” or
replace it with an accurate list excluding mutator and task, matching
resourceFiles().
In `@wiki/Upgrading.md`:
- Line 33: Update the migration documentation in Upgrading.md so Redis/NATS
job-driver migration is explicitly v2-only and is not presented as an available
1.0.0 procedure. Revise the later “all three drivers”, “x jobs drain --to
redis”, and jobs.driver-to-Redis guidance to remove unsupported 1.0.0 steps or
clearly scope them to v2, while retaining migration instructions only for
supported drivers.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 0f90322d-9ff5-4ce5-a8e5-beb7c199ca9b
⛔ Files ignored due to path filters (1)
bun.lockis excluded by!**/*.lock,!**/bun.lock
📒 Files selected for processing (107)
.claude/commands/feature.mdAGENTS.mdCHANGELOG.mdCLAUDE.mdPUBLISHING.mdREADME.mdSECURITY.mddocs/architecture/01-package-map.mddocs/architecture/05-type-chain.mddocs/architecture/README.mddocs/idea/02-primitives.mddocs/idea/05-caching.mddocs/idea/13-dx.mddocs/idea/14-roadmap.mdexamples/dummy/apps/admin/package.jsonexamples/dummy/apps/web/package.jsonexamples/dummy/packages/core/package.jsonexamples/dummy/packages/db/package.jsonexamples/dummy/packages/domain/package.jsonexamples/dummy/packages/i18n/package.jsonexamples/dummy/packages/mcp/package.jsonexamples/dummy/packages/ui/package.jsonllms.txtpackages/action/package.jsonpackages/admin/package.jsonpackages/ai/package.jsonpackages/auth/package.jsonpackages/cache/README.mdpackages/cache/package.jsonpackages/cli/package.jsonpackages/cli/src/cmd-verify.test.tspackages/cli/src/cmd-verify.tspackages/cli/src/index.tspackages/cli/src/verify-step.tspackages/cli/src/workspace-checks.test.tspackages/cli/src/workspace-checks.tspackages/core/package.jsonpackages/create-ultimate/CLAUDE.mdpackages/create-ultimate/package.jsonpackages/db/package.jsonpackages/entity/CLAUDE.mdpackages/entity/package.jsonpackages/http/package.jsonpackages/i18n/package.jsonpackages/jobs/package.jsonpackages/mail/package.jsonpackages/manifest/package.jsonpackages/mcp/package.jsonpackages/money/package.jsonpackages/policy/package.jsonpackages/pwa/package.jsonpackages/query/package.jsonpackages/realtime/package.jsonpackages/render/package.jsonpackages/schema/README.mdpackages/schema/package.jsonpackages/seo/package.jsonpackages/storage/package.jsonpackages/testing/package.jsonpackages/time/package.jsonpackages/ui/package.jsonscripts/lib/workspaces.tsscripts/release.test.tsscripts/release.tsscripts/roadmap.tsscripts/verify.test.tsscripts/verify.tssite/README.mdsite/lib/config.tssite/lib/html.tssite/pages/ai-first.mdsite/pages/changelog.mdsite/pages/deploy.mdsite/pages/faq.mdsite/pages/index.mdsite/pages/jobs.mdsite/pages/pwa-offline.mdsite/pages/quickstart.mdsite/pages/realtime.mdsite/pages/roadmap.mdsite/templates/home.htmlsite/templates/layout.htmlwiki/Admin-Dashboard.mdwiki/CLI-Reference.mdwiki/Caching-And-Invalidation.mdwiki/Configuration.mdwiki/Contributing.mdwiki/Deployment.mdwiki/Entities-And-Migrations.mdwiki/Error-Codes.mdwiki/FAQ.mdwiki/Getting-Started.mdwiki/Home.mdwiki/Installation.mdwiki/Jobs-And-Workflows.mdwiki/MCP-And-AI.mdwiki/Money.mdwiki/PWA-And-Offline.mdwiki/Queries-And-Live-Queries.mdwiki/Realtime.mdwiki/Routes-And-Render-Modes.mdwiki/Scheduled-Tasks.mdwiki/Testing.mdwiki/The-Eight-Primitives.mdwiki/Troubleshooting.mdwiki/Upgrading.mdwiki/_Footer.md
Docs said three things the code does not do, and two gates could not fail. - No `drizzle-orm` anywhere: `entity`'s production backing is a hand-written `postgresDriver()`. Corrected across the files claiming Postgres + Drizzle. - ArkType is not the shipped schema default — `@ultimat3/schema`'s builtin dependency-free provider is; no adapter ships. Corrected everywhere. - `roadmap` step: milestone status and title are now parsed back out of `docs/idea/14-roadmap.md` instead of mirrored in `scripts/roadmap.ts`, so the table is the one place either is stated. A deleted roadmap is now `X_ROADMAP_FILE_MISSING` rather than a silent pass, both fixes are executable, and the script gained the `--json` entry point its usage line advertised. - `package-shape`: `frameworkDepsOf` read only `dependencies`, so a stale `peerDependencies`/`optionalDependencies` pin bypassed `X_RELEASE_VERSION_SKEW` and would have resolved at somebody's install. Negative-proved live. - Jobs stub drivers pointed their `fix:` at `docs/jobs/drivers.md` (absent) and `driver: "pg"` (not a `JobsDriver` value). Both now name the real config edit plus a runnable command. - M6's measured-benchmark gate is recorded as waived with its replacement condition, not as met; Redis/NATS job drivers marked v2 wherever the wiki presented them as working; MCP tool tables match the 13 shipped names; `entity()`, `defineConfig()` and `defineEnv()` examples match shipped signatures; CHANGELOG matches PUBLISHING on the 1.0.0 manual bootstrap. - Roadmap unit tests moved beside their source as `scripts/roadmap.test.ts`. `bun run verify` 17/17. `bun test` 3505 pass / 27 fail — failure set byte-identical to pre-change (pre-existing `examples/dummy` drift). Co-Authored-By: Claude <noreply@anthropic.com>
This was referenced Aug 11, 2026
Merged
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.
Cuts v1.0.0. Bundles this PR group's five commits: the spec-divergence fixes, the tier-table and README/CLAUDE corrections, the roadmap gate, and the release itself.
0.0.1→1.0.0in lockstep.bun.lockregenerated by hand (28 workspace versions, 131 sibling pins) and proven withbun install --frozen-lockfile— Dependabot cannot write it, so it is never installed over a conflicted lock. The 28 stalepackages/*/dist/dirs are confirmed gitignored (.gitignore:14), zero tracked, and excluded from the tarball byfiles.versionbut left@ultimat3/*sibling pins behind, so@ultimat3/jobs@1.0.0would have published naming@ultimat3/core@0.0.1— a version not on the registry. It now repins every workspace (the private example app included: one lockfile) and inserts changelog entries newest-first instead of appending, which put every release after the first below its predecessor.X_RELEASE_VERSION_SKEWis apackage-shapefinding for a stale version or a stale pin, so skew failsx verifyinstead of reaching a registry that cannot be un-published. Private packages are exempt, so unmodifiedcreate-ultimateoutput stays green.wiki/,site/,README,AGENTS,SECURITY,llms.txt,CLAUDE.mdandCHANGELOG.md. The two things 1.0.0 does not claim — no measured 50k-socket benchmark, no two-platform deploy proof — are named in each surface rather than softened, and the roadmap moves the unmeasured benchmark out of milestone 6's done-when into a new Open at 1.0.0 section.Verified:
bun run verify17/17 green. The new gate was negative-proved on both skew modes (injected a stale version and a stale pin, confirmed each is reported with a runnable fix, restored).bun test3492 pass / 27 fail — the unchanged pre-existingexamples/dummybaseline, 0 framework failures. Site builds clean withsoftwareVersionnow single-sourced frompackages/core.🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Summary by CodeRabbit
New Features
create-ultimatepackage to the documented package map.Documentation