[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7584FF36RAWWA74TKAD4YW5":3,"skill-same:01M7584FF36RAWWA74TKAD4YW5":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":29,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7584FF36RAWWA74TKAD4YW5","aube-bump",null,"Bump nub's vendored aube engine to a newer jdx\u002Faube upstream. Invoke (via the Skill tool) whenever you need to pull upstream aube changes into `vendor\u002Faube\u002F**` — a new release, or arbitrary commits. Encodes the venue-less merge (build an ephemeral merge commit from nub's own objects with `git commit-tree`; no clone, no `nub-fork`, no push-back) and the two-conflict-list methodology: git's markers find TEXTUAL conflicts, the compiler finds SEMANTIC ones, both lists are machine-generated and exhaustive, so you never hand-review a diff. Also covers merge-base correctness (the single biggest lever), merge-not-rebase, `rerere`, the nub delta inventory that must survive, and the nub-side breaks upstream feature-gating causes. Supersedes the older `aube-sync` skill.","nubjs\u002Fnub","nubjs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6785695?v=4","01M7583N3EYYHSNB6FJQXCDMQH","Nub","01M7583N44MVMSN8385QEF3C8V",4440,"MIT","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Faube-bump\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: aube-bump\ndescription: >-\n  Bump nub's vendored aube engine to a newer jdx\u002Faube upstream. Invoke (via the\n  Skill tool) whenever you need to pull upstream aube changes into\n  `vendor\u002Faube\u002F**` — a new release, or arbitrary commits. Encodes the\n  venue-less merge (build an ephemeral merge commit from nub's own objects with\n  `git commit-tree`; no clone, no `nub-fork`, no push-back) and the\n  two-conflict-list methodology: git's markers find TEXTUAL conflicts, the\n  compiler finds SEMANTIC ones, both lists are machine-generated and exhaustive,\n  so you never hand-review a diff. Also covers merge-base correctness (the\n  single biggest lever), merge-not-rebase, `rerere`, the nub delta inventory\n  that must survive, and the nub-side breaks upstream feature-gating causes.\n  Supersedes the older `aube-sync` skill.\n---\n\n# Bumping vendored aube to a new upstream\n\n## Mental model\n\n`vendor\u002Faube\u002F**` is plain tracked files in nub's history — no submodule, no pin. An aube change is an ordinary nub PR touching `vendor\u002Faube\u002F**`. Everything lives in the nub repo; you do not need a clone of `nubjs\u002Faube` and you do not touch the `nub-fork` branch.\n\n| Thing | Where |\n| --- | --- |\n| Source of truth | `vendor\u002Faube\u002F**` on nub `main` |\n| Upstream | `jdx\u002Faube`, as the `aube-upstream` remote |\n| The base we're on | `vendor\u002Faube\u002FUPSTREAM` (commit + tag) |\n| Merge venue | built on demand, thrown away |\n\n**The venue is derived, not stored.** A 3-way merge needs a commit whose tree is the vendored state and whose ancestry contains the upstream base — both already in nub's object store. Deriving it at bump time means it cannot drift, and `rerere`'s cache lives in nub and persists across bumps.\n\n## The core: two machine-generated conflict lists\n\nYou never hand-review the upstream diff.\n\n1. **Textual conflicts** — `git merge` gives every place both sides edited the same lines. One merge, one complete list, resolved once. This is what a merge buys over a rebase.\n2. **Semantic conflicts** — `cargo check --workspace --all-targets` gives every place both sides edited *different* lines in ways that don't compose (upstream adds a required param, nub's caller keeps the old arity; upstream renames a field under a nub-added method). Git merges text, not meaning, so these produce **zero conflict markers and a perfectly clean merge**.\n\n\"All conflicts resolved\" is worthless as a correctness signal — the compiler is the second half of the merge. List 2 is layered: each fix lets the compiler reach further, so iterate to a clean exit.\n\n**The biggest lever is merge-base correctness.** Conflict count is a function of the base, not of how far upstream moved: a stale base re-presents changes you already have as conflicts (once, 72 files \u002F 205 hunks instead of 23 \u002F 48). `vendor\u002Faube\u002FUPSTREAM` exists so this is a fact you read — keep it accurate.\n\n## Recipe\n\nWork in a nub worktree off latest `origin\u002Fmain` (see the `worktree` skill). Never touch the shared tree.\n\n**Mechanics are a script, not shell improvisation.** `scripts\u002Faube-bump.ts` does the deterministic parts: `plan` (base\u002Fdelta sanity), `venue [--reset]` (build the venue + merge + conflict table), `gate` (check\u002Fclippy verdicts), `land` (rsync + UPSTREAM marker + identical-tree check). Run its subcommands instead of retyping the shell. Guarded by `scripts\u002Faube-bump.test.mts`.\n\n**Never archive-overwrite the vendor tree.** `git archive | tar -x -C vendor\u002Faube` throws away the fork delta and turns the bump into N hand-rebuilt features. The venue 3-way merge is the process; the delta survives unless both sides edited the same lines.\n\n**Never iterate the compiler loop in your own context.** After the venue's textual conflicts are resolved (partitioned subagents, below), dispatch ONE agent to own the whole gate — `check -> clippy -> test` iterated to green — with the doctrine and stop conditions in its prompt. The orchestrator reads the summary, not the errors. Iterating error-by-error in the orchestrator's context burned a full session's budget on one bump.\n\n### 1. Read the base and fetch upstream\n\n```sh\ncat vendor\u002Faube\u002FUPSTREAM                       # commit + tag this tree derives from\ngit remote add aube-upstream https:\u002F\u002Fgithub.com\u002Fjdx\u002Faube 2>\u002Fdev\u002Fnull\ngit fetch aube-upstream main\ngit log --oneline \u003Cbase-sha>..aube-upstream\u002Fmain | wc -l    # size of the bump\n```\n\nSanity-check the marker before trusting it — the delta should look like *nub delta only*, not half of upstream:\n\n```sh\ngrep -m1 '^version' vendor\u002Faube\u002FCargo.toml            # e.g. 1.25.1\ngit log --oneline aube-upstream\u002Fmain | grep 'release v1.25.1'\ngit diff --name-only \u003Cbase-sha>^{tree} origin\u002Fmain:vendor\u002Faube | wc -l   # should be ~nub delta size\n```\n\nAlready done? `git merge-base --is-ancestor aube-upstream\u002Fmain \u003Cvenue>` → nothing to do.\n\n### 2. Build the ephemeral venue and merge\n\n```sh\ngit config rerere.enabled true       # BEFORE resolving — resolve each conflict once, ever\nVENUE=$(git commit-tree origin\u002Fmain:vendor\u002Faube -p \u003Cbase-sha> -m \"venue: vendored aube @ \u003Cbase-tag>\")\ngit merge-base $VENUE aube-upstream\u002Fmain    # MUST print \u003Cbase-sha>\n\ngit worktree add -b _aube_venue \u002Ftmp\u002Faube-venue \"$VENUE\"\ncd \u002Ftmp\u002Faube-venue                           # this worktree's ROOT is aube's tree\ngit merge aube-upstream\u002Fmain --no-ff --no-commit\n\ngit diff --name-only --diff-filter=U > \u002Ftmp\u002Fconflicts.txt\nwhile read -r f; do printf \"%3s %s\\n\" \"$(grep -c '^\u003C\u003C\u003C\u003C\u003C\u003C\u003C' \"$f\")\" \"$f\"; done \u003C \u002Ftmp\u002Fconflicts.txt | sort -rn\n```\n\n**Merge, never rebase** — a rebase re-surfaces the same conflict once per nub-delta commit.\n\n### 3. Resolve list 1, in one shot, in parallel\n\nPartition conflicted files by crate\u002Farea and dispatch one Opus agent per partition — they edit disjoint files in one working tree, which is safe. A workable split:\n\n- `crates\u002Faube\u002Fsrc\u002Fcommands\u002F**` (install, add, dlx, script settings)\n- `crates\u002Faube-lockfile\u002F**` (pnpm\u002Fnpm\u002Fyarn readers + writers)\n- `crates\u002Faube-linker\u002F**`, `aube-scripts`, `aube-util`, `aube-registry`\n\nEvery dispatch prompt must carry the **doctrine below verbatim** (agents inherit nothing) and must say: *do not run `cargo check` — siblings are mid-edit and the tree will not compile; the orchestrator owns the build gate*, and *do not run mutating git commands*.\n\n### 4. Resolve list 2 (the compiler), iterating to clean\n\n```sh\ncd \u002Ftmp\u002Faube-venue && git add -A\nexport CARGO_TARGET_DIR=~\u002F.cache\u002Fnub\u002Faube-venue-target\ncargo check --workspace --all-targets --message-format short   # iterate until exit 0\ncargo clippy --workspace --all-targets --all-features -- -D warnings\nREAL_HOME=\"$HOME\"; mkdir -p \u002Ftmp\u002Fclean-aube-home\nenv HOME=\u002Ftmp\u002Fclean-aube-home RUSTUP_HOME=\"$REAL_HOME\u002F.rustup\" CARGO_HOME=\"$REAL_HOME\u002F.cargo\" \\\n  cargo test --workspace                # registry\u002Fconfig tests read ~\u002F.npmrc\n```\n\n- **`--workspace` with NO `--lib` — that is what CI runs** (`aube-parity.yml`, `working-directory: vendor\u002Faube`). `--lib` skips `crates\u002F*\u002Ftests\u002F**` entirely, including the fork-discipline integration tests that pin default-preservation — exactly what a bump is most likely to break.\n- **Run aube's suite from inside `vendor\u002Faube` (or the venue), never via `--manifest-path` from the nub root.** Cargo reads `.cargo\u002Fconfig.toml` from the invocation directory, and aube's sets `RUST_TEST_THREADS = \"1\"` because `aube-util`'s `concurrency` and `http::ticket_cache` tests mutate process env. From the nub root that is silently dropped and those tests flake, which reads exactly like a regression your merge caused.\n- For each error ask: **is this symbol nub delta or upstream?** Then apply the doctrine. Never paper over with `.unwrap()`\u002F`.expect()` or by deleting a capability.\n- **Check exit codes, not piped output** — `cargo check … | tail` reports `tail`'s status.\n\n### 5. Bring the result into `vendor\u002Faube`\n\n```sh\ncd \u002Ftmp\u002Faube-venue && git commit                       # keep the merge commit for reference\nrsync -a --delete --exclude '.git\u002F' \u002Ftmp\u002Faube-venue\u002F \u003Cworktree>\u002Fvendor\u002Faube\u002F\ndiff -rq \u002Ftmp\u002Faube-venue \u003Cworktree>\u002Fvendor\u002Faube --exclude .git    # MUST be identical\n```\n\nUpdate `vendor\u002Faube\u002FUPSTREAM` to the new upstream commit + tag **in the same commit**.\n\nCheck open PRs touching `vendor\u002Faube\u002F**` first (`gh pr list --json number,title,files`). Where they overlap the upstream delta the in-tree version wins and whoever merges second resolves — say so in the PR body.\n\n### 6. nub-side gates (do not skip — see the feature-gating section)\n\n```sh\ncd \u003Cworktree>\nscripts\u002Frust-build.sh check -p nub-cli --all-targets\nmkdir -p runtime\u002Faddons && printf 'placeholder-addon' > runtime\u002Faddons\u002Fnub-native.node  # clippy ONLY\n# `--all-features` also requires the vendored runtime node_modules. A lint ships nothing, so\n# grant the opt-out (as CI's clippy job does) instead of vendoring them — see `rust-build`.\nNUB_ALLOW_INCOMPLETE_RUNTIME=1 scripts\u002Frust-build.sh clippy --all-targets --all-features -- -D warnings\ncargo fmt --check\nrm -f runtime\u002Faddons\u002Fnub-native.node && make addon-fast    # REQUIRED before any test run\n```\n\nThen open an ordinary nub PR with the `vendor\u002Faube\u002F**` diff: summarize behavior-affecting upstream changes, and flag anything touching a default or security posture for maintainer sign-off.\n\n### 7. Tear down\n\n```sh\ngit worktree remove \u002Ftmp\u002Faube-venue --force && git branch -D _aube_venue\n```\n\n---\n\n## Conflict doctrine (paste into every resolver dispatch)\n\nPriority order. `HEAD`\u002Fours = nub's vendored aube; `aube-upstream\u002Fmain` = jdx\u002Faube.\n\n1. **UNION FIRST.** Most conflicts are add\u002Fadd at a shared anchor — one side's block is empty, or the blocks are unrelated additions (new match arms, `pub mod` lines, tests, use-list entries). Keep **both**. A blind \"ours wins\" here silently deletes upstream features — the #1 failure mode.\n2. **OURS WINS on genuine semantic conflict in code nub owns** (inventory below).\n3. **UPSTREAM WINS in code nub does not own** — upstream bugfixes, new commands, tests for upstream features, refactors with no nub delta in them.\n4. **CONVERGENCE** (both sides built the same feature differently): keep **ours** as the base, then graft any capability upstream has that ours lacks. Name every graft in the report.\n5. **NEVER drop an upstream cancellation\u002Fsafety call** (e.g. `control::check_cancelled()?`) because it landed in a region nub restructured — re-site it at the equivalent point in nub's structure.\n6. Comments stay **sparse and dense** — design, invariant, provenance only. Do not narrate.\n7. Anything turning on a **default \u002F security posture \u002F product behavior**: resolve ours-preserving and **flag it** for maintainer sign-off.\n\n**A graft that breaks a test is a wrong graft.** Let the tests arbitrate; don't defend a graft.\n\n---\n\n## The nub delta that must survive\n\nGrep after every bump — if one vanished, a resolution was wrong:\n\n```sh\ngrep -rn \"workspace_markers\\|lockfile_basename\\|virtual_store_subdir\\|branded_env_alias_enabled\\|read_branded_pnpm_config\\|env_prefix\\|cache_namespace\\|engine_context\\|env_overlay\\|path_prepends\\|runtime_node\\|cold_path\" vendor\u002Faube\u002Fcrates\n```\n\n- **Embedder profile plumbing** — `env_prefix`, `cache_namespace`, `lockfile_basename`, `workspace_markers`, `virtual_store_subdir`, `read_branded_pnpm_config` gating. Holds the brand + config boundary. Largely upstreamed, so it usually converges. Profile type is `Embedder` (`aube-util\u002Fsrc\u002Fidentity.rs`), reached via `aube_util::embedder()`. `virtual_store_subdir` earns its grep slot: upstream call sites hardcoding `aube_store::VIRTUAL_STORE_SUBDIR` (`\"virtual-store\"`) over nub's profile-named leaf auto-merge with no markers. `branded_env_alias_enabled` (`aube-util\u002Fsrc\u002Fenv.rs`) is the single switch gating every `AUBE_*` alias in `settings.toml`.\n- **Linker** — GVS, collective hidden tree as the sole phantom mechanism, per-package force-materialization (`diskMaterializePackages`), workspace-spanning hoisted planning, memoized clonedir probes, whole-dir `clonefile` on macOS, direct-exec of native bins.\n- **Install** — concurrent OSV gating and trust-policy validation via `JoinSet` overlapping the download tail, the `defaultTrust` floor, the nub TTY progress line (`files_linked`).\n- **Lockfile** — `nub.lock` naming via the profile, pnpm-10 `{ hash, path }` patch shape, patch-group range resolution, pnpm-11 `namedRegistries`, git classification in the yarn-classic reader. Patches declared against a package's registry name also apply to an npm-aliased install (`PatchGroups::resolve_package`), and an unused patch key fails the install unless `allowUnusedPatches` is set — both pnpm-parity fixes upstream lacks.\n- **Build approval** — `collect_ignored` surfaces source-backed (`file:`) deps from the install-recorded unreviewed set, and `approve-builds` writes their **source** approval key rather than a bare name. Stock aube drops them, so a dep it warns about cannot be approved. Changes standalone-aube behavior, so expect fork delta rather than convergence.\n- **Registry** — `registry_url_for` returns an owned `String` (a `namedRegistries` route lookup borrows through a lock guard), mTLS\u002F`npmAlwaysAuth`, and the cached system DNS resolver (`aube-util\u002Fsrc\u002Fhttp\u002Fdns.rs`) installed on every registry client, which replaced upstream's Hickory feature.\n- **`cold_path()` hints + the 1.95 MSRV** — `core::hint::cold_path()` on the rare arms of the hot install loops (`aube-linker\u002Fmaterialize.rs` link fallbacks, `aube-resolver\u002Fsemver_util.rs` cache misses, `aube-lockfile\u002Fpnpm\u002Fsubset.rs` parser bails, `aube-store\u002Ftarball.rs` validation rejects), plus `rust-version = \"1.95\"` in `vendor\u002Faube\u002FCargo.toml`. Upstream holds aube at 1.91 for mise's packaging; nub does not. Standing fork delta — the Cargo.toml `rust-version` conflicts every bump; **resolve OURS every time**. `crates\u002Fnub-cli\u002FCargo.toml` also sets 1.95 (workspace floor stays 1.93); the CI MSRV `Check` job runs the root leg on 1.95.0 and the aube-free nub-phantom leg on 1.93.0.\n- **Runtime \u002F lifecycle-script env** — the embedder runtime seam. `crates\u002Faube-util\u002Fsrc\u002Fengine_context.rs` is a nub-only module (`EngineContext` = process-global `OnceLock\u003CRwLock\u003C..>>`); its `runtime_node_dir` \u002F `runtime_node_bin` \u002F `env_overlay` \u002F `path_prepends` \u002F `lifecycle_user_agent_product` fields drive the augmentation. The `resolve_node_bin` \u002F `resolve_path_entry` ladders are grafted into `runtime::node_program` \u002F `path_entries` \u002F `apply_child_env`; `env_overlay` + `path_prepends` ride on `ScriptSettings`, applied last \u002F ahead of PATH via `compose_overlay_path`. Default-empty everywhere, so standalone aube is byte-identical and this delta converges silently — only the grep catches it going missing. Upstream's `seed_embedder_node` \u002F `embedder_node_bin_dir` seam overlaps semantically; expect re-collision.\n\n---\n\n## nub-side integration breaks (upstream feature-gating)\n\n**Check every bump.** Upstream keeps making things optional so embedders can drop them; nub depends with `default-features = false` and silently loses them. Diff the feature tables:\n\n```sh\ngit show aube-upstream\u002Fmain:crates\u002Faube\u002FCargo.toml | sed -n '\u002F\\[features\\]\u002F,\u002F^\\[\u002Fp'\n```\n\nLive requirements in `crates\u002Fnub-cli\u002FCargo.toml`:\n\n- `aube` → `features = [\"rustls\", \"publish\"]`. `publish` gates `commands::publish`, which `pm_engine\u002Fpublish_family.rs` calls directly; `rustls` is the crate's only TLS backend. Without both, nub-cli does not compile.\n- No `hickory-dns` anywhere. The fork deleted the feature from `aube` and `aube-registry` (#942: Hickory reads only the global nameserver list, so VPN-scoped and split DNS fail); reqwest's feature would switch every client in the final binary to it. If a bump brings the feature back, drop it again and keep the registry clients on `aube_util::http::dns::shared()`. `scripts\u002Fcheck-dns-features.sh` fails CI if reqwest's `hickory-dns` reaches the graph.\n\nAlso check the brand boundary on the incoming delta — new `AUBE_*` vars must read through `aube_util::env::embedder_env()`, and no new *unconditional* pnpm-named file read may appear:\n\n```sh\ngit diff \u003Cbase>^{tree} aube-upstream\u002Fmain^{tree} -- 'crates\u002F*' | grep '^+' | grep -oE '\"AUBE_[A-Z0-9_]+\"' | sort -u\n```\n\n---\n\n## Environment gotchas\n\n- **`nub-cli` has no lib target** — binary crate. `--lib` errors; use `--bins`.\n- **`make addon-fast` is required before any nub test run** in a fresh worktree. Without the real N-API addon the TS transpile path fails with `Cannot read properties of null (reading 'transformCached')`. CI's placeholder-addon trick is clippy-only — never leave it in place for tests.\n- **`pm_two_mode` takes ~41 minutes alone**, so `cargo test --workspace` will not finish in any harness window. Run sync-relevant binaries in bounded batches; let CI run the whole thing.\n- **`nohup setsid` does not survive** — the harness reaps the process group when the call returns. Split long runs into separate bounded background calls.\n- **This host runs a build fleet** (load 8–270). A \"test has been running for over 60 seconds\" warning is usually contention, not a hang — confirm with a direct repro before chasing it as a regression.\n- **`cargo fmt --check` fails on ~18 files inside `vendor\u002Faube`** with current rustfmt. Verify the set is *identical* pre- and post-merge before worrying; nub's root workspace excludes `vendor\u002Faube`.\n\n---\n\n## Keeping future bumps cheap\n\n- **Bump often.** Conflict count scales with delta size: 12 upstream commits produced one conflict; 133 produced 48 hunks.\n- **Keep `vendor\u002Faube\u002FUPSTREAM` accurate.** It is the only stored state the method depends on.\n- **Keep the delta thin by upstreaming.** Pluggable\u002Fadditive changes that are no-ops for standalone aube converge on the next bump and leave the fork delta entirely. **Never upstream, or even propose or offer upstreaming, without the maintainer's explicit in-the-moment instruction** (AGENTS.md hard rule). Filing an upstream *issue* is smaller than offering a PR, but still ask.\n- **Watch for upstream superseding fork delta.** When upstream grows an official version of something we forked, that is a chance to delete delta — surface it rather than migrating unilaterally.\n\n## Upstreaming mechanics\n\n`nubjs\u002Faube` the repo is the fork you push branches from to open cross-fork PRs to `jdx\u002Faube` (`gh pr create --repo jdx\u002Faube --base main --head nubjs:\u003Cbranch>`); those branches are cut from `upstream\u002Fmain`. Extract commits with `git subtree split --prefix=vendor\u002Faube` or `git format-patch --relative=vendor\u002Faube` — subject to the never-upstream-without-instruction rule above. The `nub-fork` branch is historical record only.\n","# Bumping vendored aube to a new upstream\n\n## Mental model\n\n`vendor\u002Faube\u002F**` is plain tracked files in nub's history — no submodule, no pin. An aube change is an ordinary nub PR touching `vendor\u002Faube\u002F**`. Everything lives in the nub repo; you do not need a clone of `nubjs\u002Faube` and you do not touch the `nub-fork` branch.\n\n| Thing | Where |\n| --- | --- |\n| Source of truth | `vendor\u002Faube\u002F**` on nub `main` |\n| Upstream | `jdx\u002Faube`, as the `aube-upstream` remote |\n| The base we're on | `vendor\u002Faube\u002FUPSTREAM` (commit + tag) |\n| Merge venue | built on demand, thrown away |\n\n**The venue is derived, not stored.** A 3-way merge needs a commit whose tree is the vendored state and whose ancestry contains the upstream base — both already in nub's object store. Deriving it at bump time means it cannot drift, and `rerere`'s cache lives in nub and persists across bumps.\n\n## The core: two machine-generated conflict lists\n\nYou never hand-review the upstream diff.\n\n1. **Textual conflicts** — `git merge` gives every place both sides edited the same lines. One merge, one complete list, resolved once. This is what a merge buys over a rebase.\n2. **Semantic conflicts** — `cargo check --workspace --all-targets` gives every place both sides edited *different* lines in ways that don't compose (upstream adds a required param, nub's caller keeps the old arity; upstream renames a field under a nub-added method). Git merges text, not meaning, so these produce **zero conflict markers and a perfectly clean merge**.\n\n\"All conflicts resolved\" is worthless as a correctness signal — the compiler is the second half of the merge. List 2 is layered: each fix lets the compiler reach further, so iterate to a clean exit.\n\n**The biggest lever is merge-base correctness.** Conflict count is a function of the base, not of how far upstream moved: a stale base re-presents changes you already have as conflicts (once, 72 files \u002F 205 hunks instead of 23 \u002F 48). `vendor\u002Faube\u002FUPSTREAM` exists so this is a fact you read — keep it accurate.\n\n## Recipe\n\nWork in a nub worktree off latest `origin\u002Fmain` (see the `worktree` skill). Never touch the shared tree.\n\n**Mechanics are a script, not shell improvisation.** `scripts\u002Faube-bump.ts` does the deterministic parts: `plan` (base\u002Fdelta sanity), `venue [--reset]` (build the venue + merge + conflict table), `gate` (check\u002Fclippy verdicts), `land` (rsync + UPSTREAM marker + identical-tree check). Run its subcommands instead of retyping the shell. Guarded by `scripts\u002Faube-bump.test.mts`.\n\n**Never archive-overwrite the vendor tree.** `git archive | tar -x -C vendor\u002Faube` throws away the fork delta and turns the bump into N hand-rebuilt features. The venue 3-way merge is the process; the delta survives unless both sides edited the same lines.\n\n**Never iterate the compiler loop in your own context.** After the venue's textual conflicts are resolved (partitioned subagents, below), dispatch ONE agent to own the whole gate — `check -> clippy -> test` iterated to green — with the doctrine and stop conditions in its prompt. The orchestrator reads the summary, not the errors. Iterating error-by-error in the orchestrator's context burned a full session's budget on one bump.\n\n### 1. Read the base and fetch upstream\n\n```sh\ncat vendor\u002Faube\u002FUPSTREAM                       # commit + tag this tree derives from\ngit remote add aube-upstream https:\u002F\u002Fgithub.com\u002Fjdx\u002Faube 2>\u002Fdev\u002Fnull\ngit fetch aube-upstream main\ngit log --oneline \u003Cbase-sha>..aube-upstream\u002Fmain | wc -l    # size of the bump\n```\n\nSanity-check the marker before trusting it — the delta should look like *nub delta only*, not half of upstream:\n\n```sh\ngrep -m1 '^version' vendor\u002Faube\u002FCargo.toml            # e.g. 1.25.1\ngit log --oneline aube-upstream\u002Fmain | grep 'release v1.25.1'\ngit diff --name-only \u003Cbase-sha>^{tree} origin\u002Fmain:vendor\u002Faube | wc -l   # should be ~nub delta size\n```\n\nAlready done? `git merge-base --is-ancestor aube-upstream\u002Fmain \u003Cvenue>` → nothing to do.\n\n### 2. Build the ephemeral venue and merge\n\n```sh\ngit config rerere.enabled true       # BEFORE resolving — resolve each conflict once, ever\nVENUE=$(git commit-tree origin\u002Fmain:vendor\u002Faube -p \u003Cbase-sha> -m \"venue: vendored aube @ \u003Cbase-tag>\")\ngit merge-base $VENUE aube-upstream\u002Fmain    # MUST print \u003Cbase-sha>\n\ngit worktree add -b _aube_venue \u002Ftmp\u002Faube-venue \"$VENUE\"\ncd \u002Ftmp\u002Faube-venue                           # this worktree's ROOT is aube's tree\ngit merge aube-upstream\u002Fmain --no-ff --no-commit\n\ngit diff --name-only --diff-filter=U > \u002Ftmp\u002Fconflicts.txt\nwhile read -r f; do printf \"%3s %s\\n\" \"$(grep -c '^\u003C\u003C\u003C\u003C\u003C\u003C\u003C' \"$f\")\" \"$f\"; done \u003C \u002Ftmp\u002Fconflicts.txt | sort -rn\n```\n\n**Merge, never rebase** — a rebase re-surfaces the same conflict once per nub-delta commit.\n\n### 3. Resolve list 1, in one shot, in parallel\n\nPartition conflicted files by crate\u002Farea and dispatch one Opus agent per partition — they edit disjoint files in one working tree, which is safe. A workable split:\n\n- `crates\u002Faube\u002Fsrc\u002Fcommands\u002F**` (install, add, dlx, script settings)\n- `crates\u002Faube-lockfile\u002F**` (pnpm\u002Fnpm\u002Fyarn readers + writers)\n- `crates\u002Faube-linker\u002F**`, `aube-scripts`, `aube-util`, `aube-registry`\n\nEvery dispatch prompt must carry the **doctrine below verbatim** (agents inherit nothing) and must say: *do not run `cargo check` — siblings are mid-edit and the tree will not compile; the orchestrator owns the build gate*, and *do not run mutating git commands*.\n\n### 4. Resolve list 2 (the compiler), iterating to clean\n\n```sh\ncd \u002Ftmp\u002Faube-venue && git add -A\nexport CARGO_TARGET_DIR=~\u002F.cache\u002Fnub\u002Faube-venue-target\ncargo check --workspace --all-targets --message-format short   # iterate until exit 0\ncargo clippy --workspace --all-targets --all-features -- -D warnings\nREAL_HOME=\"$HOME\"; mkdir -p \u002Ftmp\u002Fclean-aube-home\nenv HOME=\u002Ftmp\u002Fclean-aube-home RUSTUP_HOME=\"$REAL_HOME\u002F.rustup\" CARGO_HOME=\"$REAL_HOME\u002F.cargo\" \\\n  cargo test --workspace                # registry\u002Fconfig tests read ~\u002F.npmrc\n```\n\n- **`--workspace` with NO `--lib` — that is what CI runs** (`aube-parity.yml`, `working-directory: vendor\u002Faube`). `--lib` skips `crates\u002F*\u002Ftests\u002F**` entirely, including the fork-discipline integration tests that pin default-preservation — exactly what a bump is most likely to break.\n- **Run aube's suite from inside `vendor\u002Faube` (or the venue), never via `--manifest-path` from the nub root.** Cargo reads `.cargo\u002Fconfig.toml` from the invocation directory, and aube's sets `RUST_TEST_THREADS = \"1\"` because `aube-util`'s `concurrency` and `http::ticket_cache` tests mutate process env. From the nub root that is silently dropped and those tests flake, which reads exactly like a regression your merge caused.\n- For each error ask: **is this symbol nub delta or upstream?** Then apply the doctrine. Never paper over with `.unwrap()`\u002F`.expect()` or by deleting a capability.\n- **Check exit codes, not piped output** — `cargo check … | tail` reports `tail`'s status.\n\n### 5. Bring the result into `vendor\u002Faube`\n\n```sh\ncd \u002Ftmp\u002Faube-venue && git commit                       # keep the merge commit for reference\nrsync -a --delete --exclude '.git\u002F' \u002Ftmp\u002Faube-venue\u002F \u003Cworktree>\u002Fvendor\u002Faube\u002F\ndiff -rq \u002Ftmp\u002Faube-venue \u003Cworktree>\u002Fvendor\u002Faube --exclude .git    # MUST be identical\n```\n\nUpdate `vendor\u002Faube\u002FUPSTREAM` to the new upstream commit + tag **in the same commit**.\n\nCheck open PRs touching `vendor\u002Faube\u002F**` first (`gh pr list --json number,title,files`). Where they overlap the upstream delta the in-tree version wins and whoever merges second resolves — say so in the PR body.\n\n### 6. nub-side gates (do not skip — see the feature-gating section)\n\n```sh\ncd \u003Cworktree>\nscripts\u002Frust-build.sh check -p nub-cli --all-targets\nmkdir -p runtime\u002Faddons && printf 'placeholder-addon' > runtime\u002Faddons\u002Fnub-native.node  # clippy ONLY\n# `--all-features` also requires the vendored runtime node_modules. A lint ships nothing, so\n# grant the opt-out (as CI's clippy job does) instead of vendoring them — see `rust-build`.\nNUB_ALLOW_INCOMPLETE_RUNTIME=1 scripts\u002Frust-build.sh clippy --all-targets --all-features -- -D warnings\ncargo fmt --check\nrm -f runtime\u002Faddons\u002Fnub-native.node && make addon-fast    # REQUIRED before any test run\n```\n\nThen open an ordinary nub PR with the `vendor\u002Faube\u002F**` diff: summarize behavior-affecting upstream changes, and flag anything touching a default or security posture for maintainer sign-off.\n\n### 7. Tear down\n\n```sh\ngit worktree remove \u002Ftmp\u002Faube-venue --force && git branch -D _aube_venue\n```\n\n---\n\n## Conflict doctrine (paste into every resolver dispatch)\n\nPriority order. `HEAD`\u002Fours = nub's vendored aube; `aube-upstream\u002Fmain` = jdx\u002Faube.\n\n1. **UNION FIRST.** Most conflicts are add\u002Fadd at a shared anchor — one side's block is empty, or the blocks are unrelated additions (new match arms, `pub mod` lines, tests, use-list entries). Keep **both**. A blind \"ours wins\" here silently deletes upstream features — the #1 failure mode.\n2. **OURS WINS on genuine semantic conflict in code nub owns** (inventory below).\n3. **UPSTREAM WINS in code nub does not own** — upstream bugfixes, new commands, tests for upstream features, refactors with no nub delta in them.\n4. **CONVERGENCE** (both sides built the same feature differently): keep **ours** as the base, then graft any capability upstream has that ours lacks. Name every graft in the report.\n5. **NEVER drop an upstream cancellation\u002Fsafety call** (e.g. `control::check_cancelled()?`) because it landed in a region nub restructured — re-site it at the equivalent point in nub's structure.\n6. Comments stay **sparse and dense** — design, invariant, provenance only. Do not narrate.\n7. Anything turning on a **default \u002F security posture \u002F product behavior**: resolve ours-preserving and **flag it** for maintainer sign-off.\n\n**A graft that breaks a test is a wrong graft.** Let the tests arbitrate; don't defend a graft.\n\n---\n\n## The nub delta that must survive\n\nGrep after every bump — if one vanished, a resolution was wrong:\n\n```sh\ngrep -rn \"workspace_markers\\|lockfile_basename\\|virtual_store_subdir\\|branded_env_alias_enabled\\|read_branded_pnpm_config\\|env_prefix\\|cache_namespace\\|engine_context\\|env_overlay\\|path_prepends\\|runtime_node\\|cold_path\" vendor\u002Faube\u002Fcrates\n```\n\n- **Embedder profile plumbing** — `env_prefix`, `cache_namespace`, `lockfile_basename`, `workspace_markers`, `virtual_store_subdir`, `read_branded_pnpm_config` gating. Holds the brand + config boundary. Largely upstreamed, so it usually converges. Profile type is `Embedder` (`aube-util\u002Fsrc\u002Fidentity.rs`), reached via `aube_util::embedder()`. `virtual_store_subdir` earns its grep slot: upstream call sites hardcoding `aube_store::VIRTUAL_STORE_SUBDIR` (`\"virtual-store\"`) over nub's profile-named leaf auto-merge with no markers. `branded_env_alias_enabled` (`aube-util\u002Fsrc\u002Fenv.rs`) is the single switch gating every `AUBE_*` alias in `settings.toml`.\n- **Linker** — GVS, collective hidden tree as the sole phantom mechanism, per-package force-materialization (`diskMaterializePackages`), workspace-spanning hoisted planning, memoized clonedir probes, whole-dir `clonefile` on macOS, direct-exec of native bins.\n- **Install** — concurrent OSV gating and trust-policy validation via `JoinSet` overlapping the download tail, the `defaultTrust` floor, the nub TTY progress line (`files_linked`).\n- **Lockfile** — `nub.lock` naming via the profile, pnpm-10 `{ hash, path }` patch shape, patch-group range resolution, pnpm-11 `namedRegistries`, git classification in the yarn-classic reader. Patches declared against a package's registry name also apply to an npm-aliased install (`PatchGroups::resolve_package`), and an unused patch key fails the install unless `allowUnusedPatches` is set — both pnpm-parity fixes upstream lacks.\n- **Build approval** — `collect_ignored` surfaces source-backed (`file:`) deps from the install-recorded unreviewed set, and `approve-builds` writes their **source** approval key rather than a bare name. Stock aube drops them, so a dep it warns about cannot be approved. Changes standalone-aube behavior, so expect fork delta rather than convergence.\n- **Registry** — `registry_url_for` returns an owned `String` (a `namedRegistries` route lookup borrows through a lock guard), mTLS\u002F`npmAlwaysAuth`, and the cached system DNS resolver (`aube-util\u002Fsrc\u002Fhttp\u002Fdns.rs`) installed on every registry client, which replaced upstream's Hickory feature.\n- **`cold_path()` hints + the 1.95 MSRV** — `core::hint::cold_path()` on the rare arms of the hot install loops (`aube-linker\u002Fmaterialize.rs` link fallbacks, `aube-resolver\u002Fsemver_util.rs` cache misses, `aube-lockfile\u002Fpnpm\u002Fsubset.rs` parser bails, `aube-store\u002Ftarball.rs` validation rejects), plus `rust-version = \"1.95\"` in `vendor\u002Faube\u002FCargo.toml`. Upstream holds aube at 1.91 for mise's packaging; nub does not. Standing fork delta — the Cargo.toml `rust-version` conflicts every bump; **resolve OURS every time**. `crates\u002Fnub-cli\u002FCargo.toml` also sets 1.95 (workspace floor stays 1.93); the CI MSRV `Check` job runs the root leg on 1.95.0 and the aube-free nub-phantom leg on 1.93.0.\n- **Runtime \u002F lifecycle-script env** — the embedder runtime seam. `crates\u002Faube-util\u002Fsrc\u002Fengine_context.rs` is a nub-only module (`EngineContext` = process-global `OnceLock\u003CRwLock\u003C..>>`); its `runtime_node_dir` \u002F `runtime_node_bin` \u002F `env_overlay` \u002F `path_prepends` \u002F `lifecycle_user_agent_product` fields drive the augmentation. The `resolve_node_bin` \u002F `resolve_path_entry` ladders are grafted into `runtime::node_program` \u002F `path_entries` \u002F `apply_child_env`; `env_overlay` + `path_prepends` ride on `ScriptSettings`, applied last \u002F ahead of PATH via `compose_overlay_path`. Default-empty everywhere, so standalone aube is byte-identical and this delta converges silently — only the grep catches it going missing. Upstream's `seed_embedder_node` \u002F `embedder_node_bin_dir` seam overlaps semantically; expect re-collision.\n\n---\n\n## nub-side integration breaks (upstream feature-gating)\n\n**Check every bump.** Upstream keeps making things optional so embedders can drop them; nub depends with `default-features = false` and silently loses them. Diff the feature tables:\n\n```sh\ngit show aube-upstream\u002Fmain:crates\u002Faube\u002FCargo.toml | sed -n '\u002F\\[features\\]\u002F,\u002F^\\[\u002Fp'\n```\n\nLive requirements in `crates\u002Fnub-cli\u002FCargo.toml`:\n\n- `aube` → `features = [\"rustls\", \"publish\"]`. `publish` gates `commands::publish`, which `pm_engine\u002Fpublish_family.rs` calls directly; `rustls` is the crate's only TLS backend. Without both, nub-cli does not compile.\n- No `hickory-dns` anywhere. The fork deleted the feature from `aube` and `aube-registry` (#942: Hickory reads only the global nameserver list, so VPN-scoped and split DNS fail); reqwest's feature would switch every client in the final binary to it. If a bump brings the feature back, drop it again and keep the registry clients on `aube_util::http::dns::shared()`. `scripts\u002Fcheck-dns-features.sh` fails CI if reqwest's `hickory-dns` reaches the graph.\n\nAlso check the brand boundary on the incoming delta — new `AUBE_*` vars must read through `aube_util::env::embedder_env()`, and no new *unconditional* pnpm-named file read may appear:\n\n```sh\ngit diff \u003Cbase>^{tree} aube-upstream\u002Fmain^{tree} -- 'crates\u002F*' | grep '^+' | grep -oE '\"AUBE_[A-Z0-9_]+\"' | sort -u\n```\n\n---\n\n## Environment gotchas\n\n- **`nub-cli` has no lib target** — binary crate. `--lib` errors; use `--bins`.\n- **`make addon-fast` is required before any nub test run** in a fresh worktree. Without the real N-API addon the TS transpile path fails with `Cannot read properties of null (reading 'transformCached')`. CI's placeholder-addon trick is clippy-only — never leave it in place for tests.\n- **`pm_two_mode` takes ~41 minutes alone**, so `cargo test --workspace` will not finish in any harness window. Run sync-relevant binaries in bounded batches; let CI run the whole thing.\n- **`nohup setsid` does not survive** — the harness reaps the process group when the call returns. Split long runs into separate bounded background calls.\n- **This host runs a build fleet** (load 8–270). A \"test has been running for over 60 seconds\" warning is usually contention, not a hang — confirm with a direct repro before chasing it as a regression.\n- **`cargo fmt --check` fails on ~18 files inside `vendor\u002Faube`** with current rustfmt. Verify the set is *identical* pre- and post-merge before worrying; nub's root workspace excludes `vendor\u002Faube`.\n\n---\n\n## Keeping future bumps cheap\n\n- **Bump often.** Conflict count scales with delta size: 12 upstream commits produced one conflict; 133 produced 48 hunks.\n- **Keep `vendor\u002Faube\u002FUPSTREAM` accurate.** It is the only stored state the method depends on.\n- **Keep the delta thin by upstreaming.** Pluggable\u002Fadditive changes that are no-ops for standalone aube converge on the next bump and leave the fork delta entirely. **Never upstream, or even propose or offer upstreaming, without the maintainer's explicit in-the-moment instruction** (AGENTS.md hard rule). Filing an upstream *issue* is smaller than offering a PR, but still ask.\n- **Watch for upstream superseding fork delta.** When upstream grows an official version of something we forked, that is a chance to delete delta — surface it rather than migrating unilaterally.\n\n## Upstreaming mechanics\n\n`nubjs\u002Faube` the repo is the fork you push branches from to open cross-fork PRs to `jdx\u002Faube` (`gh pr create --repo jdx\u002Faube --base main --head nubjs:\u003Cbranch>`); those branches are cut from `upstream\u002Fmain`. Extract commits with `git subtree split --prefix=vendor\u002Faube` or `git format-patch --relative=vendor\u002Faube` — subject to the never-upstream-without-instruction rule above. The `nub-fork` branch is historical record only.\n",{"name":5,"description":7},"main","9b734566fd36ceed8379f67a92291bc68af60801",".claude\u002Fskills\u002Faube-bump",71,"https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub","https:\u002F\u002Fnubjs.com","https:\u002F\u002Fgithub.com\u002Fnubjs","The all-in-one Node.js toolkit","2026-11-14 14:11:35",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add nubjs\u002Fnub --skill aube-bump",{"tool":39,"command":40},"bunx","bunx skills add nubjs\u002Fnub --skill aube-bump",{"tool":42,"command":43},"pnpm","pnpm dlx skills add nubjs\u002Fnub --skill aube-bump","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Faube-bump\u002FSKILL.md",true,[],[48,54,60,67,74,81],{"skillNo":49,"name":50,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M758BSH88RVXBG8TPCT427TY","nub","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002Fskills\u002Fnub\u002FSKILL.md",[],[],{"skillNo":55,"name":50,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M758BKPRHXS5MS27WG908PBG","This project uses nub, a single Rust CLI that runs on the project's installed Node and replaces the everyday Node toolchain. ALWAYS prefer nub over node, bun, npm, npx, pnpm, and yarn for: executing JS\u002FTS files, running package.json scripts, the npx-equivalent, installing dependencies, watch mode, and Node version management. Surfaces whenever you would otherwise reach for node\u002Fbun\u002Fnpm\u002Fnpx or a package manager.","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002Fsite\u002Fpublic\u002Fskill.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M758BCR8A21H8P4TQ0YRHTC7","worktree","Create and manage isolated git worktrees for parallel build\u002Ftest\u002Flanding work on the nub repo. Invoke (via the Skill tool) whenever you need a fresh worktree to land a change, when you want to know what `.worktreeinclude` does or how to add an entry, or when cleaning up after a merge. Encodes the one-command setup (`nub scripts\u002Fnew-worktree.ts \u003Cslug>` or `node …`) that bakes in the proven recipe — worktree off origin\u002Fmain (vendor\u002Faube is plain in-tree files now, no submodule init), the shared CARGO_TARGET_DIR (`~\u002F.cache\u002Fnub\u002Fshared-target`) that all worktrees reuse, and applying `.worktreeinclude` — plus the eagerly-pull-the-shared-tree discipline and the safe cleanup path. Pairs with the `dev-loop` build skill.","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fworktree\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M758B9NZ1GQMD1A6B25NK0D9","windows-vm-test","Run ad-hoc Nub tests and debugging probes in the maintainer's existing local Windows 11 ARM64 QEMU\u002FHVF VM when its external disk and runbook are present. Use for interactive win32-arm64 or Windows-on-ARM x64-emulation checks; use ci-adhoc-test for true x64-native behavior or when the local VM is unavailable.","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwindows-vm-test\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M758B2JHMBB6YJTGYSJR65S4","visual-review","Verify UI\u002Flayout\u002Fstyling changes are correct by computing occlusion, clipping, and alignment from the browser's resolved paint order via the chrome-devtools MCP `evaluate_script` tool — instead of eyeballing a flat screenshot. Invoke BEFORE declaring any UI, site, or styling\u002Flayout change correct. Screenshots have no depth buffer, so z-index\u002Focclusion\u002Fclip bugs are exactly where \"just look at it\" fails; the `evaluate_script` routines below turn those fuzzy visual judgments into deterministic measurements — including optical center-of-mass, which measures the glyph ink's true visual center so differently-sized labels can be aligned by more than eye.","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvisual-review\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M758AWPM7CE440NBAYJHD44J","type-declarations","Add, audit, or update @nubjs\u002Ftypes declarations for Nub runtime APIs. Use whenever Nub adds or changes a user-visible global, built-in method, module loader type, or TC39 proposal; when TypeScript or @types\u002Fnode gains an overlapping declaration; and before every release to reconcile runtime changes since the previous tag. Covers conflict-safe global augmentation, compiler-version routing, fixture matrices, and package verification.","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftype-declarations\u002FSKILL.md",[],[]]