@theholocron/cli 5.0.0-alpha.17 → 5.0.0-alpha.19
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/README.md +16 -0
- package/dist/cli.mjs.map +1 -1
- package/dist/index.d.mts +78 -1
- package/dist/index.mjs +109 -2
- package/package.json +6 -6
package/README.md
CHANGED
|
@@ -142,6 +142,22 @@ Field definitions and derivation heuristics:
|
|
|
142
142
|
`.notes/tech-holocron-platform.spec.md` → "Custom-properties sync — field
|
|
143
143
|
definitions (#677)".
|
|
144
144
|
|
|
145
|
+
The four derived fields' pure computation —
|
|
146
|
+
`deriveProfile()`/`deriveStack()`/`deriveCapabilities()`/`deriveCompliance()`
|
|
147
|
+
(plus their `HolocronProfile`/`DeriveProfileInput`/`PackageJsonLike` types)
|
|
148
|
+
— is exported from this package's public entry point, separate from the
|
|
149
|
+
local-filesystem reads (`readWorkspacePackageJsons()`) that gather their
|
|
150
|
+
inputs here. `@theholocron/sentinel`'s `syncPropertiesFromConfig()` reuses
|
|
151
|
+
these functions unchanged, gathering the same inputs over the GitHub API
|
|
152
|
+
instead (D8 — one derivation, two input sources, not two
|
|
153
|
+
implementations).
|
|
154
|
+
|
|
155
|
+
`missingCapabilities(capabilities)` is `deriveCompliance()`'s sibling —
|
|
156
|
+
same `REQUIRED_BASELINE` table, but returns _which_ required capabilities
|
|
157
|
+
are absent rather than whether any are. `@theholocron/sentinel`'s
|
|
158
|
+
`postCheckRun()` uses it to name what's missing on the check run it
|
|
159
|
+
posts, instead of reporting pass/fail.
|
|
160
|
+
|
|
145
161
|
### Required status checks (`protection: "strict"`)
|
|
146
162
|
|
|
147
163
|
`holocron setup` builds the branch-protection required-check list from the
|