@indigoai-us/hq-cloud 6.16.20 → 6.16.21

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 (110) hide show
  1. package/dist/bin/sync-runner-installation-id.d.ts +66 -0
  2. package/dist/bin/sync-runner-installation-id.d.ts.map +1 -0
  3. package/dist/bin/sync-runner-installation-id.js +138 -0
  4. package/dist/bin/sync-runner-installation-id.js.map +1 -0
  5. package/dist/bin/sync-runner-manifest.d.ts +120 -0
  6. package/dist/bin/sync-runner-manifest.d.ts.map +1 -0
  7. package/dist/bin/sync-runner-manifest.js +348 -0
  8. package/dist/bin/sync-runner-manifest.js.map +1 -0
  9. package/dist/bin/sync-runner-manifest.test.d.ts +12 -0
  10. package/dist/bin/sync-runner-manifest.test.d.ts.map +1 -0
  11. package/dist/bin/sync-runner-manifest.test.js +510 -0
  12. package/dist/bin/sync-runner-manifest.test.js.map +1 -0
  13. package/dist/bin/sync-runner.d.ts +55 -0
  14. package/dist/bin/sync-runner.d.ts.map +1 -1
  15. package/dist/bin/sync-runner.js +69 -0
  16. package/dist/bin/sync-runner.js.map +1 -1
  17. package/dist/bin/sync-runner.test.js +217 -0
  18. package/dist/bin/sync-runner.test.js.map +1 -1
  19. package/dist/company-slug.d.ts +31 -0
  20. package/dist/company-slug.d.ts.map +1 -0
  21. package/dist/company-slug.js +52 -0
  22. package/dist/company-slug.js.map +1 -0
  23. package/dist/company-slug.test.d.ts +7 -0
  24. package/dist/company-slug.test.d.ts.map +1 -0
  25. package/dist/company-slug.test.js +43 -0
  26. package/dist/company-slug.test.js.map +1 -0
  27. package/dist/index.d.ts +2 -0
  28. package/dist/index.d.ts.map +1 -1
  29. package/dist/index.js +5 -0
  30. package/dist/index.js.map +1 -1
  31. package/dist/journal-ledger-index.test.d.ts +15 -0
  32. package/dist/journal-ledger-index.test.d.ts.map +1 -0
  33. package/dist/journal-ledger-index.test.js +247 -0
  34. package/dist/journal-ledger-index.test.js.map +1 -0
  35. package/dist/journal.d.ts +110 -0
  36. package/dist/journal.d.ts.map +1 -1
  37. package/dist/journal.js +253 -5
  38. package/dist/journal.js.map +1 -1
  39. package/dist/manifest/US-002.acceptance.test.d.ts +11 -0
  40. package/dist/manifest/US-002.acceptance.test.d.ts.map +1 -0
  41. package/dist/manifest/US-002.acceptance.test.js +160 -0
  42. package/dist/manifest/US-002.acceptance.test.js.map +1 -0
  43. package/dist/manifest/US-004.acceptance.test.d.ts +12 -0
  44. package/dist/manifest/US-004.acceptance.test.d.ts.map +1 -0
  45. package/dist/manifest/US-004.acceptance.test.js +173 -0
  46. package/dist/manifest/US-004.acceptance.test.js.map +1 -0
  47. package/dist/manifest/build-manifest.bench.test.d.ts +22 -0
  48. package/dist/manifest/build-manifest.bench.test.d.ts.map +1 -0
  49. package/dist/manifest/build-manifest.bench.test.js +544 -0
  50. package/dist/manifest/build-manifest.bench.test.js.map +1 -0
  51. package/dist/manifest/build-manifest.d.ts +319 -0
  52. package/dist/manifest/build-manifest.d.ts.map +1 -0
  53. package/dist/manifest/build-manifest.js +1043 -0
  54. package/dist/manifest/build-manifest.js.map +1 -0
  55. package/dist/manifest/build-manifest.test.d.ts +10 -0
  56. package/dist/manifest/build-manifest.test.d.ts.map +1 -0
  57. package/dist/manifest/build-manifest.test.js +1060 -0
  58. package/dist/manifest/build-manifest.test.js.map +1 -0
  59. package/dist/manifest/contract.d.ts +290 -0
  60. package/dist/manifest/contract.d.ts.map +1 -0
  61. package/dist/manifest/contract.js +476 -0
  62. package/dist/manifest/contract.js.map +1 -0
  63. package/dist/manifest/contract.test.d.ts +17 -0
  64. package/dist/manifest/contract.test.d.ts.map +1 -0
  65. package/dist/manifest/contract.test.js +283 -0
  66. package/dist/manifest/contract.test.js.map +1 -0
  67. package/dist/manifest/import-graph.test.d.ts +25 -0
  68. package/dist/manifest/import-graph.test.d.ts.map +1 -0
  69. package/dist/manifest/import-graph.test.js +120 -0
  70. package/dist/manifest/import-graph.test.js.map +1 -0
  71. package/dist/manifest/ledger-shard-isolation.test.d.ts +18 -0
  72. package/dist/manifest/ledger-shard-isolation.test.d.ts.map +1 -0
  73. package/dist/manifest/ledger-shard-isolation.test.js +153 -0
  74. package/dist/manifest/ledger-shard-isolation.test.js.map +1 -0
  75. package/dist/manifest/snapshot-store.d.ts +143 -0
  76. package/dist/manifest/snapshot-store.d.ts.map +1 -0
  77. package/dist/manifest/snapshot-store.js +291 -0
  78. package/dist/manifest/snapshot-store.js.map +1 -0
  79. package/dist/manifest/snapshot-store.test.d.ts +11 -0
  80. package/dist/manifest/snapshot-store.test.d.ts.map +1 -0
  81. package/dist/manifest/snapshot-store.test.js +133 -0
  82. package/dist/manifest/snapshot-store.test.js.map +1 -0
  83. package/dist/manifest/upload-manifest.d.ts +301 -0
  84. package/dist/manifest/upload-manifest.d.ts.map +1 -0
  85. package/dist/manifest/upload-manifest.js +921 -0
  86. package/dist/manifest/upload-manifest.js.map +1 -0
  87. package/dist/manifest/upload-manifest.test.d.ts +10 -0
  88. package/dist/manifest/upload-manifest.test.d.ts.map +1 -0
  89. package/dist/manifest/upload-manifest.test.js +1052 -0
  90. package/dist/manifest/upload-manifest.test.js.map +1 -0
  91. package/dist/manifest-reconcile.d.ts.map +1 -1
  92. package/dist/manifest-reconcile.js +1 -26
  93. package/dist/manifest-reconcile.js.map +1 -1
  94. package/dist/posix-key.d.ts +36 -0
  95. package/dist/posix-key.d.ts.map +1 -0
  96. package/dist/posix-key.js +38 -0
  97. package/dist/posix-key.js.map +1 -0
  98. package/dist/s3.d.ts +2 -18
  99. package/dist/s3.d.ts.map +1 -1
  100. package/dist/s3.js +6 -20
  101. package/dist/s3.js.map +1 -1
  102. package/dist/sync/journal-ledger-stream.d.ts +56 -0
  103. package/dist/sync/journal-ledger-stream.d.ts.map +1 -0
  104. package/dist/sync/journal-ledger-stream.js +191 -0
  105. package/dist/sync/journal-ledger-stream.js.map +1 -0
  106. package/dist/sync/journal-ledger-stream.test.d.ts +12 -0
  107. package/dist/sync/journal-ledger-stream.test.d.ts.map +1 -0
  108. package/dist/sync/journal-ledger-stream.test.js +134 -0
  109. package/dist/sync/journal-ledger-stream.test.js.map +1 -0
  110. package/package.json +2 -1
@@ -0,0 +1,301 @@
1
+ /**
2
+ * Client-side manifest UPLOAD pass (sync-reconciliation-audit US-004).
3
+ *
4
+ * WHY THIS SEAM LIVES IN hq-cloud
5
+ * -------------------------------
6
+ * Two clients upload manifests — the desktop sync daemon (hq-sync) after a
7
+ * sync cycle, and `hq sync manifest` in the CLI — and the PRD's decision
8
+ * record settles it as "both, via shared hq-cloud code". The rules that make
9
+ * an upload SAFE are not obvious and must not be re-derived twice:
10
+ *
11
+ * - a snapshot may become the local delta BASE only after the server says
12
+ * `materialised: true` (a `completed` fold that was refused is not a base);
13
+ * - the delta base is the snapshotId the SERVER returns, never the local
14
+ * `snap-*` handle the builder minted (the server derives its own id);
15
+ * - `sequence` must strictly increase per (installation, scope), including
16
+ * across passes that failed before they uploaded anything;
17
+ * - every chunk of one pass must be byte-identical in the fields the server
18
+ * hashes into the snapshotId (`generatedAt`, `sequence`, `chunkCount`,
19
+ * `machineId`, `mode`, `scope`);
20
+ * - a `resend_full` at ANY chunk ends the pass and invalidates the base.
21
+ *
22
+ * Two implementations of those rules would drift, and the failure mode of the
23
+ * drift is silent server-side corruption of a scope's materialised view — the
24
+ * exact thing this audit exists to detect.
25
+ *
26
+ * WHAT THIS DELIBERATELY DOES NOT OWN
27
+ * -----------------------------------
28
+ * - **Auth and the base URL.** The transport is INJECTED. hq-cloud has no
29
+ * business deciding which API host a daemon talks to or how a JWT is
30
+ * minted; the clients already own both, and owning them here would force
31
+ * this module to import the vault client (and with it the AWS SDK) into
32
+ * what is otherwise a lean, hot-path module graph.
33
+ * - **Scheduling.** The caller decides when a pass runs; this function only
34
+ * refuses to run one too often (see the 24h throttle).
35
+ * - **Wiring.** The hq-cli `sync manifest` command, its `hq doctor` check,
36
+ * and the hq-sync daemon hook land SEPARATELY, in those repos, on top of
37
+ * {@link runManifestUploadPass} and {@link readManifestUploadStatus}.
38
+ *
39
+ * FAILURE POSTURE
40
+ * ---------------
41
+ * This never throws at the caller for anything that happens at runtime. The
42
+ * daemon calls it after a sync pass and must continue regardless: an audit
43
+ * that can break sync is strictly worse than no audit. Build errors, transport
44
+ * rejections, aborts and unexpected statuses all come back as
45
+ * `{ status: "failed" }`. Only invalid OPTIONS — a programmer error, not a
46
+ * runtime condition — throw.
47
+ */
48
+ import { type BuildManifestScope, type ManifestHashPolicy } from "./build-manifest.js";
49
+ import type { JournalSummary } from "../journal.js";
50
+ import type { SyncManifestMode, SyncManifestSource, SyncManifestUpload } from "./contract.js";
51
+ import { MANIFEST_SNAPSHOT_MAX_AGE_MS } from "./snapshot-store.js";
52
+ /**
53
+ * Env var that disables manifest uploads entirely. A user (or a support
54
+ * engineer) must be able to switch this feature off on a machine WITHOUT
55
+ * downgrading hq-cloud, and the switch must short-circuit before the walk —
56
+ * the walk, not the POST, is the expensive half.
57
+ */
58
+ export declare const MANIFEST_UPLOAD_DISABLED_ENV = "HQ_SYNC_MANIFEST_DISABLED";
59
+ /**
60
+ * Default minimum spacing between upload passes for one scope.
61
+ *
62
+ * The audit is a slow-moving safety net, not telemetry: a daily picture is
63
+ * enough to catch a wedged watcher, and a 70k-file walk per sync cycle is not
64
+ * something a laptop should pay for.
65
+ */
66
+ export declare const DEFAULT_MANIFEST_UPLOAD_MIN_INTERVAL_MS: number;
67
+ /**
68
+ * Wall-clock budget for the ENTIRE upload phase (all chunks), after which the
69
+ * pass stops sending and reports a non-throwing failure.
70
+ *
71
+ * Why the whole phase and not per chunk: the caller's actual requirement is
72
+ * "the daemon's `await` returns" — the desktop daemon runs this after every
73
+ * sync pass, and a transport that never settles would otherwise wedge the pass
74
+ * (and the sync cycle behind it) forever. A per-chunk budget would not bound
75
+ * that: a 30-chunk manifest would still admit 30 x budget of hanging. One
76
+ * budget for the phase bounds the pass by construction, whatever the chunk
77
+ * count.
78
+ *
79
+ * 60s is generous next to a single small JSON POST and mean next to a sync
80
+ * cycle, so it only ever fires on a genuinely wedged transport — never on a
81
+ * merely slow link, where the pass would be retried next cycle anyway.
82
+ *
83
+ * Note this bounds only the UPLOAD; `maxWallMs` bounds the filesystem walk.
84
+ * They are separate budgets because they fail for unrelated reasons (a slow
85
+ * disk vs. a black-holed socket) and a caller may reasonably tune one alone.
86
+ */
87
+ export declare const DEFAULT_MANIFEST_UPLOAD_WALL_MS = 60000;
88
+ /**
89
+ * First retry floor after a pass FAILED without reaching the server.
90
+ *
91
+ * The 24h throttle is armed by `lastUploadAt`, which only a pass that actually
92
+ * reached the server writes. That is correct — a network blip must not
93
+ * suppress the audit for a day — but taken alone it means a permanently broken
94
+ * endpoint (a wrong base URL, an unenrolled installation answering 403, a 5xx
95
+ * outage) buys a FULL tree walk, and under `hashPolicy: "auto"` a full content
96
+ * hash, on EVERY sync cycle. On a large vault that is minutes of IO and
97
+ * gigabytes of RSS per cycle, forever, for an audit that cannot succeed.
98
+ *
99
+ * So a failed pass arms its own, much shorter floor, doubling per consecutive
100
+ * failure up to {@link MANIFEST_FAILURE_BACKOFF_MAX_MS}. One hour keeps a
101
+ * transient outage cheap to recover from (the next hourly cycle retries) while
102
+ * capping a hard failure's cost at ~1 walk/hour instead of 1 walk/cycle.
103
+ */
104
+ export declare const MANIFEST_FAILURE_BACKOFF_BASE_MS: number;
105
+ /** Ceiling for the failure backoff — the same daily spacing a healthy scope gets. */
106
+ export declare const MANIFEST_FAILURE_BACKOFF_MAX_MS: number;
107
+ /**
108
+ * Share of `source: "disk"` entries above which a FULL manifest is treated as
109
+ * an implausible picture of a scope that was previously tracked.
110
+ *
111
+ * Set hard against 1.0 rather than at a "suspicious" level like 0.9 on
112
+ * purpose. A legitimate manifest CAN be very disk-heavy — a user who just
113
+ * restored a backup, or a first pass after a journal repair — and refusing
114
+ * those would suppress the audit exactly when it is most useful. The failure
115
+ * this guards is not "mostly disk": it is "the ledger vanished", which is
116
+ * total. 0.995 leaves room for the handful of `ledger`/`both` entries a
117
+ * partially-readable ledger still contributes without admitting a merely
118
+ * lopsided scope.
119
+ */
120
+ export declare const MANIFEST_IMPLAUSIBLE_DISK_RATIO = 0.995;
121
+ /**
122
+ * Retry floor for a scope that has failed `consecutiveFailures` times in a row.
123
+ *
124
+ * `1 → 1h, 2 → 2h, 3 → 4h … capped at 24h`. Zero (or anything nonsensical)
125
+ * means "no floor": a scope with no failure history is governed by the normal
126
+ * `lastUploadAt` throttle alone.
127
+ */
128
+ export declare function manifestFailureBackoffMs(consecutiveFailures: number): number;
129
+ /**
130
+ * Only an explicit, unambiguous value disables. Empty string, `0`, `false` and
131
+ * anything else mean "not set": env vars are routinely exported empty by
132
+ * shell wrappers, and treating that as "off" would silently disable the
133
+ * feature on machines nobody meant to opt out.
134
+ */
135
+ /**
136
+ * The kill switch, readable by a CALLER.
137
+ *
138
+ * `runManifestUploadPass` enforces it itself, but a caller that assembles the
139
+ * pass (resolving identity, minting a transport, choosing scopes) needs to
140
+ * check it BEFORE doing any of that, so an opted-out machine pays literally
141
+ * nothing. Exported rather than duplicated so the two can never disagree about
142
+ * what counts as "disabled".
143
+ */
144
+ export declare function isManifestUploadDisabled(env: NodeJS.ProcessEnv): boolean;
145
+ /** Raw HTTP response, reduced to the two things the pass reasons about. */
146
+ export interface ManifestUploadResponse {
147
+ status: number;
148
+ body?: unknown;
149
+ }
150
+ /**
151
+ * Injected by hq-sync / hq-cli: POSTs one chunk to
152
+ * `POST /v1/sync-manifest/upload` with the caller's own JWT and base URL.
153
+ *
154
+ * It must RESOLVE with the status for any HTTP answer (including 4xx/5xx) and
155
+ * may reject only for transport-level failures; a rejection is caught and
156
+ * reported as a failed pass either way.
157
+ */
158
+ export type ManifestUploadTransport = (chunk: SyncManifestUpload, ctx: {
159
+ attempt: number;
160
+ }) => Promise<ManifestUploadResponse>;
161
+ export interface ManifestUploadLogger {
162
+ info?: (message: string, meta?: Record<string, unknown>) => void;
163
+ warn?: (message: string, meta?: Record<string, unknown>) => void;
164
+ error?: (message: string, meta?: Record<string, unknown>) => void;
165
+ }
166
+ export interface RunManifestUploadPassOptions {
167
+ scope: BuildManifestScope;
168
+ hqRoot: string;
169
+ stateDir: string;
170
+ /** The SAME installation id the client-health heartbeat reports. */
171
+ installationId: string;
172
+ machineId: string;
173
+ source: SyncManifestSource;
174
+ transport: ManifestUploadTransport;
175
+ /** Injected clock (epoch ms) — tests pin it; production omits it. */
176
+ now?: number;
177
+ /** Injected env — tests pin it; production reads `process.env`. */
178
+ env?: NodeJS.ProcessEnv;
179
+ /** `--full`: skip the delta base and send a fresh baseline. */
180
+ forceFull?: boolean;
181
+ /** `--print`: build only. Never uploads, never persists a snapshot. */
182
+ dryRun?: boolean;
183
+ /**
184
+ * Explicit, human-initiated invocations (`hq sync manifest`) may bypass the
185
+ * throttle. The DAEMON path must not — that is the whole point of it.
186
+ */
187
+ ignoreThrottle?: boolean;
188
+ minIntervalMs?: number;
189
+ abortSignal?: AbortSignal;
190
+ /** Wall-clock bound on the tree WALK (forwarded to the builder). */
191
+ maxWallMs?: number;
192
+ /**
193
+ * Forwarded to the builder. Omitted means the builder's stat-only default,
194
+ * which is what the daemon must use. `full` is reserved for an explicit
195
+ * human invocation (`hq sync manifest --full-hash`).
196
+ */
197
+ hashPolicy?: ManifestHashPolicy;
198
+ /** `auto` only, forwarded to the builder: files this pass may read. */
199
+ maxHashedFiles?: number;
200
+ /** `auto` only, forwarded to the builder: wall clock spent hashing. */
201
+ maxHashMs?: number;
202
+ /**
203
+ * Wall-clock bound on the whole UPLOAD phase. See
204
+ * {@link DEFAULT_MANIFEST_UPLOAD_WALL_MS}. Measured against the real clock,
205
+ * not `now` — `now` pins the manifest's CONTENT (so a pass is reproducible),
206
+ * while this is about how long a caller is prepared to be blocked.
207
+ */
208
+ uploadWallMs?: number;
209
+ logger?: ManifestUploadLogger;
210
+ /** Test seam, forwarded to the builder: stands in for the real `listJournals()`. */
211
+ listJournalsImpl?: () => JournalSummary[];
212
+ /**
213
+ * Test seam, forwarded to the builder: entries per chunk. Production leaves
214
+ * it unset and gets the contract ceiling; tests shrink it so the multi-chunk
215
+ * paths (ordering, shared header, mid-pass abort) are actually reachable.
216
+ */
217
+ maxEntriesPerChunk?: number;
218
+ }
219
+ export type ManifestUploadPassStatus = "disabled" | "throttled" | "locked" | "uploaded" | "printed" | "soft_skipped" | "resend_full_scheduled"
220
+ /**
221
+ * The tree walk did not finish (wall clock or abort), so the manifest
222
+ * describes only the part of the scope the walker reached. NOTHING is
223
+ * uploaded on this path: a truncated walk of a large vault can legitimately
224
+ * yield ZERO entries, and a full-mode manifest with zero entries tells the
225
+ * server this client holds nothing at all — which it would then act on. The
226
+ * pass burns its sequence, arms the failure backoff, and retries later.
227
+ */
228
+ | "walk_truncated"
229
+ /**
230
+ * The built manifest is a FULL statement that this machine holds nothing it
231
+ * has ever tracked — every entry `source: "disk"` — while a prior local
232
+ * snapshot for the same scope says otherwise. NOTHING is uploaded.
233
+ *
234
+ * Found on a real machine: every generation of the scope's v3 ledger store
235
+ * (`snapshot-*.bin` and `wal-*.bin`) was truncated and no legacy shard
236
+ * existed, so the ledger read came back empty, all 188,997 files walked read
237
+ * as on-disk-never-tracked, and the pass uploaded that as the truth. The
238
+ * ledger read itself is fixed (an unreadable ledger is no longer an empty
239
+ * one), but this is the backstop for the class: whatever makes the ledger
240
+ * silently disappear next time, a scope does not go from "fully tracked" to
241
+ * "nothing tracked" in one cycle.
242
+ */
243
+ | "ledger_implausible" | "failed";
244
+ export type ManifestUploadFailureKind = "build_error" | "transport_error" | "aborted" | "upload_timeout" | "chunk_too_large" | "manifest_too_large" | "rejected";
245
+ export interface ManifestUploadFailure {
246
+ kind: ManifestUploadFailureKind;
247
+ /** HTTP status, when the failure came from a response rather than a throw. */
248
+ status?: number;
249
+ /** Error CLASS name or server reason code — never a message with paths in it. */
250
+ detail?: string;
251
+ chunkIndex?: number;
252
+ }
253
+ export interface RunManifestUploadPassResult {
254
+ status: ManifestUploadPassStatus;
255
+ scopeKey: string;
256
+ snapshotId?: string;
257
+ mode?: SyncManifestMode;
258
+ chunkCount?: number;
259
+ uploadedChunks?: number;
260
+ /** True when the NEXT pass must send a full manifest. */
261
+ nextModeFull?: boolean;
262
+ /** Populated only for `dryRun` — the built chunks, unsent. */
263
+ chunks?: SyncManifestUpload[];
264
+ error?: ManifestUploadFailure;
265
+ }
266
+ /** Per-scope upload state, for `hq doctor`'s `manifest` check. */
267
+ export interface ManifestUploadStatus {
268
+ scopeKey: string;
269
+ lastUploadAt: string | null;
270
+ snapshotId: string | null;
271
+ sequence: number;
272
+ /** False when the stored record is bookkeeping-only (next pass is full). */
273
+ baseUsable: boolean;
274
+ }
275
+ /**
276
+ * The `command` recorded in the lock file. It shows up verbatim in
277
+ * `OperationLockedError` messages and in `hq doctor`-style lock dumps, so it
278
+ * names the operation a human would recognise.
279
+ */
280
+ export declare const MANIFEST_UPLOAD_LOCK_COMMAND = "sync-manifest";
281
+ /**
282
+ * Build and upload one scope's manifest.
283
+ *
284
+ * Chunks go up SEQUENTIALLY in ascending `chunkIndex`: the server folds them
285
+ * into one snapshot keyed by a hash of the shared header fields, and a
286
+ * concurrent send would make a partial-failure state (some chunks in, some
287
+ * not) impossible to reason about from the client side.
288
+ */
289
+ export declare function runManifestUploadPass(options: RunManifestUploadPassOptions): Promise<RunManifestUploadPassResult>;
290
+ /**
291
+ * Read per-scope upload state without touching the network or the disk tree.
292
+ *
293
+ * This is the seam `hq doctor`'s `manifest` check consumes: it answers "when
294
+ * did this machine last tell the server what it holds?" for each scope, which
295
+ * is the one question that distinguishes "no findings" from "no data".
296
+ * Missing/older snapshots report `lastUploadAt: null` — never uploaded.
297
+ */
298
+ export declare function readManifestUploadStatus(stateDir: string, scopes: readonly BuildManifestScope[]): ManifestUploadStatus[];
299
+ /** Re-exported so callers do not need a second import for the staleness rule. */
300
+ export { MANIFEST_SNAPSHOT_MAX_AGE_MS };
301
+ //# sourceMappingURL=upload-manifest.d.ts.map
@@ -0,0 +1 @@
1
+ {"version":3,"file":"upload-manifest.d.ts","sourceRoot":"","sources":["../../src/manifest/upload-manifest.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8CG;AAEH,OAAO,EAEL,KAAK,kBAAkB,EACvB,KAAK,kBAAkB,EACxB,MAAM,qBAAqB,CAAC;AAC7B,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,eAAe,CAAC;AAUpD,OAAO,KAAK,EAAE,gBAAgB,EAAE,kBAAkB,EAAE,kBAAkB,EAAE,MAAM,eAAe,CAAC;AAC9F,OAAO,EACL,4BAA4B,EAQ7B,MAAM,qBAAqB,CAAC;AAI7B;;;;;GAKG;AACH,eAAO,MAAM,4BAA4B,8BAA8B,CAAC;AAExE;;;;;;GAMG;AACH,eAAO,MAAM,uCAAuC,QAAsB,CAAC;AAE3E;;;;;;;;;;;;;;;;;;;GAmBG;AACH,eAAO,MAAM,+BAA+B,QAAS,CAAC;AAEtD;;;;;;;;;;;;;;;GAeG;AACH,eAAO,MAAM,gCAAgC,QAAiB,CAAC;AAE/D,qFAAqF;AACrF,eAAO,MAAM,+BAA+B,QAAsB,CAAC;AAEnE;;;;;;;;;;;;GAYG;AACH,eAAO,MAAM,+BAA+B,QAAQ,CAAC;AAErD;;;;;;GAMG;AACH,wBAAgB,wBAAwB,CAAC,mBAAmB,EAAE,MAAM,GAAG,MAAM,CAM5E;AAED;;;;;GAKG;AACH;;;;;;;;GAQG;AACH,wBAAgB,wBAAwB,CAAC,GAAG,EAAE,MAAM,CAAC,UAAU,GAAG,OAAO,CAExE;AAWD,2EAA2E;AAC3E,MAAM,WAAW,sBAAsB;IACrC,MAAM,EAAE,MAAM,CAAC;IACf,IAAI,CAAC,EAAE,OAAO,CAAC;CAChB;AAED;;;;;;;GAOG;AACH,MAAM,MAAM,uBAAuB,GAAG,CACpC,KAAK,EAAE,kBAAkB,EACzB,GAAG,EAAE;IAAE,OAAO,EAAE,MAAM,CAAA;CAAE,KACrB,OAAO,CAAC,sBAAsB,CAAC,CAAC;AAErC,MAAM,WAAW,oBAAoB;IACnC,IAAI,CAAC,EAAE,CAAC,OAAO,EAAE,MAAM,EAAE,IAAI,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,KAAK,IAAI,CAAC;IACjE,IAAI,CAAC,EAAE,CAAC,OAAO,EAAE,MAAM,EAAE,IAAI,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,KAAK,IAAI,CAAC;IACjE,KAAK,CAAC,EAAE,CAAC,OAAO,EAAE,MAAM,EAAE,IAAI,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,KAAK,IAAI,CAAC;CACnE;AAID,MAAM,WAAW,4BAA4B;IAC3C,KAAK,EAAE,kBAAkB,CAAC;IAC1B,MAAM,EAAE,MAAM,CAAC;IACf,QAAQ,EAAE,MAAM,CAAC;IACjB,oEAAoE;IACpE,cAAc,EAAE,MAAM,CAAC;IACvB,SAAS,EAAE,MAAM,CAAC;IAClB,MAAM,EAAE,kBAAkB,CAAC;IAC3B,SAAS,EAAE,uBAAuB,CAAC;IACnC,qEAAqE;IACrE,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,mEAAmE;IACnE,GAAG,CAAC,EAAE,MAAM,CAAC,UAAU,CAAC;IACxB,+DAA+D;IAC/D,SAAS,CAAC,EAAE,OAAO,CAAC;IACpB,uEAAuE;IACvE,MAAM,CAAC,EAAE,OAAO,CAAC;IACjB;;;OAGG;IACH,cAAc,CAAC,EAAE,OAAO,CAAC;IACzB,aAAa,CAAC,EAAE,MAAM,CAAC;IACvB,WAAW,CAAC,EAAE,WAAW,CAAC;IAC1B,oEAAoE;IACpE,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB;;;;OAIG;IACH,UAAU,CAAC,EAAE,kBAAkB,CAAC;IAChC,uEAAuE;IACvE,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB,uEAAuE;IACvE,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB;;;;;OAKG;IACH,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,MAAM,CAAC,EAAE,oBAAoB,CAAC;IAC9B,oFAAoF;IACpF,gBAAgB,CAAC,EAAE,MAAM,cAAc,EAAE,CAAC;IAC1C;;;;OAIG;IACH,kBAAkB,CAAC,EAAE,MAAM,CAAC;CAC7B;AAED,MAAM,MAAM,wBAAwB,GAChC,UAAU,GACV,WAAW,GACX,QAAQ,GACR,UAAU,GACV,SAAS,GACT,cAAc,GACd,uBAAuB;AACzB;;;;;;;GAOG;GACD,gBAAgB;AAClB;;;;;;;;;;;;;GAaG;GACD,oBAAoB,GACpB,QAAQ,CAAC;AAEb,MAAM,MAAM,yBAAyB,GACjC,aAAa,GACb,iBAAiB,GACjB,SAAS,GACT,gBAAgB,GAChB,iBAAiB,GACjB,oBAAoB,GACpB,UAAU,CAAC;AAEf,MAAM,WAAW,qBAAqB;IACpC,IAAI,EAAE,yBAAyB,CAAC;IAChC,8EAA8E;IAC9E,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,iFAAiF;IACjF,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,UAAU,CAAC,EAAE,MAAM,CAAC;CACrB;AAED,MAAM,WAAW,2BAA2B;IAC1C,MAAM,EAAE,wBAAwB,CAAC;IACjC,QAAQ,EAAE,MAAM,CAAC;IACjB,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,IAAI,CAAC,EAAE,gBAAgB,CAAC;IACxB,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB,yDAAyD;IACzD,YAAY,CAAC,EAAE,OAAO,CAAC;IACvB,8DAA8D;IAC9D,MAAM,CAAC,EAAE,kBAAkB,EAAE,CAAC;IAC9B,KAAK,CAAC,EAAE,qBAAqB,CAAC;CAC/B;AAED,kEAAkE;AAClE,MAAM,WAAW,oBAAoB;IACnC,QAAQ,EAAE,MAAM,CAAC;IACjB,YAAY,EAAE,MAAM,GAAG,IAAI,CAAC;IAC5B,UAAU,EAAE,MAAM,GAAG,IAAI,CAAC;IAC1B,QAAQ,EAAE,MAAM,CAAC;IACjB,4EAA4E;IAC5E,UAAU,EAAE,OAAO,CAAC;CACrB;AAwID;;;;GAIG;AACH,eAAO,MAAM,4BAA4B,kBAAkB,CAAC;AA+H5D;;;;;;;GAOG;AACH,wBAAsB,qBAAqB,CACzC,OAAO,EAAE,4BAA4B,GACpC,OAAO,CAAC,2BAA2B,CAAC,CA2DtC;AA4eD;;;;;;;GAOG;AACH,wBAAgB,wBAAwB,CACtC,QAAQ,EAAE,MAAM,EAChB,MAAM,EAAE,SAAS,kBAAkB,EAAE,GACpC,oBAAoB,EAAE,CAgBxB;AAED,iFAAiF;AACjF,OAAO,EAAE,4BAA4B,EAAE,CAAC"}