@starci/hfs 1.0.0

package/runtime/knowledge/hfs/canon-pins.yaml

@@ -0,0 +1,212 @@
+schema: starci/canon-pins@1
+purpose: >-
+  The exact version of every dependency a StarCi product repository pins. One version per dependency for the whole
+  family. Raising a version is a change to this file first (with the package bump when it is a @starci package),
+  then the repositories' own upgrade lane (each sets the exact version and reinstalls; nothing else installs a @starci package). Read on 2026-09-29 from the packages under
+  .claude/packages and from the installed node_modules of nivo-backend, nivo-fe, starci-next, starci-next-fe,
+  mia-mia-backend and miamia-fe; where they disagreed the newest version installed in more than one repository
+  won, and the runtime's own version won for @starci packages.
+pins:
+  # --- @starci packages. Every @starci package is a PUBLISHED npm package (install: registry): a product repository
+  # installs the exact pinned version from the npm registry in the root and every workspace package.json, never `file:`.
+  '@starci/grammar':
+    version: 0.7.1
+    group: starci
+    install: registry
+    side: fe
+    source: packages/grammar/package.json
+    why: nivo-fe pins 0.4.11 and 0.5.0 in one workspace, starci-next-fe 0.5.1, miamia-fe 0.5.0; the runtime source is 0.7.1.
+  '@starci/eslint-canon-be':
+    version: 1.7.0
+    group: starci
+    install: registry
+    side: be
+    source: packages/eslint/be/package.json
+    why: 'back-end repositories carry 1.2.1 and 1.2.2 while the runtime source is 1.7.0: the round-3 catch-up landed the nest code-pattern profile''s version and content digest, left unbumped when R78-R82 landed, plus the inbox-dedupe-required shape-detection fix; 1.7.0 adds named-entity-manager-only (R83).'
+  '@starci/eslint-canon-fe':
+    version: 5.1.2
+    group: starci
+    install: registry
+    side: fe
+    source: packages/eslint/fe/package.json
+    why: 'every front-end repository carries 3.0.2 or 4.0.0 while the runtime source is 5.1.0: the vn-ok pragma is gone, starciFeConfig enables every rule and the React Hooks rules at error, and 5.1.0 adds the list, effect, formatter, navigation, metadata and type-safety rules that repositories used to carry in their own config.'
+  '@starci/stylelint-canon':
+    version: 1.1.0
+    group: starci
+    install: registry
+    side: fe
+    source: packages/stylelint/package.json
+    why: no front-end repository lints its CSS yet (nivo-fe apps/landing carries 4.3k lines of raw CSS); the runtime source is the first release.
+  '@starci/tsconfig':
+    version: 1.0.0
+    group: starci
+    install: registry
+    side: both
+    source: packages/tsconfig/package.json
+  '@starci/prettier-config':
+    version: 1.0.0
+    group: starci
+    install: registry
+    side: both
+    source: packages/prettier-config/package.json
+  '@starci/jest-preset':
+    version: 1.1.0
+    group: starci
+    install: registry
+    side: be
+    source: packages/jest-preset/package.json
+    why: gains the FakeClock test double (./clock) for the platform/clock Clock port, used by the R79 no-ambient-clock migration.
+  '@starci/vitest-preset':
+    version: 1.0.0
+    group: starci
+    install: registry
+    side: fe
+    source: packages/vitest-preset/package.json
+  '@starci/playwright-preset':
+    version: 1.0.0
+    group: starci
+    install: registry
+    side: fe
+    source: packages/playwright-preset/package.json
+  '@starci/hfs':
+    version: 1.0.0
+    group: starci
+    install: registry
+    side: both
+    source: packages/hfs/package.json
+    why: the hfs command line (check, init, explain) of every product repository, installed from the npm registry.
+  # --- tooling
+  typescript:
+    version: 5.9.3
+    group: tooling
+    side: both
+    why: all six repositories resolve 5.9.3 already; the declared ranges (^5, ^5.7.3) become exact.
+  prettier:
+    version: 3.9.6
+    group: tooling
+    side: both
+    why: only nivo-backend has it installed (3.9.6); the other five adopt it with the formatter change.
+  stylelint:
+    version: 17.15.0
+    group: tooling
+    side: fe
+    why: no repository has it installed; 17.15.0 is the current release, and the canon plugin needs the ESM-only 17 line.
+  postcss-value-parser:
+    version: 4.2.0
+    group: tooling
+    side: fe
+    why: peer of @starci/stylelint-canon (it parses declaration values); 4.2.0 is what stylelint 17.15.0 itself resolves.
+  eslint:
+    version: 9.39.5
+    group: tooling
+    side: both
+    why: five repositories resolve 9.39.5, nivo-backend 9.39.4.
+  eslint-plugin-react-hooks:
+    version: 7.1.1
+    group: tooling
+    side: fe
+    why: '@starci/eslint-canon-fe 5.0.0 enables its recommended set (set-state-in-effect, refs, purity, immutability) at error and needs version 7 or newer; 7.1.1 is what the runtime examples resolve.'
+  '@types/node':
+    version: 22.20.4
+    group: tooling
+    side: both
+    why: nivo-fe resolves 20.19.43 and nivo-backend 22.20.0; the package engines are node >=22.
+  # --- test
+  jest:
+    version: 29.7.0
+    group: test
+    side: be
+  ts-jest:
+    version: 29.4.12
+    group: test
+    side: be
+  '@types/jest':
+    version: 29.5.14
+    group: test
+    side: be
+  vitest:
+    version: 3.2.7
+    group: test
+    side: fe
+  '@vitest/coverage-v8':
+    version: 3.2.7
+    group: test
+    side: fe
+  '@playwright/test':
+    version: 1.63.0
+    group: test
+    side: fe
+    why: nivo-fe pins 1.51.1 and starci-next-fe 1.63.0; the newer wins and the viewport projects need no older API.
+  jsdom:
+    version: 29.1.1
+    group: test
+    side: fe
+  '@vitejs/plugin-react':
+    version: 5.2.0
+    group: test
+    side: fe
+  '@testing-library/react':
+    version: 16.3.3
+    group: test
+    side: fe
+    why: nivo-fe resolves 16.3.2, the other two 16.3.3.
+  '@testing-library/jest-dom':
+    version: 7.0.1
+    group: test
+    side: fe
+  # --- framework
+  next:
+    version: 16.1.6
+    group: framework
+    side: fe
+  react:
+    version: 19.2.3
+    group: framework
+    side: fe
+  react-dom:
+    version: 19.2.3
+    group: framework
+    side: fe
+  '@nestjs/core':
+    version: 11.2.5
+    group: framework
+    side: be
+    why: nivo-backend resolves 11.1.27, starci-next and mia-mia-backend 11.2.5.
+  '@nestjs/common':
+    version: 11.2.5
+    group: framework
+    side: be
+  '@nestjs/platform-express':
+    version: 11.2.5
+    group: framework
+    side: be
+  '@nestjs/testing':
+    version: 11.2.5
+    group: framework
+    side: be
+  '@nestjs/terminus':
+    version: 11.1.1
+    group: framework
+    side: be
+    why: the health skeleton (hfs sync --init) answers { status, info, error, details } through Terminus; nivo-backend, starci-next and mia-mia-backend all resolve 11.1.1.
+  next-intl:
+    version: 4.13.6
+    group: framework
+    side: fe
+    why: every HFS front end uses next-intl with the [locale] segment (hfs sync --init writes it); nivo-fe resolves 4.13.6.
+  supertest:
+    version: 7.3.0
+    group: tooling
+    side: be
+    why: the composition spec of the back-end skeleton boots the real AppModule and calls /health/live; starci-next and mia-mia-backend resolve 7.3.0, nivo-backend 7.2.2.
+  # --- ui
+  '@heroui/react':
+    version: 3.2.6
+    group: ui
+    side: fe
+    why: nivo-fe resolves 3.2.4, starci-next-fe and miamia-fe 3.2.6.
+  '@heroui/styles':
+    version: 3.2.6
+    group: ui
+    side: fe
+    why: nivo-fe resolves 3.2.4, starci-next-fe and miamia-fe 3.2.6.