fg-devkit 1.22.0 → 1.24.0

package/.cursor/rules/core-coding-standards.mdc

@@ -1,291 +0,0 @@
----
-description: Core coding standards for Vue / fds-vue-core frontend projects
-alwaysApply: true
----
-
-# Core Coding Standards
-
-## Keep changes focused
-
-- Make the smallest safe change that solves the request.
-- Avoid unrelated refactors in the same task.
-- Preserve existing behavior unless a behavior change is requested.
-
-## Code comments
-
-- Do not add comments in code unless the user explicitly asks for them.
-- Prefer self-explanatory naming and structure over inline comments.
-- When updating existing code, do not add new comments or expand existing ones unless requested.
-- Exception: update comments only when they are required to keep an existing comment accurate after a behavior change in the same task.
-
-## Communication efficiency
-
-- Do not waste tokens: keep responses concise, high-signal, and scoped to the request.
-- Prefer short summaries over long explanations unless deeper detail is explicitly requested.
-
-## Evidence-first implementation
-
-- Never guess or hallucinate APIs, component props, or framework behavior.
-- Verify implementation details against authoritative sources first (official docs, project code, and library types/source).
-- If documentation is missing or ambiguous, state uncertainty explicitly and choose the safest validated approach.
-
-## Match project conventions
-
-- Follow established naming, file structure, and component patterns.
-- Reuse existing utilities and query/composable patterns before adding new ones.
-- Keep TypeScript types explicit at API boundaries.
-
-## Strict TypeScript
-
-- Keep TypeScript and Vue template typing strict (`strict: true`, `strictTemplates: true`).
-- Do not introduce `any`; use `unknown` for unsafe input and narrow before use.
-- Type API boundaries explicitly (request payloads, response DTOs, mutation variables, callback contracts).
-- Prefer named reusable types under `src/types/<domain>/` for shared domain shapes; re-export from `src/types/index.ts`. Do not keep shared interfaces in views, stores, or query files.
-- Avoid non-null assertions unless guarded by `enabled` checks or equivalent runtime guarantees.
-
-## API boundaries
-
-- Components and views should not call low-level HTTP/API clients directly for feature data fetching.
-- Centralize HTTP and endpoint wiring in a dedicated API layer (for example `src/api/endpoints/*` or the convention used in the repo).
-- Consume server state through query/mutation hooks (for example `src/queries/*` or equivalent), not ad-hoc fetches in UI code.
-
-## Query strings
-
-- Build query strings with `URLSearchParams` (or a shared helper that wraps it).
-- Do not concatenate `key=value` fragments with `&`.
-- Let `URLSearchParams` encode values. Do not interpolate untrusted or user-entered values into URLs.
-- `toString()` has no leading `?`. Prefix it when appending to a path, and skip empty values instead of emitting empty keys.
-- For list views, derive the query string in the view from route filter state (`requestQueryParams` computed). The API layer should accept the query string, not reconstruct filters.
-
-## State-management boundaries
-
-- Use TanStack Query for server state and caching. Do not add Vuex for new work.
-- Use Pinia only for client/app state that is not owned by the server (for example `src/pinia/*`).
-- Do not duplicate the same state across the query cache and Pinia unless the project explicitly documents that pattern.
-- When a project is migrating Vuex → Query/Pinia, follow that repo’s local migration rules (if present) instead of expanding Vuex.
-
-## TanStack Query server-state conventions
-
-- Use TanStack Query for server state; avoid duplicating server data in ad-hoc local state.
-- Keep API calls in the API layer and expose query/mutation hooks from a dedicated hooks folder.
-- Build query keys as stable arrays of serializable primitives; when using refs, key by `.value` in a computed key.
-- Prefer shared query key constants/factories to keep invalidation and cache updates consistent.
-- Add `enabled` guards for required IDs/paths to prevent invalid requests.
-- Use `placeholderData: keepPreviousData` for paginated/filter-driven views to avoid UI flicker.
-- Set `staleTime` intentionally per resource; keep `refetchOnWindowFocus` off unless fresh-on-focus behavior is required.
-- On mutation success, update cache intentionally (`setQueryData`) and/or invalidate the narrowest matching keys.
-- Respect shared query client retry behavior and only override retries when endpoint-specific behavior is needed.
-
-### Query loading UI
-
-TanStack Query v5 flags (do not treat them as interchangeable):
-
-| Flag | Meaning |
-| --- | --- |
-| `isPending` | No cached data yet (`status === 'pending'`) |
-| `isFetching` | Any in-flight request, including background refetch |
-| `isLoading` | First fetch in flight (`isPending && isFetching`) |
-
-Rules:
-
-1. **Content-blocking / full-page spinner** — use `isLoading` (or combine several `isLoading*` flags). Prefer `isLoading` over bare `isPending` when the query can be `enabled: false` (lazy/disabled queries stay `isPending` without fetching).
-2. **Do not use bare `isFetching` for blocking UI** — it re-shows the full loader on every background refetch. Use `isFetching` only for subtle “refreshing” indicators while keeping content visible.
-3. **Paginated / `keepPreviousData` lists** — show a hard loader only when there is nothing useful to render:
-
-```ts
-const isLoading = computed(() => isPending.value || (isFetching.value && !data.value))
-```
-
-4. **Multiple queries for one screen** — combine with OR into one (or purpose-prefixed) computed:
-
-```ts
-const isLoading = computed(() => isLoadingDetails.value || isLoadingList.value)
-```
-
-5. **No passthrough aliases** — do not wrap a single flag (`const loading = computed(() => isFetching.value)`). Destructure and rename instead:
-
-```ts
-const { data, isLoading, error } = useGetDetails(id)
-// template: v-show="isLoading"
-```
-
-6. **Naming** — local query-derived booleans use the `is*` prefix: `isLoading`, `isLoadingUnits`, `isLoadingHistory`. Keep FDS/component prop names as-is (`:loading="isLoading"`). Mutations: rename `isPending` to intent (`isSaving`, `isSubmitting`, `isUploading`).
-
-- TanStack Query boolean flags (`isPending`, `isSuccess`, `isError`) are typed `Ref<false> | Ref<true>`. `vue-tsc` unwraps that union in templates to `boolean`; the Vue language plugin may not.
-- Narrow in script (`const isPending = mutation.isPending as Ref<boolean>`), then bind without `.value` (`:loading="isPending"`). Do not use `.value` in templates (fails `vue-tsc`) and do not add a wrapping `computed` only to satisfy the editor.
-
-## Mutation cache behavior
-
-- Every mutation should define post-success cache behavior.
-- Use `invalidateQueries` for stale collections and `setQueryData` for direct entity updates.
-- Invalidate the narrowest query keys that match changed resources.
-
-## Vue Router conventions
-
-- Organize route definitions in modules (for example `src/router/modules/*`) composed from a single router entry (for example `src/router/index.ts`), matching the repo layout.
-- Every user-facing route should define `meta.title`; provide breadcrumb metadata for detail/flow routes when needed.
-- Use shared route guards for auth/anonymous access control instead of duplicating checks in views.
-- Prefer `props: true` and typed route params in components instead of reading raw params everywhere.
-- Prefer named-route navigation for internal flows (`{ name, params, query }`) and reserve raw path pushes for simple/static redirects.
-- Preserve existing query params intentionally when updating filters, pagination, or tab state.
-- Returning to a view whose filters live in the URL: call `usePreviousLocation` from `fds-vue-core` in setup. `router.push('/path')` drops that query. Browser back keeps it.
-- Use `hrefFor` on `router-link` and `FdsTabsItem`, and `goTo` on back buttons, only when the target is that same view. Leave other navigations unchanged.
-- `hrefFor(path)` reuses the previous history entry, including `_search`, `_page`, and filters, when its pathname matches. Otherwise it returns the path only.
-- `goTo(fallback, matchPaths?)` calls `router.back()` when the previous entry matches, so scroll is kept. Otherwise it pushes the fallback path.
-- Pass `matchPaths` when several paths count as the same place. Without it, only the fallback path is compared.
-
-```ts
-import { usePreviousLocation } from 'fds-vue-core'
-
-const { hrefFor, goTo } = usePreviousLocation()
-
-const goBack = () => {
-  goTo('/services/J4', ['/services/J4', '/services'])
-}
-```
-
-```vue
-<router-link :to="hrefFor(breadcrumb.path)">
-  {{ breadcrumb.name }}
-</router-link>
-<FdsTabsItem :to="hrefFor(tab.path)" />
-<FdsButtonMinor :text="t('common.back')" icon="left" @click="goBack" />
-```
-
-- Lazy-load route components with dynamic imports to keep initial bundles smaller.
-- Name organisation route params by domain meaning, not generic `id`:
-  - top org: `:topClientNumber`
-  - unit/sub-org: `:unitClientNumber`
-  - Prefer `/organisations/:topClientNumber/units/:unitClientNumber` over `:id` / `:clino`.
-- Keep route param names aligned with component props when using `props: true`.
-
-## Vue and UI expectations
-
-- Prefer clear, readable templates over compact but hard-to-follow expressions.
-- Keep components focused; extract repeated UI blocks when duplication grows.
-- Keep localization text in language files instead of hardcoded UI strings.
-
-## FDS-first component usage
-
-- Use `fds-vue-core` components as the default choice for UI building blocks.
-- Multi-step wizards use `FdsWizard` from `fds-vue-core`. Follow the project’s wizard rule file when one exists (for example `.cursor/rules/fds-wizard.md`).
-- Before adding custom UI, check whether an FDS component already solves the use case.
-- Prefer extending composition around FDS components over re-implementing design-system behavior.
-- Keep visual consistency by matching FDS variants, spacing patterns, and interaction styles.
-
-## Asset creation policy
-
-- Do not create icons, images, illustrations, or placeholder content unless explicitly requested.
-- Assume `fds-vue-core` provides the required visual assets and use those first.
-- If a required asset appears missing, clearly point out the gap instead of inventing a replacement.
-
-## FDS typography (fds-vue-core)
-
-- For headings, use `FdsH1`, `FdsH2`, and `FdsH3` (not raw `h1/h2/h3`).
-- `FdsH1/FdsH2/FdsH3` use the `text` prop for content and support `size` (`sm|md|lg|xl|responsive`).
-- When layout spacing needs to be neutralized, reset heading spacing with `class="m-0"` (and add explicit margins as needed).
-- Use `FdsLead` for intro/lead paragraphs, `FdsMeta` for metadata/secondary text, and `FdsLabel` for short labels.
-- `FdsLead`, `FdsMeta`, and `FdsLabel` render slot content; prefer these over custom styled spans for text semantics.
-
-## Tailwind (v4+)
-
-- Use Tailwind v4 patterns and utilities (for example `tailwindcss@4` with `@tailwindcss/vite` where applicable).
-- Prefer utility classes in templates; only add custom CSS when utilities cannot express the design.
-- Follow existing FDS token/preset styling (`fds-vue-core` tokens and preset) instead of inventing parallel design tokens.
-- Always use Tailwind/FDS design tokens for colors, spacing, typography, radius, and shadows.
-- Never invent ad-hoc color values (for example hex/rgb/hsl literals) when a tokenized utility exists.
-- Keep spacing and typography explicit in class names; avoid hidden styling in deep selectors.
-- Use `!` utility overrides sparingly and only when a component default cannot be changed safely.
-- For Tailwind v4 important modifiers, use postfix-important utility syntax (for example `grid-cols-1!`) instead of prefix syntax (for example `!grid-cols-1`).
-- Stack repeated items with parent `flex flex-col gap-*` (or `space-y-*`). Do not use `mb-* last:mb-0` or `last-of-type:mb-*` — those variants often miss the last `v-for` item (extra Vue/FDS nodes) and trip Tailwind conflict lint.
-
-## Figma MCP implementation workflow
-
-- When using Figma MCP, implement the design as specified (layout, spacing, typography, states, and interactions).
-- Treat the Figma file as source of truth for UI behavior unless product/technical constraints are explicitly documented.
-- Primary choice for implementation is `fds-vue-core` components that best match the design intent.
-- Only create custom UI when no suitable FDS component exists; keep custom parts minimal and design-token based.
-- If any Figma detail cannot be implemented exactly, document the deviation and choose the closest FDS-aligned solution.
-
-## i18n and content
-
-- Do not hardcode user-facing copy in templates or script logic; use `t(...)` keys.
-- Add or update locale entries under the project’s language folder (for example `src/lang/*.json`) when introducing new text.
-- Keep translation keys descriptive and grouped by screen/feature.
-- Avoid storing i18n keys inside data/definition arrays (e.g. `i18nKey`) and translating later via dynamic keys or large switch statements. Prefer building definitions with already-translated `label: t('...')` (often as a `computed`) so types stay strict and templates stay simple.
-
-## Formatting and locale consistency
-
-- Prefer shared formatting utilities for date/number/currency output instead of ad-hoc inline formatting.
-- Use Swedish locale conventions (`sv-SE`) unless a feature explicitly requires another locale.
-
-## Accessibility baseline
-
-- Use semantic HTML and accessible FDS components first; avoid click-only `div`/`span` patterns.
-- Ensure form controls have proper labels and required ARIA attributes when needed.
-- All interactive elements must be keyboard reachable and show visible focus states.
-- Provide meaningful accessible names for icon-only actions and links.
-
-## Async UI states
-
-- For data-driven screens, always handle loading, empty, error, and success states explicitly.
-- Use consistent FDS-based feedback patterns for loaders, alerts, and empty-state messaging.
-
-## Error handling UX
-
-- Do not swallow errors silently; surface actionable feedback to users.
-- Use consistent FDS feedback patterns for API failures (alerts/toasts/inline messages).
-- Keep technical error details out of user-facing copy unless explicitly required.
-
-## Performance guardrails
-
-- Avoid unnecessary reactive churn (redundant watchers/computed chains in hot paths).
-- Memoize expensive derived values and keep render-time computations lightweight.
-- Keep route-level and heavy feature components lazy-loaded.
-
-## Security and data handling
-
-- Never commit or expose secrets, tokens, or sensitive identifiers in code, logs, or UI.
-- Validate and sanitize untrusted values from route/query params before use.
-- Type and validate outgoing payloads to prevent accidental over-posting.
-
-## Testing expectations
-
-- Do not add new automated tests unless the user explicitly asks for them.
-- Update existing tests when your change requires it (for example broken assertions, renamed APIs, or changed behavior covered by current tests).
-- When new tests are requested, add them close to the affected feature.
-- Keep tests behavior-focused and avoid brittle implementation-detail assertions.
-- When no new tests are requested, rely on lint, typecheck, and manual verification of critical flows where practical.
-
-## CI/CD
-
-- Treat the repository’s CI configuration as the source of truth (`Jenkinsfile`, GitHub Actions, or equivalent).
-- Prefer frozen lockfile installs in CI (for example `pnpm install --frozen-lockfile --prefer-offline`) so CI matches local installs.
-- Keep build, lint, typecheck, and test stages deterministic; document any project-specific stages (security scans, i18n download, Docker publish) in the repo README or a dedicated rule file.
-
-## Quality checks before finishing
-
-- Run relevant checks for touched code (lint and typecheck when practical).
-- Run and update existing tests when your change affects them; add new tests only when the user explicitly requests them.
-- Fix issues introduced by your change before handing off.
-- Call out anything you could not verify.
-
-## Definition of done
-
-- Lint and type checks pass for touched code.
-- UI matches Figma/FDS expectations and uses tokenized styling.
-- i18n keys, async states, and cache behavior are handled for changed features.
-- Note any constraints, deviations, or unverified parts in handoff.
-
-## Legacy/deprecation policy
-
-- For new work, follow the current preferred patterns in this document.
-- Do not expand usage of known legacy patterns when a supported modern pattern exists.
-- If migration is out of scope, isolate legacy touchpoints and avoid spreading them.
-
-## Example: API data safety
-
-```ts
-// Prefer typed fallbacks when API data may be missing.
-const total = response?.stats?.total ?? 0
-```

package/scaffold/vue/.gitignore

@@ -1,13 +0,0 @@
-.DS_Store
-node_modules
-/dist
-pnpm-debug.log*
-
-.env.local
-.env.*.local
-*env.local
-
-.idea
-*.sw?
-
-tsconfig.tsbuildinfo

package/scripts/cz/.cz-config.cjs

@@ -1,29 +0,0 @@
-/**
- * cz-git config used by fg-devkit commit flows.
- * Keep this in czrc-compatible shape for `czg --config`.
- */
-module.exports = {
-  types: [
-    { value: 'feat', name: 'feat(scope): Added' },
-    { value: 'fix', name: 'fix(scope): Fixed' },
-    { value: 'perf', name: 'perf(scope): Performance' },
-    { value: 'refactor', name: 'refactor(scope): Changed' },
-    { value: 'chore', name: 'chore(scope): Changed' },
-    { value: 'dep', name: 'dep(scope): Dependencies (single package or batch)' },
-    { value: 'vuln', name: 'vuln(scope): Security dependency update (single package or batch)' },
-    { value: 'fix(security)', name: 'fix(security): Security' },
-  ],
-  allowCustomScopes: true,
-  allowEmptyScopes: false,
-  allowBreakingChanges: [],
-  skipQuestions: ['breaking', 'footer', 'issues', 'issuePrefixes'],
-  maxSubjectLength: 120,
-  breaklineChar: '|',
-  useEmoji: false,
-  messages: {
-    type: 'Select the type of change you are committing:',
-    customScope: 'Packages (for dep/vuln) or scope:',
-    subject: 'Commit subject (imperative, no trailing period):',
-    body: "Optional body (use '|' for newline):",
-  },
-}

package/scripts/fleet-git-commit-push.mjs

@@ -1,75 +0,0 @@
-#!/usr/bin/env node
-/**
- * Maintainer: stage all changes, commit, and push on the current branch for every git repo under projects root.
- *
- * Usage (from fg-devkit repository root):
- *   pnpm exec fg-devkit fleet-git-commit-push --message="chore: sync toolchain" [projects-root] [--dry-run]
- *   pnpm exec fg-devkit fleet-git-commit-push -m "chore: sync toolchain"
- */
-
-import fs from 'node:fs'
-import path from 'node:path'
-import { fileURLToPath } from 'node:url'
-
-import { collectFleetGitRepos } from './fleet-project-repos.mjs'
-import { filterCommitPushPositionalArgs, resolveCommitMessage } from './git-fleet-common.mjs'
-import { runFleetGitCommitPush } from './git-commit-push-fleet-common.mjs'
-
-const scriptDir = path.dirname(fileURLToPath(import.meta.url))
-const fgDevkitRoot = path.resolve(scriptDir, '..')
-const fgDevkitPkgPath = path.join(fgDevkitRoot, 'package.json')
-const LOG_PREFIX = '[fleet-git-commit-push]'
-
-const cliArgs = process.argv.slice(2)
-const dryRun = cliArgs.includes('--dry-run')
-const positionalArgs = filterCommitPushPositionalArgs(cliArgs)
-const projectsRootArg = positionalArgs.find((a) => !a.startsWith('-'))
-const projectsRoot = projectsRootArg
-  ? path.resolve(process.cwd(), projectsRootArg)
-  : path.resolve(fgDevkitRoot, '..')
-
-function assertFgDevkitMaintainerContext() {
-  if (path.resolve(process.cwd()) !== fgDevkitRoot) {
-    console.error(`${LOG_PREFIX} Run from the fg-devkit repository root.`)
-    process.exit(1)
-  }
-  try {
-    const pkg = JSON.parse(fs.readFileSync(fgDevkitPkgPath, 'utf8'))
-    if (pkg?.name !== 'fg-devkit') {
-      console.error(`${LOG_PREFIX} package.json name must be fg-devkit.`)
-      process.exit(1)
-    }
-  } catch {
-    console.error(`${LOG_PREFIX} Could not read fg-devkit package.json.`)
-    process.exit(1)
-  }
-}
-
-async function main() {
-  assertFgDevkitMaintainerContext()
-
-  if (!fs.existsSync(projectsRoot)) {
-    console.error(`${LOG_PREFIX} projects root not found: ${projectsRoot}`)
-    process.exit(1)
-  }
-
-  const commitMessage = await resolveCommitMessage(cliArgs, LOG_PREFIX)
-  const repos = collectFleetGitRepos(projectsRoot)
-
-  console.log(`${LOG_PREFIX} projectsRoot=${projectsRoot}`)
-  console.log(`${LOG_PREFIX} repositories=${repos.length}`)
-
-  const exitCode = runFleetGitCommitPush({
-    repos,
-    projectsRoot,
-    commitMessage,
-    dryRun,
-    logPrefix: LOG_PREFIX,
-  })
-  process.exit(exitCode)
-}
-
-main().catch((err) => {
-  console.error(LOG_PREFIX, err)
-  process.exit(1)
-})

package/scripts/fleet-git-discard.mjs

@@ -1,66 +0,0 @@
-#!/usr/bin/env node
-/**
- * Maintainer: discard tracked git changes in every repository under projects root.
- *
- * Usage (from fg-devkit repository root):
- *   pnpm exec fg-devkit fleet-git-discard [projects-root] [--dry-run]
- */
-
-import fs from 'node:fs'
-import path from 'node:path'
-import { fileURLToPath } from 'node:url'
-
-import { collectFleetGitRepos } from './fleet-project-repos.mjs'
-import { runFleetGitDiscard } from './git-discard-fleet-common.mjs'
-
-const scriptDir = path.dirname(fileURLToPath(import.meta.url))
-const fgDevkitRoot = path.resolve(scriptDir, '..')
-const fgDevkitPkgPath = path.join(fgDevkitRoot, 'package.json')
-const LOG_PREFIX = '[fleet-git-discard]'
-
-const cliArgs = process.argv.slice(2)
-const dryRun = cliArgs.includes('--dry-run')
-const projectsRootArg = cliArgs.find((a) => !a.startsWith('-'))
-const projectsRoot = projectsRootArg
-  ? path.resolve(process.cwd(), projectsRootArg)
-  : path.resolve(fgDevkitRoot, '..')
-
-function assertFgDevkitMaintainerContext() {
-  if (path.resolve(process.cwd()) !== fgDevkitRoot) {
-    console.error(`${LOG_PREFIX} Run from the fg-devkit repository root.`)
-    process.exit(1)
-  }
-  try {
-    const pkg = JSON.parse(fs.readFileSync(fgDevkitPkgPath, 'utf8'))
-    if (pkg?.name !== 'fg-devkit') {
-      console.error(`${LOG_PREFIX} package.json name must be fg-devkit.`)
-      process.exit(1)
-    }
-  } catch {
-    console.error(`${LOG_PREFIX} Could not read fg-devkit package.json.`)
-    process.exit(1)
-  }
-}
-
-function main() {
-  assertFgDevkitMaintainerContext()
-
-  if (!fs.existsSync(projectsRoot)) {
-    console.error(`${LOG_PREFIX} projects root not found: ${projectsRoot}`)
-    process.exit(1)
-  }
-
-  const repos = collectFleetGitRepos(projectsRoot)
-  console.log(`${LOG_PREFIX} projectsRoot=${projectsRoot}`)
-  console.log(`${LOG_PREFIX} repositories=${repos.length}`)
-
-  const exitCode = runFleetGitDiscard({
-    repos,
-    projectsRoot,
-    dryRun,
-    logPrefix: LOG_PREFIX,
-  })
-  process.exit(exitCode)
-}
-
-main()

package/scripts/fleet-git-pull.mjs

@@ -1,65 +0,0 @@
-#!/usr/bin/env node
-/**
- * Maintainer: git pull on the current branch for every git repository under projects root.
- *
- * Usage (from fg-devkit repository root):
- *   pnpm exec fg-devkit fleet-git-pull [projects-root] [--dry-run]
- */
-
-import fs from 'node:fs'
-import path from 'node:path'
-import { fileURLToPath } from 'node:url'
-
-import { collectFleetGitRepos } from './fleet-project-repos.mjs'
-import { runFleetGitPull } from './git-pull-fleet-common.mjs'
-
-const scriptDir = path.dirname(fileURLToPath(import.meta.url))
-const fgDevkitRoot = path.resolve(scriptDir, '..')
-const fgDevkitPkgPath = path.join(fgDevkitRoot, 'package.json')
-
-const cliArgs = process.argv.slice(2)
-const dryRun = cliArgs.includes('--dry-run')
-const projectsRootArg = cliArgs.find((a) => !a.startsWith('-'))
-const projectsRoot = projectsRootArg
-  ? path.resolve(process.cwd(), projectsRootArg)
-  : path.resolve(fgDevkitRoot, '..')
-
-function assertFgDevkitMaintainerContext() {
-  if (path.resolve(process.cwd()) !== fgDevkitRoot) {
-    console.error('[fleet-git-pull] Run from the fg-devkit repository root.')
-    process.exit(1)
-  }
-  try {
-    const pkg = JSON.parse(fs.readFileSync(fgDevkitPkgPath, 'utf8'))
-    if (pkg?.name !== 'fg-devkit') {
-      console.error('[fleet-git-pull] package.json name must be fg-devkit.')
-      process.exit(1)
-    }
-  } catch {
-    console.error('[fleet-git-pull] Could not read fg-devkit package.json.')
-    process.exit(1)
-  }
-}
-
-function main() {
-  assertFgDevkitMaintainerContext()
-
-  if (!fs.existsSync(projectsRoot)) {
-    console.error(`[fleet-git-pull] projects root not found: ${projectsRoot}`)
-    process.exit(1)
-  }
-
-  const repos = collectFleetGitRepos(projectsRoot)
-  console.log(`[fleet-git-pull] projectsRoot=${projectsRoot}`)
-  console.log(`[fleet-git-pull] repositories=${repos.length}`)
-
-  const exitCode = runFleetGitPull({
-    repos,
-    projectsRoot,
-    dryRun,
-    logPrefix: '[fleet-git-pull]',
-  })
-  process.exit(exitCode)
-}
-
-main()

package/scripts/sync-core-coding-standards.mjs

@@ -1,77 +0,0 @@
-#!/usr/bin/env node
-/**
- * Syncs .cursor/rules/core-coding-standards.mdc into the consumer repo.
- * Rewrites frontmatter description to include the consumer package name.
- *
- * Usage:
- *   node node_modules/fg-devkit/scripts/sync-core-coding-standards.mjs
- *   pnpm exec fg-devkit sync-core-coding-standards
- */
-
-import fs from 'node:fs'
-import path from 'node:path'
-import { fileURLToPath } from 'node:url'
-
-const projectRoot = process.cwd()
-const scriptDir = path.dirname(fileURLToPath(import.meta.url))
-
-function findFgDevkitPackageRoot() {
-  const candidates = [
-    path.resolve(scriptDir, '..'),
-    path.join(projectRoot, 'node_modules', 'fg-devkit'),
-    path.join(projectRoot, 'node_modules', 'fds-vue-core', 'node_modules', 'fg-devkit'),
-  ]
-  for (const p of candidates) {
-    if (fs.existsSync(path.join(p, 'package.json'))) {
-      return p
-    }
-  }
-  return null
-}
-
-function getConsumerPackageName() {
-  const pkgPath = path.join(projectRoot, 'package.json')
-  if (!fs.existsSync(pkgPath)) {
-    return 'consumer-project'
-  }
-  try {
-    const pkg = JSON.parse(fs.readFileSync(pkgPath, 'utf8'))
-    if (typeof pkg.name === 'string' && pkg.name.trim() !== '') {
-      return pkg.name.trim()
-    }
-  } catch {
-    // fall through to default
-  }
-  return 'consumer-project'
-}
-
-const fgRoot = findFgDevkitPackageRoot()
-if (!fgRoot) {
-  console.error(
-    '[sync-core-coding-standards] Could not find fg-devkit (install fg-devkit or a package that bundles it, e.g. fds-vue-core).',
-  )
-  process.exit(1)
-}
-
-const sourcePath = path.join(fgRoot, '.cursor', 'rules', 'core-coding-standards.mdc')
-if (!fs.existsSync(sourcePath)) {
-  console.error('[sync-core-coding-standards] Missing source rule in fg-devkit package.')
-  process.exit(1)
-}
-
-const destinationPath = path.join(projectRoot, '.cursor', 'rules', 'core-coding-standards.mdc')
-const packageName = getConsumerPackageName()
-
-try {
-  const content = fs.readFileSync(sourcePath, 'utf8')
-  const updated = content.replace(
-    /^description:\s*.*$/m,
-    `description: Core coding standards for ${packageName}`,
-  )
-  fs.mkdirSync(path.dirname(destinationPath), { recursive: true })
-  fs.writeFileSync(destinationPath, updated, 'utf8')
-  console.log(`[sync-core-coding-standards] Updated ${destinationPath}`)
-} catch (err) {
-  console.error(`[sync-core-coding-standards] ${err.message}`)
-  process.exit(1)
-}

package/scripts/sync-peers-from-dev.mjs

@@ -1,31 +0,0 @@
-#!/usr/bin/env node
-/**
- * For library packages: copies versions from devDependencies/dependencies into peerDependencies
- * for every key already listed in peerDependencies, so declared peers stay aligned with local installs.
- *
- * Does not add new peer keys; warns and skips peers that have no matching dev/dependency entry.
- */
-
-import fs from 'node:fs'
-import path from 'node:path'
-
-const pkgPath = path.resolve(process.cwd(), 'package.json')
-const pkg = JSON.parse(fs.readFileSync(pkgPath, 'utf8'))
-
-const sources = { ...pkg.devDependencies, ...pkg.dependencies }
-
-pkg.peerDependencies = pkg.peerDependencies || {}
-const peerKeys = Object.keys(pkg.peerDependencies)
-
-for (const name of peerKeys) {
-  const version = sources[name]
-  if (version) {
-    pkg.peerDependencies[name] = version
-  } else {
-    // If missing locally, leave existing peer version untouched
-    console.warn(`[sync-peers] Skipping ${name} (not found in devDependencies/dependencies)`)
-  }
-}
-
-fs.writeFileSync(pkgPath, `${JSON.stringify(pkg, null, 2)}\n`)
-console.warn('[sync-peers] peerDependencies updated from devDependencies')