@starci/eslint-canon-be 3.15.3 → 3.15.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,9 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 3.15.4 - 2026-11-04
|
|
4
|
+
|
|
5
|
+
- Changed: the runtime copies carry the R343, R251, R272 and R376 laws of `@starci/hfs` 5.7.0 and the release-6 canon pins.
|
|
6
|
+
|
|
3
7
|
## 3.15.3 - 2026-11-04
|
|
4
8
|
|
|
5
9
|
- Changed: the runtime copies carry `engine/runtime-root.mjs`, which moves an installed copy's legacy state with its owner and mode (`@starci/hfs` 5.6.1), and the release-5 canon pins. The runtime copy of the laws carries the R348 wording.
|
package/package.json
CHANGED
|
@@ -38,7 +38,7 @@ pins:
|
|
|
38
38
|
source: packages/next-data/package.json
|
|
39
39
|
why: 'the SWR data helpers of every front end (fe-stack data, owner:next-data-package): pollingRestart, the viewer and tenant key helpers, viewerSwrConfig and the viewer cache; each operation hook stays in the app and the package holds no component.'
|
|
40
40
|
'@starci/grammar':
|
|
41
|
-
version: 0.21.
|
|
41
|
+
version: 0.21.21
|
|
42
42
|
group: starci
|
|
43
43
|
install: registry
|
|
44
44
|
side: fe
|
|
@@ -52,28 +52,28 @@ pins:
|
|
|
52
52
|
source: packages/next-i18n/package.json
|
|
53
53
|
why: 'the next-intl stack of every front end (fe-stack i18n, owner:next-i18n-package): defineI18n over the locales of the app, the locale-negotiating proxy, the locale-aware navigation, the request config that loads the catalogs of the app and the locale read of the [locale] layout; the app keeps its message catalogs and writes none of the stack.'
|
|
54
54
|
'@starci/eslint-canon-be':
|
|
55
|
-
version: 3.15.
|
|
55
|
+
version: 3.15.4
|
|
56
56
|
group: starci
|
|
57
57
|
install: registry
|
|
58
58
|
side: be
|
|
59
59
|
source: packages/eslint-canon-be/package.json
|
|
60
60
|
why: 'the back-end ESLint canon: `loadHfs(import.meta.url)` of be/eslint.config.mjs finds the app-root hfs.json (kind app) and gives every linted file the view of the be side, and the project graph is built per side; its bundled runtime copies (slots, canon-pins, failure codes, the architecture machine) put .starcistacks and .sops.yaml at the app root; `starciBeConfig({ hfs: loadHfs(import.meta.url) })` is the typed factory and the BE-CONVENTION laws are its rules.'
|
|
61
61
|
'@starci/eslint-canon-fe':
|
|
62
|
-
version: 9.13.
|
|
62
|
+
version: 9.13.4
|
|
63
63
|
group: starci
|
|
64
64
|
install: registry
|
|
65
65
|
side: fe
|
|
66
66
|
source: packages/eslint-canon-fe/package.json
|
|
67
67
|
why: 'the front-end ESLint canon: `loadHfs(import.meta.url)` of fe/eslint.config.mjs finds the app-root hfs.json (kind app) and gives every linted file the view of the fe side, and the project graph is built per side; its bundled runtime copies (slots, canon-pins, failure codes, the architecture machine) put .starcistacks and .sops.yaml at the app root; the front end has no tests (FE_NO_TESTS R97 in hfs) and no-vietnamese-in-source (R91) applies.'
|
|
68
68
|
'@starci/eslint-grammar-core':
|
|
69
|
-
version: 0.21.
|
|
69
|
+
version: 0.21.21
|
|
70
70
|
group: starci
|
|
71
71
|
install: registry
|
|
72
72
|
side: fe
|
|
73
73
|
source: packages/eslint-grammar-core/package.json
|
|
74
74
|
why: 'the StarCi Grammar component API lint, versioned with @starci/grammar; front ends compose this family package with the universal FE canon.'
|
|
75
75
|
'@starci/eslint-grammar-offset-pop':
|
|
76
|
-
version: 0.21.
|
|
76
|
+
version: 0.21.21
|
|
77
77
|
group: starci
|
|
78
78
|
install: registry
|
|
79
79
|
side: fe
|
|
@@ -155,7 +155,7 @@ pins:
|
|
|
155
155
|
source: packages/mail/package.json
|
|
156
156
|
why: 'outgoing mail of a back end: a NestJS module and the Mailer port over SMTP (connect, greeting, socket and total timeouts, STARTTLS required by default, recipient, message and attachment checks, a shared SMTP target policy, coded errors, typed escaping render helpers returning { subject, text, html }), with @starci/mail/testing for its specs; the only importer of nodemailer (R90).'
|
|
157
157
|
'@starci/hfs':
|
|
158
|
-
version: 5.
|
|
158
|
+
version: 5.7.0
|
|
159
159
|
group: starci
|
|
160
160
|
install: registry
|
|
161
161
|
side: both
|
|
@@ -4204,7 +4204,7 @@ rules:
|
|
|
4204
4204
|
editions: [lite, full]
|
|
4205
4205
|
docs:
|
|
4206
4206
|
- {path: docs/application-stacks.md#r251-deploy-workflow, editions: [lite, full]}
|
|
4207
|
-
law: "In lite and full apps, deployment jobs declare a protected environment, explicit permissions and concurrency, materialize sealed secrets through SOPS_AGE_KEY or starci app secret materialize, and reference only the age key and transport SSH key/known_hosts secrets; every job that reads secrets.SOPS_AGE_KEY, a deployment job or not, is bound to the GitHub Environment whose members it opens, so it reads that environment's server key and never a repository secret of that name. Deployment jobs never embed a dotenv blob or write a dotenv file. Every remote workflow action uses a 40-hex commit SHA (local actions are allowed and container actions require a full sha256 digest); supply-chain reports each unpinned uses reference at its source line, including disabled jobs and steps; installed tools are checksum or digest verified, or supplied by a pinned action. App workflows start only on release tags [v*], the release candidate branches release/candidate-* (required in ci.yml: starci app release push waits for that run, owner ruling candidate-ci 2026-10-18), workflow_call or workflow_dispatch; ci.yml also runs on main and on pull_request to main (read-only workflow permissions, no environment bound in the file), and other branch pushes are refused. A release deploys through the reusable stack-deploy.yml (ruling app-cicd-auto-deploy): the job of ci.yml that calls it (deploy-<env>, after the verdict job) holds permissions, concurrency and with.environment, the called deploy job binds the GitHub Environment (deployment refs restricted to v* tags) and reads SOPS_AGE_KEY there, and the transport is the sealed member vps-ci opened with that key, so the CI deploy key, the host and the pinned host keys are never GitHub secrets, workflow text or log lines; STARCI_DEPLOY_PAUSED on the environment stops the automatic deploy. The secrets allowlist and the dotenv ban are judged on the deployment jobs, not on the check jobs beside them."
|
|
4207
|
+
law: "In lite and full apps, deployment jobs declare a protected environment, explicit permissions and concurrency, materialize sealed secrets through SOPS_AGE_KEY or starci app secret materialize, and reference only the age key and transport SSH key/known_hosts secrets; every job that reads secrets.SOPS_AGE_KEY, a deployment job or not, is bound to the GitHub Environment whose members it opens, so it reads that environment's server key and never a repository secret of that name. Deployment jobs never embed a dotenv blob or write a dotenv file. Every remote workflow action uses a 40-hex commit SHA (local actions are allowed and container actions require a full sha256 digest); supply-chain reports each unpinned uses reference at its source line, including disabled jobs and steps; installed tools are checksum or digest verified, or supplied by a pinned action. App workflows start only on release tags [v*], the release candidate branches release/candidate-* (required in ci.yml: starci app release push waits for that run, owner ruling candidate-ci 2026-10-18), workflow_call or workflow_dispatch, and the managed nightly verify of the check cache (cache-verify.yml) on its schedule; ci.yml also runs on main and on pull_request to main (read-only workflow permissions, no environment bound in the file), and other branch pushes are refused. A release deploys through the reusable stack-deploy.yml (ruling app-cicd-auto-deploy): the job of ci.yml that calls it (deploy-<env>, after the verdict job) holds permissions, concurrency and with.environment, the called deploy job binds the GitHub Environment (deployment refs restricted to v* tags) and reads SOPS_AGE_KEY there, and the transport is the sealed member vps-ci opened with that key, so the CI deploy key, the host and the pinned host keys are never GitHub secrets, workflow text or log lines; STARCI_DEPLOY_PAUSED on the environment stops the automatic deploy. The secrets allowlist and the dotenv ban are judged on the deployment jobs, not on the check jobs beside them."
|
|
4208
4208
|
kinds: [check]
|
|
4209
4209
|
gates: [settle, land, ci]
|
|
4210
4210
|
failureCodes: ["HFS_DEPLOY_WORKFLOW", "HFS_WORKFLOW_PIN", "HFS_CI_TOOL_INSTALL", "HFS_APP_WORKFLOW_TRIGGER"]
|
|
@@ -4631,7 +4631,7 @@ rules:
|
|
|
4631
4631
|
- {path: packages/hfs/src/hfs-release-provenance.spec.mjs, edition: full}
|
|
4632
4632
|
- id: R272
|
|
4633
4633
|
code: "BE_APP_BOOT_PROOF_MISSING"
|
|
4634
|
-
law: "Every lite back-end app proves its real Nest AppModule composition by compiling the dependency graph with explicit fixture options and infrastructure doubles; unresolved providers, circular dependencies and a missing or failed proof are refused. The proof worker runs within its own budget from its spawn and is retried once when it runs out; a second timeout reaches no verdict and is reported as BOOT_PROOF_TIMEOUT, a warning, never as a failed proof. The app check wiring verb uses the same proof. Full retains its existing e2e boot proof."
|
|
4634
|
+
law: "Every lite back-end app proves its real Nest AppModule composition by compiling the dependency graph with explicit fixture options and infrastructure doubles; unresolved providers, circular dependencies and a missing or failed proof are refused. The proof worker runs within its own budget from its spawn and is retried once when it runs out; a second timeout reaches no verdict and is reported as BOOT_PROOF_TIMEOUT, a warning, never as a failed proof. The app check wiring verb uses the same proof, and the fast job of the lite app CI runs it (`starci app check --gate wiring`), so a provider a domain module needs and the app root does not compose never passes tsc and the unit suite to fail at boot. Full retains its existing e2e boot proof."
|
|
4635
4635
|
kinds: [check]
|
|
4636
4636
|
gates: ["settle","land","ci"]
|
|
4637
4637
|
failureCodes: ["BE_APP_BOOT_PROOF_MISSING", "BOOT_PROOF_TIMEOUT"]
|
|
@@ -6039,18 +6039,24 @@ rules:
|
|
|
6039
6039
|
code: "HFS_CHECK_CACHE_FORGED"
|
|
6040
6040
|
editions: ["lite", "full"]
|
|
6041
6041
|
docs: [contexts/hfs/README.md#rule-notes]
|
|
6042
|
-
law: "An app's committed check cache (.starcistacks/cache/) is trusted in CI only as it stands at the trusted base; a record whose key matches the tree and whose findings differ from the inherited or computed result is HFS_CHECK_CACHE_FORGED (a hard blocker at any count), a touched key without a current record is HFS_CHECK_CACHE_STALE and a missing cache is HFS_CHECK_CACHE_MISSING (both report-only warnings)."
|
|
6042
|
+
law: "An app's committed check cache (.starcistacks/cache/) is trusted in CI only as it stands at the trusted base; a record whose key matches the tree and whose findings differ from the inherited or computed result is HFS_CHECK_CACHE_FORGED (a hard blocker at any count), a touched key without a current record is HFS_CHECK_CACHE_STALE and a missing cache is HFS_CHECK_CACHE_MISSING (both report-only warnings in CI); every push carries the warm cache a real run on its tree writes, refused at the pre-push hook as HFS_CHECK_CACHE_UNWARMED (a cache that run had to change, or uncommitted cache files) or HFS_CHECK_CACHE_UNPORTABLE (a host whose fingerprint is not portable); and the release gate, which trusts the warm cache, is refused HFS_CHECK_CACHE_VERIFY_LOCKED while the newest nightly verify of the default branch is red or cannot be read."
|
|
6043
6043
|
kinds: [codemod]
|
|
6044
6044
|
gates: [ci]
|
|
6045
|
-
failureCodes: ["HFS_CHECK_CACHE_FORGED", "HFS_CHECK_CACHE_STALE", "HFS_CHECK_CACHE_MISSING"]
|
|
6045
|
+
failureCodes: ["HFS_CHECK_CACHE_FORGED", "HFS_CHECK_CACHE_STALE", "HFS_CHECK_CACHE_MISSING", "HFS_CHECK_CACHE_UNWARMED", "HFS_CHECK_CACHE_UNPORTABLE", "HFS_CHECK_CACHE_VERIFY_LOCKED"]
|
|
6046
6046
|
enforcers:
|
|
6047
6047
|
- {kind: hfs, id: check-cache, at: packages/hfs/cache/trust.mjs}
|
|
6048
|
+
- {kind: hfs, id: check-cache-fresh, at: packages/hfs/cache/freshness.mjs}
|
|
6049
|
+
- {kind: hfs, id: release-cache-verify-lock, at: packages/hfs/release/cache-verify-lock.mjs}
|
|
6048
6050
|
proves:
|
|
6049
6051
|
- {path: packages/hfs/src/hfs-check-cache.spec.mjs, editions: [lite, full]}
|
|
6052
|
+
- {path: packages/hfs/src/check-cache-freshness.spec.mjs, editions: [lite, full]}
|
|
6053
|
+
- {path: packages/hfs/src/release-cache-verify-lock.spec.mjs, editions: [lite, full]}
|
|
6050
6054
|
exemplifiedBy:
|
|
6051
6055
|
- {path: packages/hfs/src/hfs-check-cache.spec.mjs, editions: [lite, full]}
|
|
6052
6056
|
witness:
|
|
6053
6057
|
- {path: packages/hfs/src/hfs-check-cache.spec.mjs, editions: [lite, full], codes: [HFS_CHECK_CACHE_FORGED, HFS_CHECK_CACHE_STALE, HFS_CHECK_CACHE_MISSING]}
|
|
6058
|
+
- {path: packages/hfs/src/check-cache-freshness.spec.mjs, editions: [lite, full], codes: [HFS_CHECK_CACHE_UNWARMED, HFS_CHECK_CACHE_UNPORTABLE]}
|
|
6059
|
+
- {path: packages/hfs/src/release-cache-verify-lock.spec.mjs, editions: [lite, full], codes: [HFS_CHECK_CACHE_VERIFY_LOCKED]}
|
|
6054
6060
|
cases:
|
|
6055
6061
|
- id: case-1
|
|
6056
6062
|
date: "2026-10-31"
|
|
@@ -6641,3 +6647,18 @@ rules:
|
|
|
6641
6647
|
- {path: contexts/project/stacks.md#project-stacks-12-seed-data-lives-in-the-seed-levels-of-the-stack, editions: [lite, full]}
|
|
6642
6648
|
proves:
|
|
6643
6649
|
- {path: packages/hfs/src/hfs-seeds-shape.spec.mjs, editions: [lite, full]}
|
|
6650
|
+
- id: R376
|
|
6651
|
+
code: "HFS_BOOT_LOGGER_SILENCED"
|
|
6652
|
+
law: "A back-end app root boots loudly: its `be/apps/<app>/src/main.ts` never hands Nest `logger: false` (NestFactory or nest-commander's CommandFactory), so a provider a module needs and the root does not compose, or any other bootstrap failure, is printed on stderr and exits non-zero instead of ending every boot or CLI command silently; the main passes the app's logger and an error handler that prints and exits non-zero."
|
|
6653
|
+
kinds: [check]
|
|
6654
|
+
gates: [settle, land, ci]
|
|
6655
|
+
failureCodes: ["HFS_BOOT_LOGGER_SILENCED"]
|
|
6656
|
+
enforcers:
|
|
6657
|
+
- {kind: hfs, id: boot-logger, at: scripts/hfs/rules/boot-logger.mjs}
|
|
6658
|
+
editions: [lite, full]
|
|
6659
|
+
proves:
|
|
6660
|
+
- {path: packages/hfs/src/hfs-boot-logger.spec.mjs, editions: [lite, full]}
|
|
6661
|
+
exemplifiedBy:
|
|
6662
|
+
- {path: packages/hfs/templates/be/skeleton/apps/cli/src/main.ts, editions: [lite, full]}
|
|
6663
|
+
witness:
|
|
6664
|
+
- {path: packages/hfs/src/hfs-boot-logger.spec.mjs, editions: [lite, full]}
|