@praxisflux/gates 0.19.0 → 0.20.0
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 +8 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -5,9 +5,15 @@ carry praxisflux itself. There are two enforcement points, deliberately split th
|
|
|
5
5
|
splits them for its own development:
|
|
6
6
|
|
|
7
7
|
- **Locally / interactively**: the installed plugins' Stop hooks run the gates as you work.
|
|
8
|
-
These float with plugin updates and are advisory
|
|
8
|
+
These float with plugin updates and are **advisory and opt-in by design** — they exist
|
|
9
|
+
only where a plugin is installed, and they never block over a missing runtime (a `gate.sh`
|
|
10
|
+
that can't find `node` notices once on stderr, then no-ops).
|
|
9
11
|
- **In CI**: the composite GitHub Action runs the same gates at a **pinned release**. CI is
|
|
10
|
-
authoritative
|
|
12
|
+
**authoritative**. Pin drift between local and CI is fine by design.
|
|
13
|
+
|
|
14
|
+
The tenet this split delivers: **gates make dishonest status expensive locally and
|
|
15
|
+
impossible in CI.** Local hooks raise the cost of overstating what's proven while you work;
|
|
16
|
+
the CI surface below is where an overstated status actually cannot land.
|
|
11
17
|
|
|
12
18
|
## The action
|
|
13
19
|
|
package/package.json
CHANGED