@koobiq/components 20.4.2 → 21.0.1

package/schematics/migrations/icons-replacement/README.md

@@ -11,31 +11,31 @@ This schematic provides migration for new icons naming attribute. It includes:
 Apply for project and log file path and icon name should be replaced
 
 ```shell
-ng g @koobiq/components:icons-replacement --project <your project>
+ng g @koobiq/components:icons-replacement --project "<your project>"
 ```
 
 - with custom icon replacement mapping:
 
 ```shell
-ng g @koobiq/components:icons-replacement --project <your project> --replacement-data-path <path-as-json>
+ng g @koobiq/components:icons-replacement --project "<your project>" --replacement-data-path "<path-as-json>"
 ```
 
 Apply for project and replace icon name.
 
 ```shell
-ng g @koobiq/components:icons-replacement --project <your project>  --fix=true
+ng g @koobiq/components:icons-replacement --project "<your project>" --fix=true
 ```
 
 #### Usage for Nx:
 
 ```shell
-nx g @koobiq/components:icons-replacement --project <your project>
+nx g @koobiq/components:icons-replacement --project "<your project>"
 ```
 
 - with custom icon replacement mapping:
 
 ```shell
-nx g @koobiq/components:icons-replacement --project <your project> --replacement-data-path <path-as-json>
+nx g @koobiq/components:icons-replacement --project "<your project>" --replacement-data-path "<path-as-json>"
 ```
 
 ### Run locally

package/schematics/migrations/icons-replacement/{index.js → index.cjs}

@@ -3,11 +3,12 @@
 Object.defineProperty(exports, '__esModule', { value: true });
 
 var path = require('path');
-var utils_messages = require('../../utils/messages.js');
-var utils_packageConfig = require('../../utils/package-config.js');
-var migrations_iconsReplacement_data = require('./data.js');
+var utils_messages = require('../../utils/messages.cjs');
+var utils_packageConfig = require('../../utils/package-config.cjs');
+var migrations_iconsReplacement_data = require('./data.cjs');
 require('@angular-devkit/schematics');
 require('@schematics/angular/utility');
+require('../../utils/project-files.cjs');
 
 const replaceIcons = (contentToBeUpdated, replacementData) => {
     let res = contentToBeUpdated;

package/schematics/migrations/inline-edit-a11y-and-types/README.md

@@ -0,0 +1,82 @@
+# inline-edit-a11y-and-types
+
+Migration schematic invoked automatically by `ng update @koobiq/components@20`
+(registered for `21.0.0-0`). Reports what the inline-edit review broke, and rewrites the one change
+that has a single mechanical translation: `modeAsReadonly` → `mode`.
+
+## Background
+
+The edit overlay used to render two `<div class="cdk-visually-hidden" aria-hidden="true" tabindex="0">`
+sentinels around its panel to detect a Tab out of the editor. That is an axe `aria-hidden-focus`
+failure and two live tab stops that announce nothing, so the sentinels — and the
+`KbqFocusRegionItem` directive behind them — are gone; the boundary is resolved against the panel's
+own first and last tabbable control.
+
+The widget semantics moved with them. The host carried a `tabindex` and no ARIA at all, so a
+`<kbq-inline-edit>` was an unknown element that happened to be focusable. `role="button"`,
+`aria-expanded`, `aria-disabled` and the accessible name now live on
+`.kbq-inline-edit__view-content`, and on `.kbq-inline-edit__focus-anchor` while the view content is
+interactive — putting them on the host would nest the `kbqInlineEditMenu` button inside a widget role.
+
+`mode` moved in the same pass. It was a `protected signal()` fronted by a public `modeAsReadonly`
+`computed()`, with an explicit `modeChange` output fed by a hand-written `toObservable` subscription.
+All three are one `model()` now, which generates an output of the same name and the same type — so
+`(modeChange)` bindings are untouched — and makes the mode writable: `[(mode)]` opens and closes the
+editor programmatically. The alias had no purpose left and was removed.
+
+| Member                       | Before                       | After                               |
+| ---------------------------- | ---------------------------- | ----------------------------------- |
+| `KbqFocusRegionItem`         | exported directive           | removed                             |
+| `mode`                       | `protected WritableSignal`   | public `ModelSignal`                |
+| `modeAsReadonly`             | public `Signal`              | removed — use `mode`                |
+| `modeChange`                 | explicit `output()`          | generated by the `mode` model       |
+| `setValueHandler`            | `(value: any) => void`       | `(value: unknown) => void`          |
+| `validationTooltip`          | `string \| TemplateRef<any>` | `string \| TemplateRef<unknown>`    |
+| `saved`, `canceled`          | `protected`                  | public                              |
+| `KbqA11yLocaleConfiguration` | 15 keys                      | plus the required `edit`            |
+| host `tabindex` / `role`     | on `<kbq-inline-edit>`       | on `.kbq-inline-edit__view-content` |
+
+## What it rewrites
+
+`.modeAsReadonly` → `.mode`, in `.ts` and `.html`, in files that name the inline edit. The alias was a
+`computed()` wrapper over the mode signal, so the read translates unchanged. Matched as a property
+access: a bare identifier of the same name belongs to the host. Pass `--fix=false` to see what would
+change without writing.
+
+An index read (`edit['modeAsReadonly']`) or a destructuring is reported instead of rewritten.
+
+## What it does _not_ do
+
+Nothing else is rewritten. A removed export has no replacement expression, a narrowed handler parameter
+needs a cast only the host can choose, and a selector that matched the host by `tabindex` or `:focus`
+is a decision about which element it actually meant.
+
+| Pattern                                     | Manual migration                                                           |
+| ------------------------------------------- | -------------------------------------------------------------------------- |
+| `kbqFocusRegionItem` / `KbqFocusRegionItem` | Drop it — the Tab boundary is detected on the panel                        |
+| `[setValueHandler]` handler                 | Widen the parameter to `unknown` and narrow inside                         |
+| `KbqA11yLocaleConfiguration` literal        | Add the `edit` key, or switch to a partial override provider               |
+| `.kbq-inline-edit[tabindex]` / `:focus`     | Target `.kbq-inline-edit__view-content` / `.kbq-inline-edit__focus-anchor` |
+| `edit.modeChange.subscribe(...)`            | `toObservable(edit.mode)` — the output is the model's, not a class member  |
+
+## Notes with no call site to point at
+
+- The view mode is announced as a `button` with `aria-expanded`. Its name comes from the new `edit`
+  a11y locale key, or from an `aria-label` on the component — which is read as an input, so a
+  hand-rolled `aria-label` on the host is no longer just an attribute.
+- `saved` and `canceled` are public, so a `viewChild(KbqInlineEdit)` can subscribe to them.
+- `modeChange` now emits synchronously on the write, rather than one microtask later — the old
+  `toObservable(...).pipe(skip(1))` relay is gone. A test that awaited that gap can drop the wait.
+- `save()` marks the projected controls touched itself and gates on the control's validity rather than
+  on the `ErrorStateMatcher` verdict. Typing no longer flips a pristine `required` field into its error
+  look, and `commit()` on a never-touched invalid control keeps the editor open instead of writing the
+  value through — a workaround directive that reset `touched` on the first input can be deleted.
+- The panel shadow reads `--kbq-inline-edit-panel-shadow`, the token the panel used to declare and then
+  bypass, so setting it now changes the shadow. The private `.kbq-mask`, `.kbq-mask__fade` and
+  `.kbq-mask__container` classes were renamed to their `.kbq-inline-edit__menu-mask*` equivalents.
+
+## Running it manually
+
+```
+ng generate @koobiq/components:inline-edit-a11y-and-types --project my-app
+```

package/schematics/migrations/inline-edit-a11y-and-types/data.cjs

@@ -0,0 +1,117 @@
+'use strict';
+
+/**
+ * Data for the `inline-edit-a11y-and-types` migration.
+ *
+ * The inline-edit review moved the widget semantics off the host and closed the surface that only
+ * existed to serve the overlay:
+ *
+ * - `KbqFocusRegionItem` — removed. It existed to give the edit overlay two `aria-hidden` tab stops,
+ *   which is an `aria-hidden-focus` failure; the Tab boundary is detected on the panel now.
+ * - `setValueHandler` — `(value: any) => void` → `(value: unknown) => void`, and `validationTooltip`
+ *   accepts `TemplateRef<unknown>` instead of `TemplateRef<any>`.
+ * - `KbqA11yLocaleConfiguration` — gained a required `edit` key, the accessible name of the control
+ *   that opens the editor.
+ * - The host is no longer the tab stop: `role`, `tabindex` and the ARIA state live on
+ *   `.kbq-inline-edit__view-content` (or on `.kbq-inline-edit__focus-anchor` when the view content is
+ *   interactive).
+ * - `mode` — a `model()` now, so it is public, writable and two-way bindable. The `modeAsReadonly`
+ *   alias that existed only to expose the hidden `protected mode` is gone, and the explicit
+ *   `modeChange` output is generated by the model under the same name.
+ *
+ * Everything is warn-only except the `modeAsReadonly` → `mode` rename: a removed export has no
+ * replacement expression, a narrowed handler parameter needs a cast the component cannot choose, and a
+ * selector that targeted the host is a decision about which element the host actually meant. The rename
+ * is the one change with a single mechanical translation.
+ */
+/** Import specifier that marks a file as an inline-edit consumer. */
+const INLINE_EDIT_PACKAGE = '@koobiq/components/inline-edit';
+/** Identifier and attribute shapes that mark a consumer without an import. */
+const INLINE_EDIT_TYPE = '\\bKbqInlineEdit\\w*\\b|\\bkbqInlineEdit\\w*\\b|\\bkbq-inline-edit\\b';
+/** Anchor for the locale change, which reaches hosts that never name the inline edit. */
+const A11Y_LOCALE_TYPE = '\\bKbqA11yLocaleConfiguration\\b|\\bkbqA11yLocaleConfigurationProvider\\s*\\(';
+/**
+ * The one auto-fix: `modeAsReadonly` was a `computed()` wrapper whose only job was to expose the
+ * `protected mode` signal for reading, so a read of it translates to a read of `mode` unchanged.
+ * Matched as a property access — a bare identifier of the same name belongs to the host, not to us.
+ */
+const MODE_AS_READONLY_ACCESS = /\.modeAsReadonly\b/g;
+/** What {@link MODE_AS_READONLY_ACCESS} is replaced with. */
+const MODE_AS_READONLY_REPLACEMENT = '.mode';
+/** Cheap pre-check so a file without the member is never scanned. */
+const MODE_AS_READONLY_MEMBER = 'modeAsReadonly';
+const warnPatterns = [
+    {
+        anchor: `${INLINE_EDIT_TYPE}|KbqFocusRegionItem`,
+        pattern: '\\bKbqFocusRegionItem\\b|\\bkbqFocusRegionItem\\b',
+        message: 'KbqFocusRegionItem was removed. It marked the two `aria-hidden="true" tabindex="0"` sentinels ' +
+            'the edit overlay rendered around its panel — an axe `aria-hidden-focus` failure and two dead-end ' +
+            'tab stops. The Tab boundary is resolved on the panel itself now, so the directive has no ' +
+            'replacement: drop the import and the attribute.'
+    },
+    {
+        anchor: INLINE_EDIT_TYPE,
+        pattern: '\\bsetValueHandler\\b',
+        message: 'KbqInlineEdit.setValueHandler takes `(value: unknown) => void` instead of `(value: any) => void`. ' +
+            'A handler typed against the concrete value no longer assigns — widen the parameter to `unknown` ' +
+            'and narrow inside, which is what the component always handed over.'
+    },
+    {
+        anchor: A11Y_LOCALE_TYPE,
+        pattern: A11Y_LOCALE_TYPE,
+        message: 'KbqA11yLocaleConfiguration gained a required `edit` key — the accessible name of the control ' +
+            'that opens an inline edit. A complete configuration object has to supply it; a partial override ' +
+            'through kbqA11yLocaleConfigurationProvider() does not.'
+    },
+    {
+        anchor: INLINE_EDIT_TYPE,
+        pattern: '\\[\\s*[\'"`]modeAsReadonly[\'"`]\\s*\\]|\\{[^{}]*\\bmodeAsReadonly\\b[^{}]*\\}\\s*=',
+        message: 'KbqInlineEdit.modeAsReadonly is `mode` now, but this read is not a property access — an index ' +
+            'signature or a destructuring — so it was left untouched. Rewrite it as `mode` by hand.'
+    },
+    {
+        anchor: INLINE_EDIT_TYPE,
+        pattern: '\\.modeChange\\s*\\.\\s*(?:subscribe|pipe|emit)\\s*\\(',
+        message: '`mode` is a model() now, so `modeChange` is the output it generates rather than a member of the ' +
+            'class. The `(modeChange)` template binding is unaffected; a programmatic subscription has to go ' +
+            'through the signal instead — `toObservable(inlineEdit.mode)` from @angular/core/rxjs-interop.'
+    },
+    {
+        anchor: INLINE_EDIT_TYPE,
+        pattern: '\\.kbq-inline-edit\\b[^\\n]*(?:\\[tabindex|:focus)|kbq-inline-edit[^\\n]*\\[tabindex',
+        message: 'The inline edit is no longer the tab stop: `role`, `tabindex` and the ARIA state moved to ' +
+            '.kbq-inline-edit__view-content, and to .kbq-inline-edit__focus-anchor while the view content is ' +
+            'interactive. A selector matching the host by tabindex or focus has to target those instead — the ' +
+            'focus ring itself still lands on the host through `cdk-keyboard-focused`.'
+    }
+];
+/** Printed once per project, after the per-file reports. */
+const SUMMARY = [
+    '  The view mode is announced as a `button` with `aria-expanded`, named by the new `edit` a11y locale ' +
+        'key or by an `aria-label` on the component. Hand-rolled role or aria-* attributes on ' +
+        '<kbq-inline-edit> are duplicates now, and `aria-label` is read as an input.',
+    '  `mode` is a model() — public, writable and two-way bindable, so `[(mode)]` opens and closes the ' +
+        'editor programmatically. `modeAsReadonly` existed only to expose the hidden signal for reading and ' +
+        'was removed; its call sites are rewritten to `mode`.',
+    '  The `modeChange` output is generated by the model under the same name and carries the same value, so ' +
+        '`(modeChange)` bindings keep working. It emits synchronously on the write now, rather than one ' +
+        'microtask later — a test that awaited the old gap can drop the wait.',
+    '  `saved` and `canceled` are public, so a viewChild(KbqInlineEdit) can subscribe to them. Template ' +
+        'bindings are unaffected.',
+    '  save() marks the projected controls touched itself and gates on the control validity rather than on ' +
+        'the ErrorStateMatcher verdict. Typing no longer flips a pristine required field into its error look, ' +
+        'and commit() on a never-touched invalid control now keeps the editor open instead of writing the ' +
+        'value through — a workaround directive that reset `touched` on first input can be deleted.',
+    '  The panel shadow reads --kbq-inline-edit-panel-shadow, which the panel used to declare and then ' +
+        'bypass, and the private .kbq-mask / .kbq-mask__fade / .kbq-mask__container classes were renamed to ' +
+        'their .kbq-inline-edit__menu-mask* equivalents.'
+];
+
+exports.A11Y_LOCALE_TYPE = A11Y_LOCALE_TYPE;
+exports.INLINE_EDIT_PACKAGE = INLINE_EDIT_PACKAGE;
+exports.INLINE_EDIT_TYPE = INLINE_EDIT_TYPE;
+exports.MODE_AS_READONLY_ACCESS = MODE_AS_READONLY_ACCESS;
+exports.MODE_AS_READONLY_MEMBER = MODE_AS_READONLY_MEMBER;
+exports.MODE_AS_READONLY_REPLACEMENT = MODE_AS_READONLY_REPLACEMENT;
+exports.SUMMARY = SUMMARY;
+exports.warnPatterns = warnPatterns;

package/schematics/migrations/inline-edit-a11y-and-types/index.cjs

@@ -0,0 +1,98 @@
+'use strict';
+
+Object.defineProperty(exports, '__esModule', { value: true });
+
+var utils_messages = require('../../utils/messages.cjs');
+var utils_packageConfig = require('../../utils/package-config.cjs');
+var utils_projectFiles = require('../../utils/project-files.cjs');
+var migrations_inlineEditA11yAndTypes_data = require('./data.cjs');
+require('@angular-devkit/schematics');
+require('@schematics/angular/utility');
+
+const LABEL = '[inline-edit-a11y-and-types]';
+const EXTENSIONS = ['.ts', '.html', '.scss', '.css'];
+/** The rename lives in code and markup only; the `.scss`/`.css` pass stays report-only. */
+const FIXABLE_EXTENSIONS = ['.ts', '.html'];
+// Compiled once: the scope test runs against every file of the project, and the warn patterns against
+// every file that passes it. None carries the `g` flag, so a shared instance holds no `lastIndex`.
+const inlineEditType = new RegExp(migrations_inlineEditA11yAndTypes_data.INLINE_EDIT_TYPE);
+const a11yLocaleType = new RegExp(migrations_inlineEditA11yAndTypes_data.A11Y_LOCALE_TYPE);
+const compiledWarnPatterns = migrations_inlineEditA11yAndTypes_data.warnPatterns.map(({ anchor, pattern, message }) => ({
+    anchor: new RegExp(anchor),
+    pattern: new RegExp(pattern),
+    message
+}));
+/** A file is in scope if it names the inline edit, or if it configures the a11y locale section. */
+function referencesSubject(content) {
+    return content.includes(migrations_inlineEditA11yAndTypes_data.INLINE_EDIT_PACKAGE) || inlineEditType.test(content) || a11yLocaleType.test(content);
+}
+/**
+ * Rewrites `modeAsReadonly` reads to `mode`, and reports the rest of what the inline-edit review broke:
+ * the removed `KbqFocusRegionItem`, the handler and tooltip types narrowed from `any` to `unknown`, the
+ * new required `edit` key of `KbqA11yLocaleConfiguration`, and the tab stop that moved off the host onto
+ * the view content.
+ *
+ * The rename is the only write. `modeAsReadonly` was a `computed()` wrapper over the mode signal, so a
+ * read of it translates to a read of `mode` unchanged — every other change is reported instead: a removed
+ * export has no replacement expression, a narrowed parameter needs a cast only the host can choose, and a
+ * selector that matched the host is a decision about which element it meant. `.scss`/`.css` are visited
+ * as well, because the tab stop moved in the DOM rather than in the API.
+ */
+function inlineEditA11yAndTypes(options) {
+    return async (tree, context) => {
+        const { project } = options;
+        // `ng update` invokes migrations with no options at all, so the schema default never reaches us —
+        // applying the fix is the intended behaviour there.
+        const fix = options.fix ?? true;
+        const projectDefinition = await utils_packageConfig.setupOptions(project, tree);
+        const root = projectDefinition?.root ?? '';
+        const rootDir = root ? tree.getDir(root) : tree.root;
+        let consumers = 0;
+        let reported = 0;
+        /** Collected during the walk and applied after it, so the tree is not mutated while iterating. */
+        const renames = [];
+        utils_projectFiles.visitProjectFiles(rootDir, (filePath, entry) => {
+            if (!EXTENSIONS.some((extension) => filePath.endsWith(extension)))
+                return;
+            const originalContent = entry?.content.toString();
+            if (!originalContent || !referencesSubject(originalContent))
+                return;
+            consumers++;
+            let content = originalContent;
+            if (FIXABLE_EXTENSIONS.some((extension) => filePath.endsWith(extension)) &&
+                originalContent.includes(migrations_inlineEditA11yAndTypes_data.MODE_AS_READONLY_MEMBER)) {
+                content = originalContent.replace(migrations_inlineEditA11yAndTypes_data.MODE_AS_READONLY_ACCESS, migrations_inlineEditA11yAndTypes_data.MODE_AS_READONLY_REPLACEMENT);
+                if (content !== originalContent)
+                    renames.push({ filePath, content });
+            }
+            // Warn against the fixed content, so a rewritten call site does not also produce a
+            // "migrate by hand" note. In dry-run nothing is written, so report against the original.
+            const reportedContent = fix ? content : originalContent;
+            for (const { anchor, pattern, message } of compiledWarnPatterns) {
+                if (!anchor.test(reportedContent) || !pattern.test(reportedContent))
+                    continue;
+                reported++;
+                utils_messages.logMessage(context.logger, [`${LABEL} ${filePath}`, `  ${message}`]);
+            }
+        });
+        for (const { filePath, content } of renames) {
+            if (fix) {
+                tree.overwrite(filePath, content);
+            }
+            else {
+                utils_messages.logMessage(context.logger, [`${LABEL} would update ${filePath} (run with --fix to apply)`]);
+            }
+        }
+        // Nothing here renders an inline edit or touches the a11y locale, so the summary would only be noise.
+        if (consumers === 0)
+            return;
+        utils_messages.logMessage(context.logger, [
+            `${LABEL} processed kbq-inline-edit under "${root || '<workspace root>'}", ` +
+                `${consumers} file(s) reference the component, ${renames.length} file(s) ` +
+                `${fix ? 'updated' : 'would be updated'}, ${reported} call site(s) reported.`,
+            ...migrations_inlineEditA11yAndTypes_data.SUMMARY
+        ]);
+    };
+}
+
+exports.default = inlineEditA11yAndTypes;

package/schematics/migrations/inline-edit-a11y-and-types/schema.json

@@ -0,0 +1,20 @@
+{
+    "$schema": "http://json-schema.org/schema",
+    "$id": "koobiq-components-inline-edit-a11y-and-types",
+    "title": "Koobiq components inline-edit review migration",
+    "type": "object",
+    "properties": {
+        "project": {
+            "type": "string",
+            "description": "Name of the project to inspect. If omitted, the migration runs over the whole tree.",
+            "$default": {
+                "$source": "projectName"
+            }
+        },
+        "fix": {
+            "type": "boolean",
+            "default": true,
+            "description": "When true, applies the modeAsReadonly to mode rename. When false, prints what would change without writing."
+        }
+    }
+}

package/schematics/migrations/input-number-surface/README.md

@@ -0,0 +1,140 @@
+# input-number-surface
+
+Migration schematic invoked automatically by `ng update @koobiq/components@20`
+(registered for `21.0.0-0`). Rewrites reads of the four `KbqNumberInput` members that became signals,
+and reports everything else: the members that disappeared with the `KbqFormFieldControl` surface the
+directive declared and never populated, the validator directives that gained a `Kbq` prefix, and the
+behaviors that changed without a call site to point at.
+
+## `min`, `max`, `step` and `bigStep` are `input()` signals
+
+A read becomes a call. The value is unchanged, so this part is auto-fixed:
+
+```ts
+// before
+const span = numberInput.max - numberInput.min;
+// after
+const span = numberInput.max() - numberInput.min();
+```
+
+The rewrite is scoped, not textual. `min`, `max` and `step` are among the most common property names
+there are, so a bare `\.min\b` match would rewrite a plain object literal's bounds. Only two receivers
+qualify:
+
+- an identifier this file **annotates** as `KbqNumberInput` — a parameter, a field, a local, or a
+  `viewChild(KbqNumberInput)` initializer. There is no cross-package type resolution, so a receiver
+  whose type is only inferred is left alone.
+- a template reference bound through the directive's `exportAs`: `#ref="kbqNumberInput"` or the
+  `kbqNumericalInput` alias. Both external and inline templates.
+
+Template **bindings** are otherwise untouched — `[min]="lower"` and `min="3"` still work.
+
+The one exception is `bigStep`, which had a second spelling: the legacy `big-step` attribute, read once
+at construction and deaf to every later change. Keeping both would mean maintaining the same input
+twice, so the kebab-case one is dropped and renamed here, scoped to the `<input>` tag that carries the
+directive.
+
+A programmatic **write** (`numberInput.min = 0`) is reported, not rewritten: an `input()` is read-only
+and has no `.set()`, so the binding has to take over. The rewrite is idempotent — an already-migrated
+`min()` is left alone, so running it twice is safe.
+
+## `KbqInputPassword` mints its ids in its own namespace
+
+It shared the `kbq-input-` counter with `KbqInput`, so any page holding both controls emitted two
+elements with the same id, and the form field's `<label for>` resolved to whichever came first. A
+password field now renders `id="kbq-input-password-7"` where it used to render `id="kbq-input-7"`.
+
+Reported, not rewritten: a hand-written reference to a generated id is a symptom, and the fix is
+usually to stop depending on the generated value rather than to renumber it.
+
+## The unprefixed validator exports are gone
+
+`MinValidator`, `MaxValidator`, `MIN_VALIDATOR` and `MAX_VALIDATOR` were deprecated aliases of the
+`Kbq`-prefixed names. They are removed, and rewritten here — a pure rename has one mechanical
+translation.
+
+The rewrite is scoped to the names a file imports from `@koobiq/components/input`, because
+`@angular/forms` exports `MinValidator` and `MaxValidator` under exactly those spellings — which is
+why the koobiq ones were renamed in the first place. A file importing the framework's is left alone.
+
+## `valueChange` and `disabledChange` are Subjects
+
+Both were `EventEmitter`. Subscribing is unchanged; a call to `.emit()` becomes `.next()`. Reported
+rather than rewritten: those two names are far too common to match blind.
+
+## Background
+
+`KbqNumberInput` declared `implements KbqFormFieldControl<any>` and then assigned none of it. The
+private `control` field behind `ngControl` had no writer anywhere in the file, so `ngControl` was
+permanently `undefined`, and `id`, `placeholder`, `empty`, `required` and `errorState` were declared
+only to satisfy the interface. Nothing broke, because the `KbqFormFieldControl` provider lives on the
+sibling `KbqInput` — which matches the same host and supplies the real implementation — but the
+members were public, so a consumer reading `numberInputRef.errorState` got `undefined` with no type
+error.
+
+| Member                                                              | Before                     | After              |
+| ------------------------------------------------------------------- | -------------------------- | ------------------ |
+| `ngControl`, `id`, `placeholder`, `empty`, `required`, `errorState` | public, always `undefined` | removed            |
+| `MinValidator`, `MaxValidator`                                      | deprecated aliases         | removed, rewritten |
+| `MIN_VALIDATOR`, `MAX_VALIDATOR`                                    | deprecated aliases         | removed, rewritten |
+
+The unprefixed validator names are the exact names `@angular/forms` exports, so importing both in one
+file shadowed the framework's.
+
+## Two behaviors that changed with no call site
+
+`type="number"` on a `kbqNumberInput` is now reset to `type="text"` with a console warning. A native
+number field runs the value sanitization algorithm on assignment and rejects everything the directive
+renders once a group separator or a comma fraction separator is in it, so the field went blank while
+the model still held the value; it also reports `selectionStart` as `null`, which disabled caret
+preservation entirely.
+
+`HTMLInputElement.prototype.valueAsNumber` is no longer redefined. The constructor used to call
+`Object.defineProperty(Object.getPrototypeOf(this.nativeElement), 'valueAsNumber', …)` — that is the
+prototype, not the element, so constructing one koobiq number input replaced the platform accessor for
+every `<input>` in the application, permanently and with no teardown. A locale-aware numeric read is
+now a member of the directive: `numberInput.valueAsNumber`.
+
+## What it does _not_ rewrite
+
+A member that was always `undefined` has no replacement expression, and the validator rename is safe to
+leave in place until the deprecated aliases are dropped.
+
+| Pattern                                                          | Manual migration                                                   |
+| ---------------------------------------------------------------- | ------------------------------------------------------------------ |
+| `numberInput.errorState` / `.ngControl` / `.empty` / `.required` | Read them off the sibling `KbqInput` or off the `<kbq-form-field>` |
+| `numberInput.min = 0`                                            | Bind `[min]="0"` — an `input()` has no `.set()`                    |
+| `numberInput.valueChange.emit(v)`                                | `numberInput.valueChange.next(v)`                                  |
+| `<input kbqNumberInput type="number">`                           | Drop the attribute                                                 |
+| `inputElement.valueAsNumber`                                     | `numberInput.valueAsNumber`, or read the form control              |
+| `#kbq-input-7` on a password field                               | Stop keying on a generated id, or use `kbq-input-password-7`       |
+
+A receiver whose `KbqNumberInput` type is inferred rather than written down is also out of reach, as
+are the forms no structural match can see — an index read (`refs['input'].min`) and destructuring
+(`const { min } = numberInput`). Nothing about those is reported, so check them by hand.
+
+## Also in the release, with nothing to migrate
+
+- The numeric inputs coerce their value, so a static attribute (`min="3"`) holds the number `3` rather
+  than the string `"3"`. The `ngAcceptInputType_*` declarations that used to carry that are gone: a
+  signal input types what it accepts through its transform's parameter.
+- The validators no longer `parseInt` their bound value, so `[min]="0.5"` validates against `0.5`
+  instead of `0`, and a bound `[min]="0"` reaches the DOM instead of being dropped by a falsy check.
+- Stepping runs in integer space against a decimal scale, so one arrow press on `1.005` with
+  `step="0.001"` renders `1,006` rather than `1,0059999999999998`.
+- `KbqNumberInput` carries spinbutton semantics: `role`, `aria-valuenow`, `aria-valuetext`,
+  `aria-valuemin`, `aria-valuemax` and `inputmode`.
+- `startFormattingFrom` is read from the input as well as from the locale, instead of being declared
+  and ignored.
+
+## Usage
+
+```bash
+ng update @koobiq/components
+```
+
+Or standalone:
+
+```bash
+ng generate @koobiq/components:input-number-surface --project=my-app
+```

package/schematics/migrations/input-number-surface/data.cjs

@@ -0,0 +1,135 @@
+'use strict';
+
+/**
+ * Data for the `input-number-surface` migration.
+ *
+ * The input review stripped the `KbqFormFieldControl` surface `KbqNumberInput` declared and never
+ * populated, and prefixed the two validator directives whose unprefixed names shadow the identically
+ * named exports of `@angular/forms`:
+ *
+ * - `KbqNumberInput` no longer `implements KbqFormFieldControl`. `ngControl`, `errorState`, `id`,
+ *   `placeholder`, `empty` and `required` are gone; every one of them was `undefined` for the whole
+ *   lifetime of the directive, because the backing `control` field was never assigned. The real
+ *   implementation always lived on the sibling `KbqInput`, which is what the form field resolves.
+ * - `MinValidator` / `MaxValidator` / `MIN_VALIDATOR` / `MAX_VALIDATOR` → `KbqMinValidator` /
+ *   `KbqMaxValidator` / `KBQ_MIN_VALIDATOR` / `KBQ_MAX_VALIDATOR`. The old names stay as deprecated
+ *   aliases for one minor, so nothing breaks today.
+ *
+ * It then finished the signal migration: `min`, `max`, `step` and `bigStep` became `input()`, so a read
+ * has to become a call. That part *is* rewritten — scoped to a receiver whose type is provably
+ * `KbqNumberInput`, because `min`/`max`/`step` are far too common to match on the member name alone.
+ *
+ * The rest is warn-only. A removed member that was always `undefined` has no replacement expression,
+ * and the validator rename is safe to leave until the aliases are dropped.
+ */
+/** Import specifier that marks a file as an input consumer. */
+const INPUT_PACKAGE = '@koobiq/components/input';
+/** Identifier and attribute shapes that mark a consumer without an import. */
+const INPUT_TYPE = '\\bKbqNumberInput\\b|\\bkbqNumberInput\\b';
+/** The password directive, which owns the id-namespace change. Anchors its own warning. */
+const PASSWORD_TYPE = '\\bKbqInputPassword\\b|\\bkbqInputPassword\\b';
+/** TypeScript type annotation that marks a receiver as a number input. */
+const NUMBER_INPUT_TYPE = 'KbqNumberInput';
+/** `exportAs` names a template reference variable can bind the directive under. */
+const NUMBER_INPUT_EXPORT_AS = ['kbqNumberInput', 'kbqNumericalInput'];
+/**
+ * `KbqNumberInput` members that became `input()` signals. The value is unchanged — only the call
+ * syntax — so a read is rewritten to a call. Every one of these is read-only: a programmatic write
+ * has no `.set()` and is warned about instead.
+ */
+const SIGNAL_MEMBERS = ['min', 'max', 'step', 'bigStep'];
+/**
+ * The `KbqFormFieldControl` member-access pattern, handled separately from {@link warnPatterns}: `KbqInput`
+ * — the sibling directive that also matches `input[kbqNumberInput]` — still exposes every one of these
+ * members, so a bare text match would also flag a file that correctly reads them off a `KbqInput`-typed
+ * reference. `index.ts` resolves the receiver of each match against the file's AST before reporting it.
+ */
+const FORM_FIELD_CONTROL_MEMBER_PATTERN = {
+    anchor: INPUT_TYPE,
+    pattern: '\\b([A-Za-z_$][\\w$]*)\\s*\\.\\s*(?:ngControl|errorState|placeholder|empty|required)\\b',
+    message: 'KbqNumberInput no longer implements KbqFormFieldControl: ngControl, errorState, id, placeholder, ' +
+        'empty and required were removed. None of them was ever assigned — the private `control` field ' +
+        'behind ngControl had no writer — so every read returned undefined. Read them off the sibling ' +
+        'KbqInput, which owns the KbqFormFieldControl provider on the same element, or off the form ' +
+        'field itself.'
+};
+/**
+ * Removed exports and the prefixed names that replace them. A pure rename with one mechanical
+ * translation each, so these are rewritten rather than reported.
+ *
+ * The unprefixed names were the exact names `@angular/forms` exports, so importing both in one file
+ * shadowed the framework validator. They were deprecated aliases; this release drops them.
+ *
+ * Only rewritten in a file that imports `@koobiq/components/input` — without that anchor, a project
+ * importing `MinValidator` from `@angular/forms` would be rewritten to a koobiq name it never imported.
+ */
+const RENAMED_EXPORTS = [
+    ['MinValidator', 'KbqMinValidator'],
+    ['MaxValidator', 'KbqMaxValidator'],
+    ['MIN_VALIDATOR', 'KBQ_MIN_VALIDATOR'],
+    ['MAX_VALIDATOR', 'KBQ_MAX_VALIDATOR']
+];
+const warnPatterns = [
+    {
+        anchor: INPUT_TYPE,
+        // Both attribute orders, and only within the same `<input>` tag as `kbqNumberInput` — a bare
+        // `type\s*=\s*"number"` anywhere in the file also matches an unrelated native input.
+        pattern: '<input\\b[^>]*\\bkbqNumberInput\\b[^>]*\\btype\\s*=\\s*[\'"]number[\'"]|' +
+            '<input\\b[^>]*\\btype\\s*=\\s*[\'"]number[\'"][^>]*\\bkbqNumberInput\\b',
+        message: 'type="number" on a kbqNumberInput is reset to type="text" with a console warning. A native ' +
+            'number field runs the value sanitization algorithm on assignment and drops every value the ' +
+            'directive formats — anything with a fraction, and anything over 999 while withThousandSeparator ' +
+            'is on — so the field went blank while the model still held the value. Drop the attribute.'
+    },
+    {
+        anchor: INPUT_TYPE,
+        pattern: '\\b(?:valueChange|disabledChange)\\s*\\.\\s*emit\\b',
+        message: 'KbqNumberInput.valueChange and .disabledChange are RxJS Subjects rather than EventEmitters. ' +
+            'Subscribing is unchanged; a call to .emit() becomes .next(). These names are too common to ' +
+            'rewrite blind — check whether the receiver is the number input before renaming.'
+    },
+    {
+        // Anchored on the password directive, not on INPUT_TYPE: the ids belong to KbqInputPassword.
+        anchor: PASSWORD_TYPE,
+        // A hand-written reference to a generated id, in a selector, a test id or an aria-* attribute.
+        pattern: '[\'"#\\[]\\s*kbq-input-\\d|kbq-input-\\d+["\'\\]]|\\bkbq-input-\\d',
+        message: 'KbqInputPassword mints its ids in its own kbq-input-password- namespace now, so a password ' +
+            'field that used to render id="kbq-input-7" renders id="kbq-input-password-7". It shared the ' +
+            'kbq-input- counter with KbqInput before, which produced two elements with the same id on any ' +
+            "page holding both controls, and the form field's <label for> then resolved to the wrong one. " +
+            'Anything keyed on the generated id — a CSS selector, a test locator, a hand-written ' +
+            'aria-labelledby — has to be updated, or better, stop depending on a generated value.'
+    },
+    {
+        anchor: INPUT_TYPE,
+        pattern: '\\bvalueAsNumber\\b',
+        message: 'KbqNumberInput no longer redefines HTMLInputElement.prototype.valueAsNumber. The patch replaced ' +
+            'the platform accessor for every <input> in the application, returned null where the DOM ' +
+            'specification requires NaN, and read a date field as parseFloat of its date string. A ' +
+            'locale-aware numeric read is now a member of the directive: numberInput.valueAsNumber.'
+    }
+];
+/** Printed once per project, after the per-file reports. */
+const SUMMARY = [
+    '  min, max, step and bigStep are input() signals that coerce their value, so a static attribute ' +
+        '(min="3") holds the number 3 rather than the string "3". Reads on a KbqNumberInput-typed ' +
+        'receiver were rewritten to calls; template bindings ([min], big-step="2") are unchanged.',
+    '  MinValidator/MaxValidator no longer parseInt their bound value, so a fractional [min]="0.5" ' +
+        'validates against 0.5 instead of 0, and a bound [min]="0" reaches the DOM instead of being ' +
+        'dropped by a falsy check.',
+    '  Stepping is done in integer space against a decimal scale, so one arrow press on 1.005 with ' +
+        'step="0.001" renders 1,006 rather than 1,0059999999999998.',
+    '  KbqNumberInput carries spinbutton semantics — role, aria-valuenow, aria-valuetext, aria-valuemin, ' +
+        'aria-valuemax and inputmode.'
+];
+
+exports.FORM_FIELD_CONTROL_MEMBER_PATTERN = FORM_FIELD_CONTROL_MEMBER_PATTERN;
+exports.INPUT_PACKAGE = INPUT_PACKAGE;
+exports.INPUT_TYPE = INPUT_TYPE;
+exports.NUMBER_INPUT_EXPORT_AS = NUMBER_INPUT_EXPORT_AS;
+exports.NUMBER_INPUT_TYPE = NUMBER_INPUT_TYPE;
+exports.PASSWORD_TYPE = PASSWORD_TYPE;
+exports.RENAMED_EXPORTS = RENAMED_EXPORTS;
+exports.SIGNAL_MEMBERS = SIGNAL_MEMBERS;
+exports.SUMMARY = SUMMARY;
+exports.warnPatterns = warnPatterns;