chore(ui): past-tense the comments that still named the removed vscode-extension

Claude-Session: https://claude.ai/code/session_01QSeKYm29SiQaonK2q8F7CS
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

ui/packages/core/src/utils/dataset-format.ts

@@ -305,7 +305,7 @@ function formatMeasureDate(v: unknown, format: string | undefined, locale: strin
  * lived in `@object-ui/i18n`, which depends on `i18next`/`react-i18next` and
  * peer-depends on React, while this package is the React-free engine (AGENTS.md
  * §3: "No UI-lib deps. Logic only.") and a runtime dependency of React-FREE
- * consumers — the `object-ui` VS Code extension and `@object-ui/data-objectstack`.
+ * consumers — `@object-ui/data-objectstack`, and then the VS Code extension too.
  *
  * #4576 removed the boundary rather than working around it: `formatDisplayNumber`
  * is pure, so it moved DOWN into this package (`./number-display.ts`) and

ui/packages/core/src/utils/number-display.ts

@@ -32,8 +32,8 @@
  * It used to live in `@object-ui/i18n`, and that home cost the repo a real
  * defect. `@object-ui/core`'s `utils/dataset-format.ts` could not import it —
  * `core` is the React-free engine (AGENTS.md §3: "No UI-lib deps. Logic only.")
- * and is a runtime dependency of React-FREE consumers (the `object-ui` VS Code
- * extension, `@object-ui/data-objectstack`), while `i18n` depends on
+ * and is a runtime dependency of React-FREE consumers (`@object-ui/data-objectstack`,
+ * and then the VS Code extension too), while `i18n` depends on
  * `i18next`/`react-i18next` and peer-depends on React. So `formatMeasure` kept
  * a parallel `Intl` implementation, the two drifted, and a German session read
  * `1.234,5 %` from a list cell beside `1.234,5%` from a dashboard measure

ui/packages/types/src/__tests__/package-exports-manifest.test.ts

@@ -20,10 +20,11 @@
  * `require` condition rather than adding a second build format — is the
  * contract-honest fix; see the PR body for the full premise verification
  * (nothing in-repo `require()`s this package, and the one in-repo CJS-format
- * bundle consumer, `packages/vscode-extension` via `tsup --format cjs` with
- * `noExternal: ['@object-ui/types', ...]`, builds byte-identically with the
- * condition present or absent — it resolves the value imports it re-exports
- * via the `import` condition regardless of its own output format).
+ * bundle consumer of the time, the VS Code extension via `tsup --format cjs`
+ * with `noExternal: ['@object-ui/types', ...]`, built byte-identically with the
+ * condition present or absent — it resolved the value imports it re-exported
+ * via the `import` condition regardless of its own output format; that
+ * package has since left the workspace, objectstack#25910).
  *
  * ## What this test is, and is not
  *

ui/packages/types/src/zod/form.zod.ts

@@ -987,9 +987,9 @@ export const CommandSchema = BaseSchema.extend({
  * the author shipped the bad metadata anyway.
  *
  * This is deliberately NOT an answer to "which validator is canonical"
- * (objectui#5449, objectui#4631): a third hand-rolled implementation lives in
- * `packages/vscode-extension/src/providers/SchemaValidator.ts`, and whether
- * the end state is one canonical validator or a contract the others defer to
+ * (objectui#5449, objectui#4631): a third hand-rolled implementation lived in
+ * the VS Code extension's `SchemaValidator.ts` until objectstack#25910 removed
+ * that package, and whether the end state is one canonical validator or a contract the others defer to
  * is a maintainer architecture call. Closing the authoring-time gap is not,
  * and is all that happens here.
  */

ui/scripts/__tests__/check-doc-component-types.test.ts

@@ -1793,10 +1793,12 @@ describe('the three snippets this gate found on its first run stay fixed', () =>
   // ordinary docs edit.
   const read = (rel: string) => fs.readFileSync(path.join(repoRoot, rel), 'utf8');
 
-  it('`heading` is gone from the two page schemas that taught it', () => {
+  it('`heading` is gone from the page schema that taught it', () => {
     // Nothing registers `heading`. `h1` is registered by `html-elements.tsx`'s
-    // TAGS loop and renders `schema.children`, which is what both snippets want.
-    for (const file of ['content/docs/utilities/runner.mdx', 'content/docs/utilities/vscode-extension.mdx']) {
+    // TAGS loop and renders `schema.children`, which is what the snippet wants.
+    // The second page that taught it, the VS Code extension's, was deleted with
+    // that package (objectstack#25910).
+    for (const file of ['content/docs/utilities/runner.mdx']) {
       const body = read(file);
       expect(body, `${file} still teaches the unregistered \`heading\` type`).not.toContain('"type": "heading"');
       expect(body).toContain('"type": "h1"');

ui/scripts/__tests__/check-published-dist-tooling.test.ts

@@ -441,7 +441,7 @@ describe('discoverPublishedPackages', () => {
   it('drops packages npm never receives, and keeps the ones under apps/', () => {
     const root = makeWorkspace({
       'packages/core': { name: '@object-ui/core' },
-      'packages/vscode-extension': { name: 'object-ui', private: true },
+      'packages/editor-ext': { name: 'ext-x', private: true },
       'apps/console': { name: '@object-ui/console' },
     });
     expect(discoverPublishedPackages(root).map((p: { name: string }) => p.name)).toEqual([
@@ -461,9 +461,10 @@ describe('discoverPublishedPackages', () => {
   });
 
   it('excludes THIS repository’s private fixed-group member by name', () => {
-    // `packages/vscode-extension` is named `object-ui`, is in the fixed group
-    // (changesets versions it) and is `private`. Reading the fixed group alone
-    // would put an unpublishable package in scope.
+    // `object-ui` (the VS Code extension) was in the fixed group and `private`
+    // until objectstack#25910 removed it; the pin keeps the name out of scope
+    // should it return. Reading the fixed group alone would put an
+    // unpublishable package in scope.
     const names = discoverPublishedPackages(repoRoot).map((p: { name: string }) => p.name);
     expect(names).not.toContain('object-ui');
     expect(names).toContain('@object-ui/console');

ui/scripts/__tests__/doc-version-claims.test.ts

@@ -300,7 +300,7 @@ import { labelPath, skillBundleBase, skillsWalk } from '../skill-bundle-root.mjs
  * NOT ONE of the four earned an inventory entry, and that is the half of this change
  * worth carrying forward. They were not a floor this project declares — of the 46
  * workspace manifests, ZERO declare `engines.node` or `engines.pnpm`, the only
- * `engines` block outside the root being `packages/vscode-extension`'s `engines.vscode`
+ * `engines` block outside the root being the VS Code extension's `engines.vscode`
  * — and not one it tests: 26 of the 27 `node-version:` declarations in
  * `.github/workflows` read `'22.x'` and the 27th reads `'22'`, so nothing anywhere runs
  * the Node 20 those bullets named. A number a reader will act on, restating no manifest

ui/scripts/__tests__/package-files-exist.test.ts

@@ -373,8 +373,8 @@ describe('package.json `files` entries exist on disk (objectui#3663)', () => {
  *
  * `!private && license` — the two conditions that together turn "MIT" from a
  * label into an obligation. A private package makes no distribution and owes no
- * text (`object-ui`, the vscode-extension, is exactly that case and is excluded
- * on purpose). A package declaring no license at all is a different defect that
+ * text (`@object-ui/test-support` is exactly that case and is excluded on
+ * purpose). A package declaring no license at all is a different defect that
  * this guard deliberately does not invent a verdict about.
  *
  * The population is DERIVED from the same workspace scan as the guard above, so
@@ -479,7 +479,7 @@ describe('published packages that declare a license ship its text (objectui#3696
         '  cp LICENSE <package-dir>/LICENSE      # all 38 are byte-identical, blob cf2ca285',
         '',
         'If the package should NOT be published, mark it `"private": true` instead — that is the',
-        'other true direction, and it is why `object-ui` (the vscode-extension) is not listed here.',
+        'other true direction, and it is why `@object-ui/test-support` is not listed here.',
         '',
         ...violations,
       ].join('\n'),
@@ -562,8 +562,8 @@ describe('published packages that declare a license ship its text (objectui#3696
     // The `private` limb only means something while some private package would
     // otherwise be reported. Asserting the specimen set is NON-EMPTY first is
     // what keeps this from becoming a test that passes because it examines
-    // nothing — today it is `object-ui` (packages/vscode-extension), which
-    // declares "MIT" and has no LICENSE file.
+    // nothing — today it is `@object-ui/test-support`, which declares "MIT"
+    // and has no LICENSE file.
     const privateOwingIfPublished = packages.filter(
       (p) => p.private && p.license !== undefined && licenseTextFiles(p).length === 0,
     );

ui/scripts/__tests__/quick-reference-commands-4149.test.ts

@@ -384,8 +384,8 @@ describe('the UI workspace guide — the published-package count is not written
   /**
    * The row used to state the count ("39 published packages", later 36, then 35), and
    * this test derived the true number to hold the prose to it. The first hand-written
-   * figure counted directories and missed that `packages/vscode-extension` (published
-   * to the VS Code marketplace, not to npm) is `private: true` — off by one, in the
+   * figure counted directories and missed that the VS Code extension (published to
+   * the VS Code marketplace, not to npm; removed since, objectstack#25910) was `private: true` — off by one, in the
    * direction that overstates. Holding it exact then cost a doc edit on every package
    * retirement, for a number the manifests already answer (`private` in each one). So
    * the row names the published packages without counting them, and this test keeps it

ui/scripts/check-changeset-presence.mjs

@@ -665,9 +665,10 @@ export function readReleaseConfig(root) {
  * produce two different guarded surfaces.
  *
  * A package with NO `files` field publishes its whole directory. That is not read
- * as "everything counts": the one such package here (`packages/vscode-extension`)
- * is `private: true` and reaches no registry, and taking the absent field as a
- * blanket would guard every tsconfig and doc page in it. Absent means clause (c)
+ * as "everything counts": such a package that is `private: true` reaches no
+ * registry (the VS Code extension was the case here until objectstack#25910
+ * removed it), and taking the absent field as a blanket would guard every
+ * tsconfig and doc page in it. Absent means clause (c)
  * matches nothing, and clauses (a) and (b) still apply.
  */
 function publishedEntries(manifest) {