@cat-factory/contracts 0.274.0 → 0.276.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.
Files changed (57) hide show
  1. package/dist/accountSettings.d.ts +156 -22
  2. package/dist/accountSettings.d.ts.map +1 -1
  3. package/dist/accountSettings.js +48 -5
  4. package/dist/accountSettings.js.map +1 -1
  5. package/dist/errors.d.ts +16 -1
  6. package/dist/errors.d.ts.map +1 -1
  7. package/dist/errors.js +16 -0
  8. package/dist/errors.js.map +1 -1
  9. package/dist/index.d.ts +2 -1
  10. package/dist/index.d.ts.map +1 -1
  11. package/dist/index.js +2 -1
  12. package/dist/index.js.map +1 -1
  13. package/dist/notification-routing.d.ts +100 -0
  14. package/dist/notification-routing.d.ts.map +1 -0
  15. package/dist/notification-routing.js +155 -0
  16. package/dist/notification-routing.js.map +1 -0
  17. package/dist/public-api.d.ts +137 -0
  18. package/dist/public-api.d.ts.map +1 -1
  19. package/dist/public-api.js +74 -0
  20. package/dist/public-api.js.map +1 -1
  21. package/dist/public-board.d.ts +276 -0
  22. package/dist/public-board.d.ts.map +1 -0
  23. package/dist/public-board.js +215 -0
  24. package/dist/public-board.js.map +1 -0
  25. package/dist/public-evidence.d.ts +30 -3
  26. package/dist/public-evidence.d.ts.map +1 -1
  27. package/dist/public-evidence.js +27 -3
  28. package/dist/public-evidence.js.map +1 -1
  29. package/dist/requests.d.ts +19 -2
  30. package/dist/requests.d.ts.map +1 -1
  31. package/dist/requests.js +18 -1
  32. package/dist/requests.js.map +1 -1
  33. package/dist/routes/accounts.d.ts +81 -15
  34. package/dist/routes/accounts.d.ts.map +1 -1
  35. package/dist/routes/board.d.ts +6 -2
  36. package/dist/routes/board.d.ts.map +1 -1
  37. package/dist/routes/index.d.ts +1 -0
  38. package/dist/routes/index.d.ts.map +1 -1
  39. package/dist/routes/index.js +1 -0
  40. package/dist/routes/index.js.map +1 -1
  41. package/dist/routes/notifications.d.ts +76 -0
  42. package/dist/routes/notifications.d.ts.map +1 -1
  43. package/dist/routes/notifications.js +15 -0
  44. package/dist/routes/notifications.js.map +1 -1
  45. package/dist/routes/public-api.d.ts +18 -0
  46. package/dist/routes/public-api.d.ts.map +1 -1
  47. package/dist/routes/public-board.d.ts +369 -0
  48. package/dist/routes/public-board.d.ts.map +1 -0
  49. package/dist/routes/public-board.js +112 -0
  50. package/dist/routes/public-board.js.map +1 -0
  51. package/dist/routes/public-evidence.d.ts +1 -0
  52. package/dist/routes/public-evidence.d.ts.map +1 -1
  53. package/package.json +1 -1
  54. package/dist/gate-parking.d.ts +0 -30
  55. package/dist/gate-parking.d.ts.map +0 -1
  56. package/dist/gate-parking.js +0 -58
  57. package/dist/gate-parking.js.map +0 -1
@@ -1,30 +0,0 @@
1
- /**
2
- * Built-in gate kinds whose poll never times out because they are waiting on a HUMAN, so a step
3
- * carrying one can park the run indefinitely.
4
- *
5
- * Membership is equivalent to the gate's `pollExhaustion: 'rearm'` declaration, and
6
- * `@cat-factory/gates`' `human-wait-parity.test.ts` fails the build if the two ever disagree: a new
7
- * built-in gate that waits on a human cannot ship without being classified here.
8
- *
9
- * Only BUILT-IN gates are covered. A deployment that registers its own unbounded-wait gate is not
10
- * seen by the static rule (reading a registered gate's `pollExhaustion` means invoking its factory
11
- * with an engine context, which a request-time admission check has no business doing), so the run
12
- * is admitted and the park is answered in the app. Stated rather than silently assumed: see
13
- * ADR 0032.
14
- */
15
- export declare const HUMAN_WAIT_GATE_KINDS: ReadonlySet<string>;
16
- /**
17
- * Every gate kind the platform itself ships, human-wait and bounded alike.
18
- *
19
- * What it is FOR is the negative: a gate step whose kind is NOT in here was registered by the
20
- * DEPLOYMENT through the public `GateRegistry` seam, and the note above is why nothing outside
21
- * `@cat-factory/gates` can then say whether it ever ends on its own. That is a fact worth
22
- * REPORTING rather than one to silently assume either way — a run sitting on such a gate with an
23
- * empty public decision list is either mid-probe or waiting on a person forever, and only the
24
- * deployment that registered it knows which.
25
- *
26
- * Pinned by the same drift guard as {@link HUMAN_WAIT_GATE_KINDS}, derived from the built-in
27
- * registry, so a new built-in cannot ship without landing here.
28
- */
29
- export declare const BUILTIN_GATE_KINDS: ReadonlySet<string>;
30
- //# sourceMappingURL=gate-parking.d.ts.map
@@ -1 +0,0 @@
1
- {"version":3,"file":"gate-parking.d.ts","sourceRoot":"","sources":["../src/gate-parking.ts"],"names":[],"mappings":"AAmBA;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,qBAAqB,EAAE,WAAW,CAAC,MAAM,CAIpD,CAAA;AAEF;;;;;;;;;;;;GAYG;AACH,eAAO,MAAM,kBAAkB,EAAE,WAAW,CAAC,MAAM,CAMjD,CAAA"}
@@ -1,58 +0,0 @@
1
- // Which polling-GATE kinds park the run on a human, and are therefore a static park surface a
2
- // start path can refuse on.
3
- //
4
- // A gate is normally the opposite of a park: it probes a provider, escalates to a helper agent on a
5
- // negative verdict, and settles itself. One gate kind is different. `human-review` declares
6
- // `pollExhaustion: 'rearm'` with an effectively unbounded attempt budget, which is the engine's way
7
- // of saying "there is no deadline for a human reviewer": running out of polls is not a verdict, so
8
- // the step re-arms and the run waits indefinitely for a person on the PR.
9
- //
10
- // That makes it a human park in exactly the sense the public API's admission rule cares about, and
11
- // it is STATIC: the kind sits in the pipeline's step chain at save time, unlike an agent-raised
12
- // decision or a judge `park` disposition, which only exist once a run is under way.
13
- //
14
- // This lives in `contracts` rather than beside either consumer because the two packages that must
15
- // agree cannot see each other: `@cat-factory/server`'s public-API admission reads it, and
16
- // `@cat-factory/gates` (which owns the gate definitions and therefore the `pollExhaustion` values)
17
- // pins it with a drift guard. A shared constant is the only shape in which those two cannot
18
- // disagree. The same reasoning as `BUILTIN_GATABLE_KINDS` in `agent-gating.ts`.
19
- /**
20
- * Built-in gate kinds whose poll never times out because they are waiting on a HUMAN, so a step
21
- * carrying one can park the run indefinitely.
22
- *
23
- * Membership is equivalent to the gate's `pollExhaustion: 'rearm'` declaration, and
24
- * `@cat-factory/gates`' `human-wait-parity.test.ts` fails the build if the two ever disagree: a new
25
- * built-in gate that waits on a human cannot ship without being classified here.
26
- *
27
- * Only BUILT-IN gates are covered. A deployment that registers its own unbounded-wait gate is not
28
- * seen by the static rule (reading a registered gate's `pollExhaustion` means invoking its factory
29
- * with an engine context, which a request-time admission check has no business doing), so the run
30
- * is admitted and the park is answered in the app. Stated rather than silently assumed: see
31
- * ADR 0032.
32
- */
33
- export const HUMAN_WAIT_GATE_KINDS = new Set([
34
- // Waits for a real human code review on the PR. `pollExhaustion: 'rearm'`, an effectively
35
- // infinite attempt budget, and a notification (not a timeout) as the nudge.
36
- 'human-review',
37
- ]);
38
- /**
39
- * Every gate kind the platform itself ships, human-wait and bounded alike.
40
- *
41
- * What it is FOR is the negative: a gate step whose kind is NOT in here was registered by the
42
- * DEPLOYMENT through the public `GateRegistry` seam, and the note above is why nothing outside
43
- * `@cat-factory/gates` can then say whether it ever ends on its own. That is a fact worth
44
- * REPORTING rather than one to silently assume either way — a run sitting on such a gate with an
45
- * empty public decision list is either mid-probe or waiting on a person forever, and only the
46
- * deployment that registered it knows which.
47
- *
48
- * Pinned by the same drift guard as {@link HUMAN_WAIT_GATE_KINDS}, derived from the built-in
49
- * registry, so a new built-in cannot ship without landing here.
50
- */
51
- export const BUILTIN_GATE_KINDS = new Set([
52
- 'ci',
53
- 'conflicts',
54
- 'post-release-health',
55
- 'human-review',
56
- 'doc-quality',
57
- ]);
58
- //# sourceMappingURL=gate-parking.js.map
@@ -1 +0,0 @@
1
- {"version":3,"file":"gate-parking.js","sourceRoot":"","sources":["../src/gate-parking.ts"],"names":[],"mappings":"AAAA,8FAA8F;AAC9F,4BAA4B;AAC5B,EAAE;AACF,oGAAoG;AACpG,4FAA4F;AAC5F,oGAAoG;AACpG,mGAAmG;AACnG,0EAA0E;AAC1E,EAAE;AACF,mGAAmG;AACnG,gGAAgG;AAChG,oFAAoF;AACpF,EAAE;AACF,kGAAkG;AAClG,0FAA0F;AAC1F,mGAAmG;AACnG,4FAA4F;AAC5F,gFAAgF;AAEhF;;;;;;;;;;;;;GAaG;AACH,MAAM,CAAC,MAAM,qBAAqB,GAAwB,IAAI,GAAG,CAAS;IACxE,0FAA0F;IAC1F,4EAA4E;IAC5E,cAAc;CACf,CAAC,CAAA;AAEF;;;;;;;;;;;;GAYG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAwB,IAAI,GAAG,CAAS;IACrE,IAAI;IACJ,WAAW;IACX,qBAAqB;IACrB,cAAc;IACd,aAAa;CACd,CAAC,CAAA"}