feat(deno): developer-ecosystem workspace finalisation — root deno.json with workspace field (STEP 7 closeout)#100
Merged
Conversation
…rkspace field (STEP 7 closeout) Completes the STEP 7 workspace finalisation acceptance criterion (1) for developer-ecosystem from hyperpolymath/standards#275: add `deno.json` at repo root with `workspace` array listing all 40 sub-projects that have their own `deno.json`. This was the missing acceptance gate. Per the STEP 6 closure comment on hyperpolymath/standards#273, the per-sub-project migrations were already landed via the cross-cutting workflow-modernisation + tooling sweeps over April-May 2026 (19 of 23 in-scope manifests paired with deno.json; the remaining 4 are dependency-shim Class C npm-publishable consumer artifacts where Deno-native exposure isn't a priority). The workspace-root coordination is the closeout task per STEP 7's body. ## Workspace member breakdown - `affinescript-ecosystem/` (3 members) - `aggregate-library` (1) - `cadre-router` + nested `tea-router-pkg` (2) - `cadre-tea-router` (1) - `coq-ecosystem/coq-jr` (1) - `deno-ecosystem/projects/` (2) - `rescript-ecosystem/` (29 across packages/, cadre-router, cadre-tea-router, idaptik, rescript-*) - `v-ecosystem/v-deno` (1) Top-level tasks `build-all`/`test-all`/`fmt`/`lint` delegate to per-member tasks via `deno task --recursive`. ## What is intentionally NOT included - `rescript-ecosystem/rescript/**` — upstream-fork carve-out (22 manifests) covered by hypatia `:nodejs_detected` `rescript/` path_allow_prefix - `rescript-ecosystem/packages/core/compiler-source/**` — vendored upstream rescript snapshot (45 manifests, separate version line from the active `rescript/` fork) - `affinescript-ecosystem/.../editors/{vscode,tree-sitter-affinescript}/**` — VSCode + tree-sitter Class C carve-outs - 4 dependency-shim Class C npm-publishable manifests (`affinescript-vite`, `rescript-grpc-runtime`, `rescript-string-power`, `rescript-vite-config`) — declared in STEP 6 closure as residual After this PR merges, developer-ecosystem satisfies acceptance criterion (1) of hyperpolymath/standards#275; the remaining residuals are out-of-scope per the umbrella body's `Out of scope` carry-forward. Refs hyperpolymath/standards#275 (this completes the developer-ecosystem portion) Refs hyperpolymath/standards#253 (umbrella npm → Deno migration) Refs hyperpolymath/standards#273 (STEP 6 closeout — substantially-done declaration) Co-Authored-By: Claude Opus 4.7 (1M context) <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
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.
Summary
Completes the STEP 7 workspace finalisation acceptance criterion (1) for
developer-ecosystemfrom hyperpolymath/standards#275: adddeno.jsonat repo root withworkspacearray listing all 40 sub-projects with their owndeno.json.Per the STEP 6 closure (hyperpolymath/standards#273), the per-sub-project migrations were already landed via the cross-cutting workflow-modernisation + tooling sweeps over April-May 2026 (19 of 23 in-scope manifests paired with
deno.json; the remaining 4 are dependency-shim Class C npm-publishable consumer artifacts where Deno-native exposure isn't a priority). The workspace-root coordination is the closeout task per STEP 7's body.Workspace member breakdown (40 members)
affinescript-ecosystem/affinescript-deno-test,rattlescript/affinescript/packages/{affine-js,affine-ts}aggregate-librarycadre-router+ nestedtea-router-pkgcadre-tea-routercoq-ecosystem/coq-jrdeno-ecosystem/projects/beamdeno,deno-bunbridge(always Deno-native)rescript-ecosystem/v-ecosystem/v-denoTop-level tasks
build-all/test-all/fmt/lintdelegate to per-member tasks viadeno task --recursive.What is intentionally NOT included
:nodejs_detectedrescript/path_allow_prefix13.0.0-alpha.1vsalpha.3of the active fork)affinescript-vite,rescript-grpc-runtime,rescript-string-power,rescript-vite-config— declared in STEP 6 closure as residualAfter this PR merges, developer-ecosystem satisfies acceptance criterion (1) of hyperpolymath/standards#275; the remaining residuals are out-of-scope per the umbrella body's
Out of scopecarry-forward.Test plan
deno task --versionrecognises the workspace root:nodejs_detectedscan stays quiet (zeropackage-lock.jsonin repo)Refs hyperpolymath/standards#275 (this completes the developer-ecosystem portion).
Refs hyperpolymath/standards#253 (umbrella npm → Deno migration).
Refs hyperpolymath/standards#273 (STEP 6 closeout — substantially-done declaration).
🤖 Generated with Claude Code