@egox/contracts 0.5.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/LICENSE ADDED
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or Derivative
95
+ Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright 2025 EgoX
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
package/NOTICE ADDED
@@ -0,0 +1,10 @@
1
+ EgoX Contracts (@egox/contracts)
2
+ Copyright 2025 EgoX
3
+
4
+ This product includes software developed by EgoX.
5
+
6
+ Licensed under the Apache License, Version 2.0 (the "License");
7
+ you may not use this file except in compliance with the License.
8
+ You may obtain a copy of the License at
9
+
10
+ http://www.apache.org/licenses/LICENSE-2.0
package/README.md ADDED
@@ -0,0 +1,87 @@
1
+ # @egox/contracts
2
+
3
+ Wire-format TypeScript contracts shared by every EgoX surface — backend,
4
+ SDK (`@egox/client`), MCP server, and console. **Types only**, no runtime
5
+ exports. Published to npm as [`@egox/contracts`](https://www.npmjs.com/package/@egox/contracts) so every surface can pin the same version.
6
+
7
+ ## Why this exists
8
+
9
+ The `answer === undefined` bug in `@egox/client@1.1.0` was caused by the
10
+ SDK's response decoder reading `data.response` while the backend was
11
+ writing `data.answer`. Two parallel hand-maintained interface sets in two
12
+ packages, drifting silently — exactly the failure mode this package is
13
+ designed to make impossible.
14
+
15
+ Anything that crosses the network between EgoX components is declared
16
+ here once. Backend response builders and SDK decoders both reference the
17
+ same `AskResponseData` interface, so a field rename is a one-edit change
18
+ that the TypeScript compiler enforces across the stack.
19
+
20
+ ## Why types-only
21
+
22
+ `import type { … } from '@egox/contracts'` is fully erased by `tsc` /
23
+ `tsup`. That means:
24
+
25
+ - **Zero runtime cost.** No JS file is ever required. End users of
26
+ `@egox/client` see no `@egox/contracts` in their `node_modules`.
27
+ - **No path-alias-at-runtime headaches.** Path resolution only matters at
28
+ compile time; `dist` output has no leftover references.
29
+ - **No publish.** This package is `private: true` and is consumed via
30
+ tsconfig `paths` only.
31
+
32
+ If you need a runtime constant (e.g. `SDK_RESERVED_HEADERS`,
33
+ `HEADER_FORWARD_BLOCKLIST`), keep it in the package that actually uses it
34
+ and add a `// must mirror @egox/contracts` comment if it shadows a contract.
35
+
36
+ ## How to consume it
37
+
38
+ In any package that needs the wire types, add to its `tsconfig.json`:
39
+
40
+ ```json
41
+ {
42
+ "compilerOptions": {
43
+ "paths": {
44
+ "@egox/contracts": ["../egox-contracts/src"]
45
+ }
46
+ }
47
+ }
48
+ ```
49
+
50
+ Adjust the relative path if the package isn't a sibling of `egox-contracts/`.
51
+ Then in code:
52
+
53
+ ```ts
54
+ import type { AskRequestBody, AskResponseData, AskStreamEvent } from '@egox/contracts';
55
+ ```
56
+
57
+ `tsup`-built packages (`@egox/client`) inline the imported types into
58
+ their generated `.d.ts` automatically — end users see the types as if
59
+ they were declared in the SDK itself.
60
+
61
+ ## When to bump
62
+
63
+ - **Adding** an optional field — non-breaking, no version bump required
64
+ (still good practice to bump the minor).
65
+ - **Renaming or removing** a field — breaking, bump major **and** ship a
66
+ coordinated update of backend + SDK + MCP in one release.
67
+ - **Adding** a new SSE event variant to `AskStreamEvent` — non-breaking
68
+ for producers (backend just starts emitting it), breaking for consumers
69
+ who exhaustively switch on `event.type` and rely on `never` checks. Bump
70
+ the minor and call it out in the release notes.
71
+
72
+ ## What's in scope today
73
+
74
+ - `EgoxApiResponse<T>` envelope
75
+ - `/ask` request + response (`AskRequestBody`, `AskResponseData`)
76
+ - `/ask/stream` request + full SSE event union
77
+ - Common building blocks: `Intent`, `ResponseFormat`, `TokenUsage`,
78
+ `JsonSchemaDefinition`
79
+
80
+ What's **not** in scope yet (planned, see TODOs in each module):
81
+
82
+ - Tool CRUD wire shapes (`/tools/*`)
83
+ - RAG document wire shapes (`/rag/*`)
84
+ - API key / MCP token wire shapes (`/api-keys/*`, `/mcp-tokens/*`)
85
+ - Tenant / project wire shapes
86
+
87
+ These will be migrated incrementally as we touch them.
package/package.json ADDED
@@ -0,0 +1,46 @@
1
+ {
2
+ "name": "@egox/contracts",
3
+ "version": "0.5.0",
4
+ "description": "Wire-format type contracts shared between EgoX backend, SDK, MCP and console. Type-only — no runtime artifacts.",
5
+ "types": "./src/index.d.ts",
6
+ "exports": {
7
+ ".": {
8
+ "types": "./src/index.d.ts"
9
+ }
10
+ },
11
+ "files": [
12
+ "src",
13
+ "README.md",
14
+ "LICENSE",
15
+ "NOTICE"
16
+ ],
17
+ "scripts": {
18
+ "typecheck": "tsc --noEmit"
19
+ },
20
+ "keywords": [
21
+ "egox",
22
+ "contracts",
23
+ "types",
24
+ "typescript",
25
+ "wire-format"
26
+ ],
27
+ "repository": {
28
+ "type": "git",
29
+ "url": "https://github.com/egox-io/contracts.git"
30
+ },
31
+ "homepage": "https://github.com/egox-io/contracts#readme",
32
+ "bugs": {
33
+ "url": "https://github.com/egox-io/contracts/issues"
34
+ },
35
+ "author": "EgoX Team",
36
+ "license": "Apache-2.0",
37
+ "publishConfig": {
38
+ "access": "public"
39
+ },
40
+ "engines": {
41
+ "node": ">=18.0.0"
42
+ },
43
+ "devDependencies": {
44
+ "typescript": "^5.0.0"
45
+ }
46
+ }
@@ -0,0 +1,155 @@
1
+ /**
2
+ * @egox/contracts — `/egox/tenants/:tenantId/api-keys/*` wire types.
3
+ *
4
+ * Per-project API keys (the `egox_live_*` / `egox_test_*` credentials
5
+ * the SDK and any service calling the public `/ask` API present as
6
+ * `Authorization: Bearer <key>`).
7
+ *
8
+ * Drift cleaned up here:
9
+ * - Backend's `ApiKeyInfo` used `Date` for `expiresAt` / `lastUsedAt`
10
+ * / `createdAt`; the wire (and the Console mirror) already used
11
+ * ISO strings. Backend now matches via `formatKeyInfo` + ISO emit.
12
+ * - The console hand-maintained an `ApiKeyScope` union that mirrored
13
+ * the backend's `API_KEY_SCOPES` constant. The union now lives here
14
+ * once and both surfaces re-export.
15
+ */
16
+
17
+ // ============================================================================
18
+ // Locked vocabularies
19
+ // ============================================================================
20
+
21
+ /**
22
+ * Scopes a per-project API key can hold. Mirrors `API_KEY_SCOPES` in
23
+ * `backend/egox/modules/tenant-api-key/constants.ts` — adding a new
24
+ * scope is a one-edit change here (plus the backend constant) and
25
+ * propagates to console + SDK at compile time.
26
+ *
27
+ * - `'ask'` — call the `/ask` and `/ask/stream` endpoints.
28
+ * - `'rag:read'` — read knowledge-base documents.
29
+ * - `'rag:write'` — create / update / delete KB documents.
30
+ * - `'tools:read'` — read tool definitions.
31
+ * - `'tools:write'` — create / update / delete tools.
32
+ * - `'threads:read'` — read conversation threads.
33
+ * - `'admin'` — full access (implies every scope above).
34
+ */
35
+ export type ApiKeyScope =
36
+ | 'ask'
37
+ | 'rag:read'
38
+ | 'rag:write'
39
+ | 'tools:read'
40
+ | 'tools:write'
41
+ | 'threads:read'
42
+ | 'admin';
43
+
44
+ // ============================================================================
45
+ // ApiKeyWire — the canonical row shape (no secrets)
46
+ // ============================================================================
47
+
48
+ /**
49
+ * Public-facing API key info. Returned by every
50
+ * `GET /egox/tenants/:tenantId/api-keys` and
51
+ * `GET /egox/tenants/:tenantId/api-keys/:keyId` response.
52
+ *
53
+ * Carries NO secret material — only the hashed-prefix display value.
54
+ * The raw key is exposed exactly once on create / rotate via
55
+ * `ApiKeyCreatedWire`; there is no endpoint that returns it again.
56
+ *
57
+ * Timestamps are ISO 8601 strings (backend's `formatKeyInfo` emits
58
+ * ISO to match the wire — verified by re-anchor in Phase 9.3).
59
+ */
60
+ export interface ApiKeyWire {
61
+ id: string;
62
+ tenantId: string;
63
+ name: string;
64
+ /**
65
+ * Public-display prefix of the raw key (the part the SDK shows in
66
+ * connection-test errors, e.g. `egox_live_abc12345`). Safe to log;
67
+ * the full key is unrecoverable from this value.
68
+ */
69
+ keyPrefix: string;
70
+ scopes: ApiKeyScope[];
71
+ expiresAt: string | null;
72
+ isActive: boolean;
73
+ /**
74
+ * Server-computed convenience flag: `true` when `expiresAt` is in
75
+ * the past. Saves consumers from re-implementing the comparison
76
+ * (and from forgetting timezone handling on it).
77
+ */
78
+ isExpired: boolean;
79
+ lastUsedAt: string | null;
80
+ /**
81
+ * Total successful authentications using this key. Denormalised
82
+ * counter, updated by the auth middleware on every accepted
83
+ * request.
84
+ */
85
+ usageCount: number;
86
+ createdAt: string;
87
+ }
88
+
89
+ /**
90
+ * Returned exactly once at creation / rotation. The raw `apiKey`
91
+ * string is unrecoverable afterwards — only the SHA-256 hash and
92
+ * prefix are persisted server-side. Consumers MUST surface the value
93
+ * to the human operator immediately and clear it from memory after
94
+ * confirmation.
95
+ */
96
+ export interface ApiKeyCreatedWire {
97
+ /** Raw key — show once, then forget. */
98
+ apiKey: string;
99
+ keyId: string;
100
+ keyPrefix: string;
101
+ name: string;
102
+ scopes: ApiKeyScope[];
103
+ expiresAt: string | null;
104
+ createdAt: string;
105
+ }
106
+
107
+ // ============================================================================
108
+ // Request bodies (what the client SENDS)
109
+ // ============================================================================
110
+
111
+ /**
112
+ * Wire body of `POST /egox/tenants/:tenantId/api-keys`. `tenantId`
113
+ * is the URL param, not the body.
114
+ */
115
+ export interface ApiKeyCreateBody {
116
+ name: string;
117
+ scopes?: ApiKeyScope[];
118
+ /**
119
+ * Optional TTL in days. Omit (or `undefined`) for never-expiring.
120
+ * Server caps at `MAX_EXPIRY_DAYS` from
121
+ * `backend/egox/modules/tenant-api-key/constants.ts`.
122
+ */
123
+ expiresInDays?: number;
124
+ }
125
+
126
+ /**
127
+ * Wire body of `POST /egox/tenants/:tenantId/api-keys/:keyId/rotate`.
128
+ * Rotation generates a new raw key (returned in `ApiKeyCreatedWire`)
129
+ * and revokes the old one. The `name` defaults to the old key's name.
130
+ */
131
+ export interface ApiKeyRotateBody {
132
+ name?: string;
133
+ }
134
+
135
+ // ============================================================================
136
+ // Response data shapes (carried inside `EgoxApiResponse.data`)
137
+ // ============================================================================
138
+
139
+ export interface ApiKeyListResponseData {
140
+ keys: ApiKeyWire[];
141
+ }
142
+
143
+ export interface ApiKeyGetResponseData {
144
+ key: ApiKeyWire;
145
+ }
146
+
147
+ /**
148
+ * Returned by both `POST /egox/tenants/:tenantId/api-keys` (create)
149
+ * and `POST /egox/tenants/:tenantId/api-keys/:keyId/rotate`. Wraps
150
+ * `ApiKeyCreatedWire` so the response data shape is consistent with
151
+ * `ApiKeyGetResponseData` / `ApiKeyListResponseData`.
152
+ */
153
+ export interface ApiKeyCreatedResponseData {
154
+ key: ApiKeyCreatedWire;
155
+ }