Load sign-in assets in the initial graph and defer the workspace, demo features, and mock client until needed. Split feature dependencies and clear stale files from the default production output. Document feature entry points for runtime imports and record the browser and Harness results.
48 KiB
Toolchain upgrade record (2026-11-02)
Version baseline
Versions were verified against the official npm registry's latest tags; the lockfile contains the complete resolutions. Only stable releases were used, without beta/RC versions. The upgrade selected Node.js LTS 26.13.0 and pinned pnpm to 12.16.1. Local verification used Node downloaded to a temporary directory after SHA-256 verification; the global Node installation was not replaced.
| Core dependency | Before upgrade | Recorded version |
|---|---|---|
Node.js (.nvmrc) |
22.12.0 | 26.13.0 LTS |
| pnpm | Unpinned; CI used 9 | 12.16.1 |
| Vite | 7.2.6 | 8.3.5 |
| Vue | 3.5.25 | 3.5.44 |
| Vue Router | 4.6.3 | 5.4.0 |
| Pinia | 3.0.3 | 4.1.0 |
| Naive UI | 2.43.2 | 2.45.3 |
| VueUse | 13.1.0 | 15.0.0 |
| ECharts | 6.0.0 | 6.1.0 |
| Axios | 1.10.0 | 1.21.0 |
| TypeScript | 5.9.3 | 6.0.3 (compatibility ceiling) |
| vue-tsc | 2.2.8 | 3.3.14 |
| Vitest / UI | 4.0.12 | 5.0.5 |
| ESLint | 9.39.1 | 10.14.0 |
| typescript-eslint | 8.47.0 (separate packages) | 8.72.1 |
| Prettier | 3.6.2 | 3.9.10 |
| Husky | 8.0.3 | 9.1.7 |
| lint-staged | 15.4.3 | 17.6.0 |
| Mock data generation | Mock.js 1.1.0 | Faker 10.6.0, Chinese locale |
| SVG spritemaps | vite-plugin-svg-icons 2.0.1 | @spiriit/vite-plugin-svg-spritemap 7.2.0 |
Other retained direct dependencies were also updated to verified stable releases and pinned exactly; see package.json for the full list. Dependencies with no newer release kept their existing latest version.
Required adaptations
- Optional CDN loading uses exact npm-version paths on jsDelivr and production files that actually exist in published packages. Removed the dom-to-image entry, which was no longer a dependency. Local bundling remains the default.
- Vite 8 uses Rolldown/Oxc. Removed ineffective
build.transpile, adoptedrolldownOptionsand Oxc minification settings, and delegated chunking to the native dependency graph. Preserved lazy routes, compressed files, deployment bases, and per-mode output directories. - Node configuration uses ESM path resolution, explicit
.tsextensions, and JSON import attributes for the native config loader. Unified@apiwith the actualsrc/apidirectory and fixed TypeScript's@images/*mapping. - Replaced the old SVG plugin's missing dependencies and obsolete dependency tree.
RIconstill addressed icons throughprefix + name; the new plugin generated separate hashed spritemaps respecting the deployment base.<use>uses standardhref. - Removed
vite-plugin-eslint, which rewrote source during development/builds. ESLint 10 uses native flat config. Retained useful existing rules, delegated formatting to Prettier, and kept lint/check behavior read-only by default. - Updated hooks for Husky 9, removing Husky 8 initialization and old package.json hooks. Staged checks use
--no-warn-ignoredonly to suppress notices for explicitly supplied ignored declaration files; real lint warnings still fail. Removed unused Webpack sprite loaders, depcheck, and duplicate ESLint presets. - Import VueUse's
MaybeRef/MaybeRefOrGetterfrom Vue. Axios exposes its existing API that returnsdataonly at boundaries with installed response-unwrapping interceptors; adapter regressions were added. - Fixed invalid assignments generated by TSX demo
v-modelbindings to destructuredconstvariables, using component-instance properties instead. - Router 5 permission guards return route results while retaining authentication, role, and allowlist checks. Cancel navigation when the home route is itself unauthorized to avoid redirect loops. Added real in-memory-router tests.
- Limited development dependency scanning to
index.htmlto avoid old build directories. Moved the SVG preview glob into a separate.tsmodule to work around Vite 8 scanning preserved JSX as JavaScript. Reassess the split when upstream supports that case. - Vitest reuses only Vue/TSX and auto-import transforms; it does not start mock services, HTML injection, icon scanning, or compression plugins. Fixed missing
awaitassertions and stale watermark/fullscreen expectations while retaining behavioral assertions. - Existing color-conversion regressions exposed inconsistent rgba spacing and lost alpha in eight-digit hex colors; both were fixed. Chart errors retain their original
cause. - Mock.js had an unresolved prototype-pollution advisory and direct
evalusage. Replaced it with a Chinese Faker instance while retaining person fields, pagination endpoints, and table demos. The updated mock plugin matches include paths relative todir; removed the duplicatedmock/prefix, waited for initial loading, and verified API responses. - During development, open
#/tables/remoteand inspectGET /api/list?page=1&pageSize=10under Network's Fetch/XHR filter. The endpoint uses the site-root path/api/list, without/ray-template/. Use the actual Vite port in startup logs. At this stage, static builds used the same local example-generation logic without depending on a mock server. - Aligned browser builds and Autoprefixer with Vite 8's Baseline Widely Available target. The development server defaults to loopback; LAN access requires explicit
--host. Excluded all build directories and.ai-localfrom watching to prevent repeated reloads during report builds. - CI and Docker use the same Node/pnpm versions and frozen-lockfile installs. Consolidated duplicate CI workflows to cover types, lint, formatting, tests, and builds. Preserved deployment from
mainto thedistbranch after checks pass.
Compatibility limits and reassessment conditions
TypeScript 7
The latest npm release at verification was 7.0.2, but vue-tsc's compiler wrapper did not fully support native TypeScript 7, and typescript-eslint@8.72.1 explicitly required <6.1.0. Retained 6.0.3 without disabling type checking or introducing peer conflicts. Upgrade only after both upstream projects explicitly support TypeScript 7 and complete verification passes.
Compatible transitive dependency overrides
Three narrowly scoped overrides in pnpm-workspace.yaml prevent upgraded dependencies from retaining older major versions with known advisories:
| Override | Verified usage contract | Removal condition |
|---|---|---|
@logicflow/core>uuid → 14.0.3 |
LogicFlow uses only argument-free v4() for IDs |
LogicFlow adopts a fixed version and flowchart verification passes |
minimatch@>=10 <11.0.1 → 11.0.4 |
ESLint matching functions and class interfaces still work; full lint passed | Upstream permits 11+; audit and lint pass after removing the override |
glob@>=9 <14.0.2 → 14.0.3 |
The js-beautify CLI uses hasMagic and globSync |
Upstream permits a fixed version; verification passes after removing the override |
Dependency build scripts use pnpm's allowBuilds list. LogicFlow's AI-notice postinstall is unrelated to runtime builds and is explicitly disabled; other entries retain only scripts required by existing native dependencies. The exact-version minimumReleaseAgeExclude entries recorded by pnpm resulted from this explicit upgrade to the latest stable versions, not from disabling all supply-chain checks.
CryptoJS
CryptoJS 4.2.0 was unmaintained but remained the final published release. Preserve existing synchronous AES APIs and ciphertext formats. Replace them with Web Crypto only alongside a design for legacy-ciphertext migration, asynchronous APIs, and caller adaptation. Client-embedded keys are not a server-side confidentiality boundary.
Verification record
Verified locally on macOS with Node.js 26.13.0 / pnpm 12.16.1:
| Check | Result |
|---|---|
pnpm env:check |
Passed; avoids colliding with pnpm's built-in doctor subcommand |
Frozen-lockfile install, pnpm peers check |
Passed without peer conflicts |
CI=true HUSKY=0 pnpm install --frozen-lockfile --offline in a fresh temporary directory |
Passed; reconstructed dependencies from cache without the original node_modules |
pnpm check |
Types, ESLint (zero warnings), Prettier, 42 test files / 146 tests, and production build passed |
pnpm dev-build |
Passed; produced dist/development and sourcemaps |
pnpm report |
Passed; static report at dist/report/stats.html, without opening a browser or retaining a report server |
vite build --configLoader native |
Passed; configuration does not depend on legacy extension guessing |
| Optional CDN build | Passed; all 9 referenced exact-version script URLs returned HTTP 200. Chrome login, home, and SVG preview had no console errors. |
pnpm audit |
0 info / low / moderate / high / critical; no ignored-advisory configuration |
pnpm outdated |
Reported only the TypeScript 7 compatibility exception and final-release CryptoJS deprecation |
| APIs of the three transitive overrides | uuid.v4/validate, globSync/hasMagic, and minimatch/Minimatch calls passed |
| commitlint | Accepted valid messages and rejected invalid formats |
| Mock HTTP API | /api/list?page=2&pageSize=10 returned 10 records / total 100; no pagination returned 100. Field and age-range checks passed. |
| Chrome development pages | Demo login, home, SVG menu icons, ECharts, LogicFlow nodes, and QR rendering passed |
| Chrome production preview | Login, real dependency versions on home, Chinese advanced-table data, 10→20 page-size changes, Chinese/English menus, and light/dark themes passed. No console errors were observed. |
Local evidence, including screenshots, is in ignored .ai-local/evidence/. production-home.png shows the production home page; production-table-dark.png shows English menus and a dark table; cdn-svg-icons.png shows CDN-build icons. Temporary installs, CDN verification configuration, and outputs are not committed.
At this stage, CI configuration and official Action inputs had been checked, but remote CI had not run. Docker was not installed, so no image build was performed. Real backends, Wujie hosts, other browsers, minimum-version devices, and complete print/download flows were not verified.
The production build still reported a shared chunk of about 2 MB, including shared component dependencies, and mixed static/dynamic ContentWrapper imports. Functional checks passed; warning thresholds were not raised to hide these issues. A future performance effort should use the static report to examine component exports and loading boundaries, then reverify route caching and initialization order.
2026-11-03: Hook, layout, and icon refactor verification
No dependencies or lockfile entries changed. Added icons:generate / icons:check. The generator uses the project's existing Prettier configuration and preserves declaration spacing required by ESLint. Vite generates a separate spritemap per top-level group; names and types come from the same directory manifest.
| Check | Observed result |
|---|---|
Node.js 26.13.0, pnpm 12.16.1, frozen-lockfile install, pnpm env:check |
Passed. Existing local Node 26.12.1 was below the requirement, so this run used a temporary 26.13.0 runtime. |
pnpm typecheck (including icons:check), pnpm lint |
Passed without weaker rules or new global ignores |
pnpm format:check / pnpm check |
Formatting flagged local TODO.md and .vscode/settings.json. Preserved those unrelated changes. pnpm check stopped at formatting; full success was not claimed. |
| Prettier on files added/changed by this task | Passed; generated manifests were also formatted directly with project configuration |
pnpm test:run |
Run separately; all 50 test files / 173 tests passed |
pnpm exec vite build |
Run separately and passed; 44 icons produced 7 separate hashed groups with no duplicate symbol IDs within a group |
| Chrome development build | Side/top/mixed navigation; nested-page menu matching; centered fixed width at 1200px; opening the drawer at 390px, collapsing after selection, and no page-level horizontal overflow; desktop preferences retained after reload; PNG screenshots and element fullscreen/restore |
| Chrome production preview | Demo login; 44 rendered icons; 7 icon asset paths respecting base; complete icon-copy operations; dark theme; Chinese/English new-page copy; content maximization and Esc; restoration after unmount/reload; content scrolled to 300px; scrolling footer and existing auto-height table rendering |
Pinia settings retained existing persistence keys. Legacy bare logo names migrate on read; lock screens still use the historical boolean format. Regressions cover the migration, concurrent refreshes, scroll-instance replacement, out-of-bounds navigation, asynchronous context-menu closure, fullscreen frame cleanup, and screenshot failures.
Local screenshots are in .ai-local/evidence/2026-11-03/. File watching initially hit EMFILE, so this development verification used CHOKIDAR_USEPOLLING=1; the workaround was not added to default development configuration. Shared-chunk size, mixed ContentWrapper imports, and mock CORS serialization warnings remain, without threshold changes. Physical printing, minimum-version browsers, and Wujie hosts were not verified.
2026-11-03: Automatic synchronization, comment conventions, and visual cleanup
No dependencies or lockfile entries changed. Icon generation is connected to dev, build, dev-build, report, check, and the Vite build entry point; standalone typecheck and icons:check remain read-only. AGENTS.md introduced the shared comment style. Page layout and theme entry points are in the visual conventions.
| Check | Observed result |
|---|---|
Frozen-lockfile install and pnpm env:check |
Passed with Node.js 26.13.0 / pnpm 12.16.1 |
pnpm check |
Icon synchronization, types, and ESLint passed. Formatting flagged only unchanged .vscode/settings.json; full-check success was not claimed. |
pnpm test:run |
Run separately; all 52 test files / 181 tests passed |
pnpm build |
Passed, including generation, types, and production build; final output contained 44 icons and 7 separate spritemaps |
| Build without a development server | After adding a temporary SVG, confirmed icons:check reported a stale manifest, then ran pnpm build directly and verified automatic generation. Removed the temporary SVG and rebuilt final output. |
| Actual icon HMR | Add/rename/delete synchronized the manifest. Content edits changed asset hashes and retained search state. Adding/removing whole groups rebuilt plugin configuration and requested browser reloads. Regressions cover hyphenated group names and CLI execution through symlink paths. |
| Comment placement | Removed component introductions and stacked duplicates. Rechecked type, store, and constant descriptions against adjacent declarations; corrected the login-state description's storage medium. |
| Chrome layout | Dashboard, hooks, layout lab, and icon library at 1440/1280px desktop and 390px single-column widths, without page-level horizontal overflow. Retained compact login-page resource links. |
| Themes and languages | Production light/dark switching, dark selected-state foregrounds, and Chinese/English headings. Fixed raw translation keys after HMR replaced the i18n instance; covered translation recovery for hooks created before initialization. |
Development verification still used local CHOKIDAR_USEPOLLING=1 without changing the default watcher. The browser-control connection broke while restoring the viewport. A separate Chrome DevTools context then checked the final production artifacts. Final screenshots and phase records are in .ai-local/evidence/2026-11-03/polish/. Vue JSX hot replacement inside complex base components was not exhaustively tested. Production acceptance used freshly loaded final artifacts; these checks were not presented as real-backend, minimum-device, or physical-printing verification.
Shared-chunk size, mixed static/dynamic ContentWrapper imports, and mock CORS serialization warnings remain. Neither check strictness nor warning thresholds were relaxed.
2026-11-03: TypeScript project configuration split
The previous setup passed --noEmit only to the vue-tsc command. Reading project configuration directly caused allowImportingTsExtensions to trigger TS5096. Shared configuration now declares noEmit; the root references application, Node, and test configurations separately. Application/test configurations load Vue JSX and auto-import declarations. TypeScript 6's DOM includes iterable declarations. Vite still controls development/production sourcemaps through build.sourcemap.
Dependencies and the lockfile retained their existing versions. Commands and project ownership are in TypeScript project configuration.
With Node.js 26.13.0 and pnpm 12.16.1, pnpm check passed types, ESLint, Prettier, 59 test files / 240 cases, and the production build. pnpm dev-build passed and produced development JS sourcemaps. The TypeScript service confirmed project ownership for the application entry point, Vite configuration, mock files, and tests.
2026-11-03: AI Harness migration
Task entry points, scope registration, and verification commands were consolidated in the AI Harness. GitHub Actions validates context and regression paths through pnpm check. Removed old tool configuration and developer guides. TypeScript incremental caches moved to node_modules/.cache/ray-template/. Dependencies and lockfile versions stayed unchanged.
Local macOS verification used Node.js 26.13.0 and pnpm 12.16.1. Targeted checks passed for all six task scopes. New regressions cover empty test directories and exit codes, fail-fast behavior, and JSON reports when child commands fail. pnpm harness verify passed Harness validation, types, ESLint, Prettier, 60 test files / 242 cases, and the production build.
Reports are saved in .harness-local/runs/. npm pack --dry-run --ignore-scripts confirmed that local evidence directories were excluded from the package. Windows/Linux results awaited remote CI. Browser verification follows the separate Harness steps.
2026-11-03: Component directories and public demo discovery
Shared components were consolidated in src/components, retaining @/components and removing the unused RCollapse. Bilingual READMEs gained actual dashboard screenshots, quick-start instructions, and customization entry points. Public-build canonical metadata, sharing images, and sitemaps follow the Vite base; see the deployment guide.
pnpm harness verifypassed types, ESLint, Prettier, 63 test files / 265 cases, and the production build.- Checked builds for the official path, a custom subpath, and an unset site origin. Public home, sitemap, and resource URLs were consistent; ordinary builds emitted
noindex. - Chrome production previews verified desktop two-column and 390px single-column layouts, Chinese/English and light/dark switching, prefilled demo login, and project information/links with JavaScript disabled. GitHub About description, demo URL, and topics were read back and confirmed. Site builds were not deployed, and search-engine indexing was not verified.
2026-11-04: Static GitHub Pages deployment
The live home page matched index.html on the dist branch, and the referenced js/_toKey-BqfG5Sv9.js existed on that branch, yet Pages returned 404. The deployment root lacked .nojekyll, so Jekyll filtered underscore-prefixed files. Vite now copies public/.nojekyll to the deployment root. See the architecture map for deployment conventions.
- A clean
HEADplus this fix reused installed local dependencies to runpnpm harness verify; 66 test files / 285 cases and the production build passed. Full checks in the original worktree failed while initializing__test__/router/config.spec.ts; standalonepnpm buildpassed. - Build output contained
.nojekyll. All 12 JS/CSS assets referenced by the production-preview home page returned HTTP 200 with content matching the output. Chrome entered home using the demo account without console errors. GitHub Pages required a post-deployment recheck.
2026-11-04: Documentation workspace and inline examples
Documentation moved into apps/docs, sharing the root lockfile with the admin application and packages/utils. VitePress 1.6.4 uses Vite 6.4.5; the override applies only to VitePress, while the admin application retains Vite 8.3.5. @/utils/precision re-exports the shared package. RBarcode was still maintained by the application and loaded on demand by documentation.
- Local macOS verification with Node.js 26.13.0 and pnpm 12.16.1 passed
pnpm harness verify: 66 test files, 291 cases, and application/documentation production builds. Report:.harness-local/runs/all-ukYffY/report.json. - Checked target pages and anchors for 93 legacy paths. Chrome verified precision input, barcode redraw and invalid-input recovery, example code, search, legacy redirects, light/dark switching, and 390px layouts under the production subpath.
- Only local builds were verified. Docker images, remote CI, and the GitHub Pages site migration were not verified.
2026-11-04: Separating Ray Admin and shared capabilities
Ray Admin's application entry point moved to apps/admin. Documentation and the application consume eight shared packages through public entry points. Development, build, and Harness commands remain at the root; application/documentation Vite versions are pinned separately. pnpm pages:build produces combined output and, when a site origin is configured, separate legacy-documentation redirects.
- Frozen-lockfile installation and
pnpm harness verifypassed with Node.js 26.13.0 and pnpm 12.16.1, including package boundaries, independent type checks, 68 test files / 293 cases, and admin/documentation production builds. Report:.harness-local/runs/all-GPS5No/report.json. - Development
/api/listreturned HTTP 200. Chrome production previews verified demo login, navigation-preference restoration after reload, icons, and documentation interactions: TablePro cancellation/failure retry, shell navigation/themes, precision utilities, barcodes, route validation, debounce, and fullscreen. Checked targets/anchors for 93 legacy paths and generated 138 legacy-site redirects. - Docker, Wujie hosts, and remote CI were not run. The legacy-site migration required separate verification when published to GitHub Pages.
2026-11-04: Documentation examples and admin theme integration
Documentation component previews reuse the admin application's Naive UI light/dark themes and locale configuration. Inline examples isolate VitePress article styles. Examples requiring application context run through example.html from the same Pages build. The example host registers only demo routes, uses in-memory caching and an independent store, and documentation includes the source actually running.
pnpm harness verify passed 69 test files / 294 cases. Checked 26 embedded entry points and source references across 22 documentation pages in the combined output. Chrome production previews verified TablePro styling, light/dark themes, Chinese pagination, and failure retry; sampled component, directive, hook, and utility interactions and the normal admin login entry point. Border padding was 12px in desktop and 390px previews.
2026-11-05: HTTP mocks and backend contracts
Demos now use MSW 2.11.6 consistently. Startup waits for Service Worker readiness; development, production previews, and GitHub Pages share handlers. Removed the development-only Vite mock plugin and the production branch that called local person data directly. Initial routes moved to mock JSON; online reads/writes use standard GET/PUT APIs. The frontend still owns the component allowlist and shell routes.
Browser verification reproduced the known MSW 3.x issue in which interception stops after about five minutes, so the dependency was pinned to 2.11.6. Before business requests, probe the mock marker; if missing, recover through public stop/start APIs. Block business requests from falling through if recovery fails. Reassess the upgrade after an upstream fix passes long-running and background-resume verification. Keep the official worker unchanged; do not modify library message protocols manually.
pnpm api:generate creates downloadable OpenAPI 3.1 from runtime schemas. pnpm api:check checks contract/official MSW worker synchronization and is included in full checks. Recursive route-schema references point to their owning OpenAPI components, and regressions verify that all references resolve. Node/pnpm requirements remain as specified by manifests. Integration/deployment boundaries are in the backend guide.
- With Node.js 26.13.0 and pnpm 12.16.1,
pnpm harness verifypassed types, lint, formatting, package boundaries, 79 test files / 357 cases, and admin/documentation production builds. Report:.harness-local/runs/all-z0kewW/report.json. - Browser verification covered user CRUD, repeated input and cancellation, bulk operations, read-only accounts, favorite/history isolation, keyboard search, API-route saving, and reload readback. Verified independent scrolling in both regions, Chinese/English, and light/dark themes at 1280px desktop and 390px narrow widths. The documentation contract endpoint returned final JSON. Evidence:
.harness-local/browser/admin-2026-11-05/report.json. - After the Chrome automation connection failed, full production acceptance used an independent embedded Chromium preview. Mock requests still came from the Service Worker after extended operation. The available browser tools could not forcibly terminate the worker; regressions covered concurrent recovery and failure blocking. No real backend was connected, and neither deployment nor remote CI ran.
2026-11-06: Harness review and scoped verification
Official-guidance comparisons, structural assessment, and findings are in the Harness review record. Root guidance, the PR template, topic indexes, visual conventions, and reader guides now select verification by impact: local fixes use relevant tests or scopes, visible behavior uses affected pages/dimensions, and integration risk, releases, or explicit requests trigger full checks. Targeted api and icons entry points now include existing generated-artifact synchronization checks.
Local macOS verification used Node.js 26.13.0 and pnpm 12.16.1:
pnpm harness checkpassed. All 10 topics are reachable; all 81 test files are registered in at least one scope.pnpm harness verify harnesspassed 11 cases covering targeted scope, fail-fast behavior, and full-check compatibility. Report:.harness-local/runs/harness-MadWUc/report.json.- Ran
pnpm harness verify allonce to verify this change to verification entry points. Types, ESLint, formatting, API/package boundaries, 81 test files / 371 cases, and admin/documentation builds passed. Report:.harness-local/runs/all-3iyfPu/report.json; complete output:.harness-local/harness-review-2026-11-06.log. - After updating remaining old rules in the public tooling guide, reran only affected
pnpm harness verify docsand changed-file format/index checks. Documentation types, links, and build passed. Report:.harness-local/runs/docs-Uge4Sg/report.json.
No page behavior changed, so no UI/UX browser matrix was run. Remote CI and deployment were not run. Large-chunk and mixed static/dynamic import warnings remain, as do Node's experimental localStorage notices; these existing issues were outside this task. Passing commands does not establish browser or real-backend acceptance.
2026-11-06: English agent and maintainer guidance
Translated agent entry points, Harness topics and workflow, internal architecture/convention/history records, source-adjacent maintenance guides, CLI messages, and matching regression assertions into English. Root guidance now records this language convention. Product copy, public reader documentation, code examples, and the existing Chinese code-comment policy retain their intended languages. Commands, scope IDs, report fields, and verification triggers are unchanged by this translation pass.
- The translation covers 41 internal files. Hash comparisons confirmed that 99 protected product/reader files were unchanged from the start of this pass.
- Static review confirmed unchanged link destinations and fenced code examples, valid local links and translated heading anchors, and unchanged scope commands. Remaining Chinese text consists of literal UI/brand names and code-comment examples.
pnpm harness check, targeted ESLint, and formatting checks passed.pnpm harness verify harnesspassed all 11 cases; report:.harness-local/runs/harness-MVuum9/report.json.- Local translation evidence is in
.harness-local/english-guidance/. This pass did not rerun full application checks or browser acceptance because no application behavior or rendering changed.
References
- Node.js 26.13.0 LTS
- Vite 8 migration guide
- Vitest 5 migration guide
- Vue Router 5 migration guide
- Vue Language Tools TypeScript 7 support
- SVG Spritemap subpath deployment
- Faker localization
Remote CI follow-up
The historical Ubuntu failure was in detectOperatingSystem.spec.ts: the test read the Linux runner's actual user agent but always expected Unknown. Commit 83bada95 covers systems with mocked user agents and touch-point counts. CI for recorded baseline 80e80775 passed Ubuntu, macOS, Windows, and deployment. At that checkpoint, the matrix ran the same pnpm check on all three systems.
2026-11-06: Optional server and source distributions checkpoint
Added explicit browser/server/universal workspace ownership, universal route contracts and shared demo fixtures, and independent frontend/fullstack source exports with pruned lockfiles. The optional server pins NestJS 12.3.3, Prisma 7.10.1, node-redis 6.3.1 and esbuild 0.28.2. Prisma runtime checks and migration-engine downloads are explicitly allowed. The documentation still uses Vite 6; its Vue Router runtime does not load the optional Vite plugin, so that single peer combination is explicitly recorded in the workspace config.
Full Harness verification passed with Node 26.13.0 and pnpm 12.16.1: 103 frontend test files / 535 tests, 13 backend unit/platform tests with real Redis, API and workspace checks, types, lint/format, and both application builds. Six backend HTTP integration tests separately passed on temporary PostgreSQL 18.6 and Redis 8.2.11. The real external-service setup command applied Prisma migrations and initialized a private local administrator. No fixed production passwords were introduced.
An exported frontend archive extracted outside the repository passed frozen dependency installation, API/package/Harness checks and production build. Frontend/fullstack archive projection and nine distribution regressions passed. At this checkpoint, standalone fullstack install, container images and browser integration were still pending.
2026-11-06: Fullstack PC acceptance and upgrade
The server pins JOSE 6.2.12 for JWT signing and verification. The browser defaults to same-origin cookie transport in the fullstack launcher and Compose image. A repeatable Compose command provisions the signing key, dependencies and migrations from clean source. The rollout adds the administrator credential grant without recreating a renamed administrator.
The PC acceptance record contains the full Harness, real PostgreSQL/Redis, clean archive, Docker Compose and desktop Chrome results. It also records the external-service upgrade and the required sign-in after replacing legacy tokens. No remote workflow or public deployment was used.
2026-11-06: Direct Pages builds on main
Removed the Ubuntu/Windows/macOS verification matrix and the deployment job's dependency on it. The existing workflow file now contains one Pages job: every push to main builds the admin and documentation with pnpm pages:build, then publishes successful output to dist. It deliberately has no path filter, so shared packages, dependencies, tooling, and documentation cannot be omitted from the deployment trigger. Backend-only and maintenance changes also trigger a build. Manual dispatch is restricted to main; PRs and generated branches do not publish. The separate source-distributions workflow remains unchanged.
Updated contributor guidance, both READMEs, architecture, and the reader tooling guide to distinguish local full verification from Pages publication. The build command, deployment branch, site paths, source-reference environment, and .nojekyll behavior are unchanged.
Local verification used Node.js 26.13.0 and pnpm 12.16.1:
- Parsed the workflow YAML and checked main pushes, manual dispatch, excluded branches, removal of the check dependency, and successful-build-before-publication ordering.
pnpm harness verify allpassed environment, index, contract, boundary, type, lint, and format checks; 106 frontend test files / 552 cases; and both production site builds. It then stopped because the sandbox blocked the server tests from listening on loopback. Report:.harness-local/runs/all-8AOcdZ/report.json.- Re-ran only
pnpm server:checkwith loopback permission: server types, 12 tests, and build passed. The optional real Redis test was skipped. The remainingpnpm dist:checkpassed for both source editions. - Reused the completed site builds for
node scripts/assemble-pages.mjs; confirmed both entry pages,.nojekyll, the Mock worker, and both API contract files indist/pages.
Remote Actions and public deployment results were not inspected. No application rendering or asset-path behavior changed, so browser acceptance was not repeated.
2026-11-06: GitHub Pages artifact deployment
The branch publishing source (dist at /) runs a GitHub-managed workflow whose runner labels and artifact action are set by GitHub. The repository workflow now builds and deploys on ubuntu-24.04. It uploads dist/pages with actions/upload-pages-artifact@v5.0.0 and deploys with actions/deploy-pages@v5.0.1. The upload action delegates to upload-artifact v7, and both JavaScript actions use Node.js 24. Runner migration · Pages artifact release · Deployment action metadata
Build and deployment use separate jobs. The build has read access to the source. Only the deploy job receives Pages and OIDC write permissions. The build keeps .nojekyll in the artifact and uses the same site paths and source reference. For rollout, set the repository's Pages source to GitHub Actions and allow main in the github-pages environment. Publishing source setup
Local validation passed actionlint 1.7.12 and pnpm harness verify all, including both production builds, 569 frontend tests, and 12 server tests. The optional real Redis test was skipped. Assembling dist/pages confirmed both site entry points, both API contracts, the mock worker, and .nojekyll. The github-pages environment already allows main. The new workflow's hosted deployment is pending the source switch.
2026-11-09 Dependabot dependency updates
Vitest and its UI move together to 5.1.0. The sidebar regression waits for the mounted icons' asynchronous imports before inspecting the layout. The root and admin packages use Vite 8.3.6. The documentation package and VitePress use Vite 6.4.5 so the docs plugins resolve against the Vite version that runs them. Vitest 5.1.0 · Vite 8.3.6
Two earlier updates required follow-up before verification could pass. The five shared browser packages now declare the same Vue 3.5.45 peer as the apps. The mock client and Node test setup use the MSW 3.0.4 entry points and options, and the checked-in worker matches that release. Unhandled mock API calls fail locally as network errors. Other resources can pass through to the host. MSW migration guide · MSW 3.0.4
On macOS with Node.js 26.13.0 and pnpm 12.16.1, the combined candidate passed frozen-lockfile installation, peer dependency checks, and pnpm harness verify all. The run covered 575 frontend tests, 12 backend tests, both site builds, and both source distributions. The optional real Redis test was skipped. The assembled Pages preview passed demo sign-in, dashboard navigation, and the embedded TablePro failure and retry flow in Chrome. An existing MSW 2 registration could stall startup after an update. The versioned script URL let Chrome register the 3.0.4 worker and sign in while a tab from the previous build remained open. The 3.0.4 worker answered 37 health probes over 362 seconds.
2026-11-10: Admin startup and bundles
The admin entry includes the sign-in view and both configured locale dictionaries in the initial module graph. The workspace shell, chart and flow libraries, lock dialog, route schema converter, and mock code load when needed. In demo mode, the request guard waits for MSW readiness, shares startup between concurrent requests, and retries after a startup failure. Production bundle conventions
The largest minified JS file went from 2,511.83 kB to 498.49 kB with the default 500 kB warning limit. The mock startup chunk dropped from 888.75 kB to 404.41 kB after the people generator moved behind its endpoint. The output grew from 96 to 113 JS files as features gained independent loading boundaries. Related table, nested menu, and error views share entry files.
The existing local production directory had accumulated 2,165 JS files because Vite's application root is below the workspace output directory. The default production build now clears its own output. The clean output occupies 6.8 MiB on this machine, down from 156 MiB with stale builds present.
Local Chrome comparison used three cold HTTP cache loads per build, a 390 × 844 viewport, 4× CPU slowdown, 150 ms added network latency, and 1.6 Mbit/s download. The English sign-in heading's median LCP went from 6.78 s to 2.51 s. CLS was 0 on each run. The page loaded 23 JS resources in both builds, and their combined encoded response bodies went from 1,330.43 kB to 359.24 kB. The measured demo sign-in Event Timing sample went from 88 ms to 72 ms. Field Core Web Vitals require real-user measurements. Google's measurement guidance
pnpm harness verify all passed with loopback access for the server tests. The run covered 576 frontend tests, 12 server tests, both site builds, and both source distributions. The optional Redis integration test was skipped. The admin build stayed below the chunk warning limit. VitePress still reports a large chunk for the TablePro examples page.
The assembled Pages preview verified demo sign-in, session restoration, chart, flow, barcode, grouped table views, the 404 route, and the first opening of the lock dialog. The documentation iframe fetched rows, cleared them on a simulated failure, and restored them on retry. The example entry also rendered the workspace shell when requested. Browser evidence is in .harness-local/browser/admin-startup-2026-11-10/report.json.