@indigoai-us/hq-cloud 6.14.17 → 6.14.18

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 (39) hide show
  1. package/dist/active-company.d.ts +43 -0
  2. package/dist/active-company.d.ts.map +1 -0
  3. package/dist/active-company.js +132 -0
  4. package/dist/active-company.js.map +1 -0
  5. package/dist/active-company.test.d.ts +2 -0
  6. package/dist/active-company.test.d.ts.map +1 -0
  7. package/dist/active-company.test.js +149 -0
  8. package/dist/active-company.test.js.map +1 -0
  9. package/dist/bin/sync-runner-planning.d.ts +27 -1
  10. package/dist/bin/sync-runner-planning.d.ts.map +1 -1
  11. package/dist/bin/sync-runner-planning.js +33 -4
  12. package/dist/bin/sync-runner-planning.js.map +1 -1
  13. package/dist/bin/sync-runner-planning.test.d.ts +2 -0
  14. package/dist/bin/sync-runner-planning.test.d.ts.map +1 -0
  15. package/dist/bin/sync-runner-planning.test.js +115 -0
  16. package/dist/bin/sync-runner-planning.test.js.map +1 -0
  17. package/dist/bin/sync-runner.d.ts +22 -7
  18. package/dist/bin/sync-runner.d.ts.map +1 -1
  19. package/dist/bin/sync-runner.js +92 -16
  20. package/dist/bin/sync-runner.js.map +1 -1
  21. package/dist/bin/sync-runner.test.js +357 -5
  22. package/dist/bin/sync-runner.test.js.map +1 -1
  23. package/dist/manifest-reconcile.d.ts +118 -5
  24. package/dist/manifest-reconcile.d.ts.map +1 -1
  25. package/dist/manifest-reconcile.js +319 -62
  26. package/dist/manifest-reconcile.js.map +1 -1
  27. package/dist/manifest-reconcile.test.js +824 -2
  28. package/dist/manifest-reconcile.test.js.map +1 -1
  29. package/package.json +1 -1
  30. package/pnpm-workspace.yaml +1 -1
  31. package/src/active-company.test.ts +188 -0
  32. package/src/active-company.ts +168 -0
  33. package/src/bin/sync-runner-planning.test.ts +131 -0
  34. package/src/bin/sync-runner-planning.ts +60 -7
  35. package/src/bin/sync-runner.test.ts +430 -10
  36. package/src/bin/sync-runner.ts +129 -23
  37. package/src/manifest-reconcile.test.ts +1019 -3
  38. package/src/manifest-reconcile.ts +424 -66
  39. package/test/joiner-manifest-reconcile.integration.test.ts +283 -0
@@ -5,6 +5,22 @@
5
5
  * only after the complete fanout has settled. That makes the locally
6
6
  * materialized cloud companies authoritative for their own manifest entries
7
7
  * without discarding entries the personal vault already had.
8
+ *
9
+ * Two layers live here on purpose:
10
+ *
11
+ * - `reconcileManifest(hqRoot, targets)` is the pure reconciler. It takes
12
+ * already-resolved targets and does nothing but validate slugs, merge the
13
+ * fields it owns, and (only when something would actually change) write the
14
+ * manifest.
15
+ * - `reconcileCompanyManifest(options)` is the sync-runner adapter. It decides
16
+ * WHICH targets are eligible (personal mode, fanout completion, on-disk
17
+ * materialization, and — only when an entity resolver is injected — live
18
+ * entity resolution) and then delegates the mutation.
19
+ *
20
+ * The adapter keeps its name and options-object shape because `sync-runner`
21
+ * injects it through `deps.reconcileManifest`. That injection seam is an
22
+ * options-object callback with a different shape from the pure reconciler and
23
+ * must not be conflated with it — renaming the adapter would break the seam.
8
24
  */
9
25
 
10
26
  import { randomUUID } from "node:crypto";
@@ -12,19 +28,102 @@ import * as fs from "node:fs";
12
28
  import * as path from "node:path";
13
29
  import yaml from "js-yaml";
14
30
 
15
- import type { EntityInfo } from "./vault-client.js";
31
+ import {
32
+ VaultNotFoundError,
33
+ VaultPermissionDeniedError,
34
+ type EntityInfo,
35
+ } from "./vault-client.js";
16
36
 
17
37
  export interface ManifestReconcileTarget {
18
38
  uid: string;
19
39
  slug: string;
40
+ /**
41
+ * Carried by the fanout plan, which already resolved the entity to build the
42
+ * target. Present so the adapter can write a manifest entry with zero extra
43
+ * API calls; still optional because a plan built from a degraded lookup keeps
44
+ * the uid as its only identifier.
45
+ */
46
+ name?: string;
47
+ bucketName?: string;
48
+ /**
49
+ * Entity type/status as captured AT PLAN TIME. These are the liveness
50
+ * evidence for the no-`getEntity` path and are checked with exactly the same
51
+ * predicate the `getEntity` path applies to a freshly fetched entity. Both
52
+ * are optional in the type and REQUIRED in practice: a target that carries
53
+ * neither is "unknown", and unknown is rejected.
54
+ */
55
+ entityType?: string;
56
+ entityStatus?: string;
20
57
  personalMode?: boolean;
21
58
  }
22
59
 
60
+ /**
61
+ * Reported when the injected entity resolver fails in a way that is NOT an
62
+ * ordinary "this entity is gone" lookup outcome. The target is skipped either
63
+ * way; this exists so a systematic resolver failure cannot present as the
64
+ * silent "joiners never get manifest entries" bug this module was written to
65
+ * fix.
66
+ */
67
+ export interface ManifestReconcileDiagnostic {
68
+ event: string;
69
+ message: string;
70
+ err: unknown;
71
+ context: Record<string, unknown>;
72
+ }
73
+
23
74
  export interface ManifestReconcileOptions {
24
75
  hqRoot: string;
25
76
  targets: readonly ManifestReconcileTarget[];
26
77
  completedCompanySlugs: ReadonlySet<string>;
27
- getEntity: (uid: string) => Promise<EntityInfo>;
78
+ /**
79
+ * OPTIONAL entity resolver.
80
+ *
81
+ * When supplied, every eligible target is re-verified against a freshly
82
+ * fetched entity ({@link isLiveCompany}) before it may contribute an entry.
83
+ *
84
+ * When omitted — the sync-runner path — each eligible target's entry is
85
+ * resolved from the plan-carried `uid`/`slug`/`name`/`bucketName`, costing
86
+ * zero API calls. This does NOT discharge the liveness requirement: the same
87
+ * type/status assertion still runs, against `entityType`/`entityStatus`
88
+ * captured by `buildFanoutPlan` at the moment it fetched the entity (see
89
+ * {@link isLiveTargetSnapshot}). The only thing given up is freshness — the
90
+ * evidence is from earlier in the same run rather than from a second fetch.
91
+ *
92
+ * A target carrying no liveness fields is REJECTED. Absence is treated as
93
+ * "unknown", never as "fine": the degraded lookup path in `buildFanoutPlan`
94
+ * produces exactly that shape, and admitting it would let an unverified
95
+ * entity into a vault-synced file.
96
+ */
97
+ getEntity?: (uid: string) => Promise<EntityInfo>;
98
+ /**
99
+ * Optional sink for non-fatal problems. Never affects control flow.
100
+ */
101
+ reportDiagnostic?: (diagnostic: ManifestReconcileDiagnostic) => void;
102
+ }
103
+
104
+ /**
105
+ * A target that has already been resolved to the values the manifest should
106
+ * carry. `name` and `bucketName` are optional: a company that lacks either is
107
+ * still a real, routable company and must get its `cloud_uid` entry.
108
+ */
109
+ export interface ManifestReconcileEntryTarget {
110
+ slug: string;
111
+ uid: string;
112
+ bucketName?: string;
113
+ name?: string;
114
+ }
115
+
116
+ /**
117
+ * `added` — slugs newly inserted into `companies:`.
118
+ * `updated` — slugs whose pre-existing entry had a field changed.
119
+ * `skipped` — slugs rejected outright (unsafe slug, non-record existing entry).
120
+ * `written` — whether the manifest file was actually rewritten.
121
+ */
122
+ export interface ManifestReconcileResult {
123
+ written: boolean;
124
+ added: string[];
125
+ updated: string[];
126
+ skipped: string[];
28
127
  }
29
128
 
30
129
  interface ManifestCompany {
@@ -39,122 +138,381 @@ interface ManifestDocument {
39
138
  [key: string]: unknown;
40
139
  }
41
140
 
141
+ /**
142
+ * A PLAIN object, not merely "typeof object". js-yaml parses timestamp scalars
143
+ * into `Date`, and a looser check let a `Date` masquerade as the company map (or
144
+ * as an entry), which both defeated the non-record skip and silently destroyed
145
+ * the value via object spread. Arrays, Date, RegExp, and Map are all rejected.
146
+ */
42
147
  function isRecord(value: unknown): value is Record<string, unknown> {
43
- return value !== null && typeof value === "object" && !Array.isArray(value);
148
+ if (value === null || typeof value !== "object") return false;
149
+ const proto = Object.getPrototypeOf(value) as unknown;
150
+ return proto === Object.prototype || proto === null;
151
+ }
152
+
153
+ /**
154
+ * Keys that would traverse or mutate the prototype chain rather than create an
155
+ * own property. `__proto__` in particular resolves to `Object.prototype` on read
156
+ * and invokes the prototype setter on write, so it never persists to YAML and
157
+ * therefore reported drift on every single run — an unbounded rewrite loop on a
158
+ * vault-synced file. None of these is ever a legitimate company directory name.
159
+ */
160
+ const UNSAFE_SLUG_KEYS = new Set(["__proto__", "constructor", "prototype"]);
161
+
162
+ /** Own-property read; never falls through to the prototype chain. */
163
+ function ownEntry(
164
+ companies: Record<string, ManifestCompany>,
165
+ slug: string,
166
+ ): ManifestCompany | undefined {
167
+ return Object.prototype.hasOwnProperty.call(companies, slug) ? companies[slug] : undefined;
168
+ }
169
+
170
+ /** Own-property write; never invokes an inherited setter. */
171
+ function setEntry(
172
+ companies: Record<string, ManifestCompany>,
173
+ slug: string,
174
+ value: ManifestCompany,
175
+ ): void {
176
+ Object.defineProperty(companies, slug, {
177
+ value,
178
+ enumerable: true,
179
+ writable: true,
180
+ configurable: true,
181
+ });
182
+ }
183
+
184
+ /**
185
+ * THE liveness rule. Both eligibility paths route through this single function
186
+ * so they cannot drift: an entity qualifies for a manifest entry only if it is
187
+ * an active company.
188
+ *
189
+ * Written to fail closed on `undefined`. That is the whole point — the
190
+ * plan-carried path can legitimately have no idea what the entity was (the
191
+ * degraded lookup branch in `buildFanoutPlan` records nothing), and "no idea"
192
+ * must never read as "active company".
193
+ */
194
+ function isLiveCompanyDescriptor(
195
+ type: string | undefined,
196
+ status: string | undefined,
197
+ ): boolean {
198
+ return type === "company" && status === "active";
44
199
  }
45
200
 
201
+ /**
202
+ * A company is live when the entity still resolves to the uid we routed on and
203
+ * is an active company. `name` and `bucketName` are deliberately NOT required:
204
+ * demanding them dropped otherwise-valid companies from the manifest entirely,
205
+ * which is exactly the joiner bug this module now guards against. Missing
206
+ * fields are omitted from the written entry instead of disqualifying it.
207
+ */
46
208
  function isLiveCompany(entity: EntityInfo, uid: string): boolean {
209
+ return entity.uid === uid && isLiveCompanyDescriptor(entity.type, entity.status);
210
+ }
211
+
212
+ /**
213
+ * The same rule applied to liveness captured at plan time instead of to a
214
+ * freshly fetched entity. There is no uid re-check here because there is no
215
+ * second observation to reconcile against — the snapshot came off the very
216
+ * `entity.get(uid)` that produced this target.
217
+ */
218
+ function isLiveTargetSnapshot(target: ManifestReconcileTarget): boolean {
219
+ return isLiveCompanyDescriptor(target.entityType, target.entityStatus);
220
+ }
221
+
222
+ /**
223
+ * Is this entity-probe failure the routine kind?
224
+ *
225
+ * "The company is gone" (404) and "the caller can no longer see it" (403) are
226
+ * the two ordinary reasons a target stops resolving, and both correctly mean
227
+ * "skip, write nothing". Anything else — an auth failure, a 5xx, a network
228
+ * fault, or a plain programming error like a TypeError — shares the same
229
+ * control flow but is NOT routine, and swallowing it silently is how a broken
230
+ * resolver disguises itself as "joiners never get manifest entries".
231
+ *
232
+ * The duck-typed `statusCode` arm matters: `buildFanoutPlan` already classifies
233
+ * this same call's failures that way, so a bare `{ statusCode }` rejection is a
234
+ * shape this codebase genuinely produces, not a hypothetical.
235
+ */
236
+ function isExpectedLookupFailure(err: unknown): boolean {
237
+ if (err instanceof VaultNotFoundError) return true;
238
+ if (err instanceof VaultPermissionDeniedError) return true;
47
239
  return (
48
- entity.uid === uid &&
49
- entity.type === "company" &&
50
- entity.status === "active" &&
51
- typeof entity.name === "string" &&
52
- entity.name.length > 0 &&
53
- typeof entity.bucketName === "string" &&
54
- entity.bucketName.length > 0
240
+ typeof err === "object" &&
241
+ err !== null &&
242
+ "statusCode" in err &&
243
+ typeof (err as { statusCode?: unknown }).statusCode === "number"
55
244
  );
56
245
  }
57
246
 
58
- function hasCompanyDirectory(companiesDir: string, slug: string): boolean {
247
+ /** Non-empty string, or undefined. Keys with no value are never written. */
248
+ function optionalField(value: string | undefined): string | undefined {
249
+ return typeof value === "string" && value.length > 0 ? value : undefined;
250
+ }
251
+
252
+ /**
253
+ * Pure path check — a slug must name a direct child of `companies/` and nothing
254
+ * else. This deliberately does NOT require the directory to exist; the on-disk
255
+ * stat check is an eligibility concern and lives in the adapter.
256
+ */
257
+ function isSafeCompanySlug(companiesDir: string, slug: string): boolean {
258
+ if (slug.length === 0) return false;
259
+ if (slug.includes("/") || slug.includes("\\")) return false;
260
+ if (slug === "." || slug === "..") return false;
261
+ if (UNSAFE_SLUG_KEYS.has(slug)) return false;
59
262
  const resolvedCompaniesDir = path.resolve(companiesDir);
60
263
  const companyDir = path.resolve(resolvedCompaniesDir, slug);
61
- if (path.dirname(companyDir) !== resolvedCompaniesDir) return false;
264
+ return path.dirname(companyDir) === resolvedCompaniesDir;
265
+ }
266
+
267
+ function hasCompanyDirectory(companiesDir: string, slug: string): boolean {
268
+ if (!isSafeCompanySlug(companiesDir, slug)) return false;
62
269
  try {
63
- return fs.statSync(companyDir).isDirectory();
270
+ return fs.statSync(path.resolve(companiesDir, slug)).isDirectory();
64
271
  } catch {
65
272
  return false;
66
273
  }
67
274
  }
68
275
 
276
+ /**
277
+ * Read the manifest, or return null when there is nothing safe to merge into.
278
+ * A missing manifest is a no-op, NOT an invitation to create one: this module
279
+ * only ever restores entries into a manifest that already exists.
280
+ */
69
281
  function loadManifest(manifestPath: string): ManifestDocument | null {
70
282
  try {
71
- const raw = fs.readFileSync(manifestPath, "utf8");
72
- const parsed = yaml.load(raw);
283
+ const parsed = yaml.load(fs.readFileSync(manifestPath, "utf8"));
73
284
  return isRecord(parsed) ? (parsed as ManifestDocument) : null;
74
- } catch (err) {
75
- if ((err as NodeJS.ErrnoException).code === "ENOENT") return {};
285
+ } catch {
76
286
  return null;
77
287
  }
78
288
  }
79
289
 
80
- function writeManifestAtomically(manifestPath: string, document: ManifestDocument): void {
290
+ function serializeManifest(document: ManifestDocument): string {
291
+ return yaml.dump(document, { lineWidth: -1 });
292
+ }
293
+
294
+ /**
295
+ * Temp-file + rename. The temp file is created in the SAME directory as the
296
+ * target so the rename is a true atomic same-filesystem operation.
297
+ *
298
+ * The `finally` is not cosmetic: without it, a failed write or rename stranded a
299
+ * uniquely-named `.manifest-*.yaml` inside `companies/`, which rides the personal
300
+ * vault to every machine and accumulates one file per failed run.
301
+ *
302
+ * A write failure deliberately PROPAGATES rather than being swallowed into
303
+ * `written: false`. The caller at `sync-runner.ts` already wraps this in a
304
+ * try/catch that emits a `runner.manifest_reconcile.failed` diagnostic; reporting
305
+ * a real I/O failure as a clean no-op would hide it. The AC's "never throws"
306
+ * clause covers manifest READ problems (missing/unreadable/unparseable), all of
307
+ * which are handled as no-ops in `loadManifest`.
308
+ */
309
+ function writeManifestAtomically(manifestPath: string, serialized: string): void {
81
310
  const temporaryPath = path.join(
82
311
  path.dirname(manifestPath),
83
312
  `.manifest-${process.pid}-${randomUUID()}.yaml`,
84
313
  );
85
- fs.writeFileSync(temporaryPath, yaml.dump(document, { lineWidth: -1 }), "utf8");
86
- fs.renameSync(temporaryPath, manifestPath);
314
+ try {
315
+ fs.writeFileSync(temporaryPath, serialized, "utf8");
316
+ fs.renameSync(temporaryPath, manifestPath);
317
+ } finally {
318
+ // After a successful rename the temp path is already gone, so this is a
319
+ // no-op on the happy path and a cleanup on every failure path.
320
+ try {
321
+ fs.rmSync(temporaryPath, { force: true });
322
+ } catch {
323
+ // Best effort — never mask the original error.
324
+ }
325
+ }
326
+ }
327
+
328
+ function emptyResult(skipped: string[] = []): ManifestReconcileResult {
329
+ return { written: false, added: [], updated: [], skipped };
87
330
  }
88
331
 
89
332
  /**
90
- * Atomically merge live, successfully pulled company targets into
91
- * `companies/manifest.yaml`. Targets that are personal, incomplete, deleted,
92
- * no longer resolvable, or not materialized on disk are intentionally ignored.
333
+ * Merge resolved targets into `companies/manifest.yaml` and report what moved.
334
+ *
335
+ * Only the three fields this module owns are considered: `cloud_uid` (always
336
+ * written — it is the routing key), plus `name` and `bucket_name` when the
337
+ * target carries them. Omitting a field means "do not set this key"; it never
338
+ * means "delete it", so a manifest value already on disk survives a target that
339
+ * has nothing to say about it.
340
+ *
341
+ * The skip-if-unchanged comparison is load-bearing rather than an optimization.
342
+ * `yaml.dump` cannot round-trip comments, so an unconditional rewrite strips the
343
+ * manifest header — and because `manifest.yaml` rides the personal vault, that
344
+ * rewrite propagates to every machine and drives a recurring sync conflict loop.
345
+ * When nothing would change, the file is left byte-for-byte identical and its
346
+ * mtime untouched.
93
347
  */
94
- export async function reconcileCompanyManifest(
95
- options: ManifestReconcileOptions,
96
- ): Promise<void> {
97
- const companiesDir = path.join(options.hqRoot, "companies");
98
- const candidates: Array<{ slug: string; entity: EntityInfo }> = [];
348
+ export function reconcileManifest(
349
+ hqRoot: string,
350
+ targets: readonly ManifestReconcileEntryTarget[],
351
+ ): ManifestReconcileResult {
352
+ const companiesDir = path.join(hqRoot, "companies");
99
353
 
100
- for (const target of options.targets) {
101
- if (
102
- target.personalMode === true ||
103
- !options.completedCompanySlugs.has(target.slug) ||
104
- !hasCompanyDirectory(companiesDir, target.slug)
105
- ) {
354
+ const skipped: string[] = [];
355
+ // Dedupe by slug, last-wins. Two targets for one slug used to flip the change
356
+ // flag on and then back off again, leaving it stuck true while the resulting
357
+ // content was identical — a write (and an mtime bump) on every single run.
358
+ const safeBySlug = new Map<string, ManifestReconcileEntryTarget>();
359
+ for (const target of targets) {
360
+ if (!isSafeCompanySlug(companiesDir, target.slug)) {
361
+ skipped.push(target.slug);
106
362
  continue;
107
363
  }
108
-
109
- try {
110
- const entity = await options.getEntity(target.uid);
111
- if (isLiveCompany(entity, target.uid)) {
112
- candidates.push({ slug: target.slug, entity });
113
- }
114
- } catch {
115
- // The target is not presently a live, resolvable company. Never mint a
116
- // manifest entry from stale fanout data.
117
- }
364
+ safeBySlug.set(target.slug, target);
118
365
  }
119
366
 
120
- if (candidates.length === 0) return;
367
+ if (safeBySlug.size === 0) return emptyResult(skipped);
121
368
 
122
369
  const manifestPath = path.join(companiesDir, "manifest.yaml");
123
370
  const document = loadManifest(manifestPath);
124
- if (!document) return;
371
+ if (!document) return emptyResult(skipped);
372
+ // Pre-image, in the SAME serialization the writer uses. Comparing against the
373
+ // raw file bytes would be wrong: raw text carries comments and formatting that
374
+ // `yaml.dump` cannot reproduce, so every commented manifest would look
375
+ // "changed" and rewrite on every single run.
376
+ const before = serializeManifest(document);
125
377
 
126
378
  let companies: Record<string, ManifestCompany>;
127
- if (document.companies === undefined) {
379
+ if (document.companies === undefined || document.companies === null) {
380
+ // A missing `companies:` key and a bare `companies:` (which YAML parses as
381
+ // null) mean the same thing — an empty map. Treating them differently would
382
+ // silently deny a joiner their entry on one of the two shapes.
128
383
  companies = {};
129
384
  document.companies = companies;
130
385
  } else if (isRecord(document.companies)) {
131
386
  companies = document.companies as Record<string, ManifestCompany>;
132
387
  } else {
133
- // A malformed `companies` key is user state; refusing to replace it is
134
- // safer than losing a manifest that cannot be interpreted unambiguously.
135
- return;
388
+ // Any other shape (array, scalar, timestamp, string) is malformed user
389
+ // state; refusing to replace it is safer than losing a manifest that cannot
390
+ // be interpreted unambiguously.
391
+ return emptyResult(skipped);
392
+ }
393
+
394
+ // Changes are STAGED rather than applied in place, so the pre-image can be
395
+ // serialized for comparison and so a pure no-op costs no serialization at all.
396
+ const pending: Array<{ slug: string; entry: ManifestCompany; isNew: boolean }> = [];
397
+
398
+ for (const target of safeBySlug.values()) {
399
+ const existing = ownEntry(companies, target.slug);
400
+ if (existing !== undefined && !isRecord(existing)) {
401
+ skipped.push(target.slug);
402
+ continue;
403
+ }
404
+
405
+ const desired: ManifestCompany = { cloud_uid: target.uid };
406
+ const name = optionalField(target.name);
407
+ if (name !== undefined) desired.name = name;
408
+ const bucketName = optionalField(target.bucketName);
409
+ if (bucketName !== undefined) desired.bucket_name = bucketName;
410
+
411
+ if (existing === undefined) {
412
+ pending.push({ slug: target.slug, entry: desired, isNew: true });
413
+ continue;
414
+ }
415
+
416
+ // Compare ONLY the fields we would write. Everything else on the entry is
417
+ // someone else's state and never participates in the change decision.
418
+ const drifted = Object.keys(desired).some((key) => existing[key] !== desired[key]);
419
+ if (!drifted) continue;
420
+
421
+ pending.push({ slug: target.slug, entry: { ...existing, ...desired }, isNew: false });
136
422
  }
137
423
 
138
- let changed = false;
139
- for (const { slug, entity } of candidates) {
140
- const existing = companies[slug];
141
- if (existing !== undefined && !isRecord(existing)) continue;
142
- const entry: ManifestCompany = existing ?? {};
424
+ if (pending.length === 0) return emptyResult(skipped);
425
+
426
+ // Final-state guard. The write decision rests on the document itself, not on
427
+ // a flag the merge loop could have toggled: apply the staged changes, then
428
+ // write only if the serialized result genuinely differs from the `before`
429
+ // snapshot taken at load time. This is the backstop that stops any
430
+ // order-dependent bug — duplicate targets cancelling out, a sticky flag — from
431
+ // ever reaching a vault-synced file.
432
+ for (const change of pending) setEntry(companies, change.slug, change.entry);
433
+ const serialized = serializeManifest(document);
434
+ if (serialized === before) return emptyResult(skipped);
435
+
436
+ writeManifestAtomically(manifestPath, serialized);
437
+ return {
438
+ written: true,
439
+ added: pending.filter((change) => change.isNew).map((change) => change.slug),
440
+ updated: pending.filter((change) => !change.isNew).map((change) => change.slug),
441
+ skipped,
442
+ };
443
+ }
444
+
445
+ /**
446
+ * Atomically merge live, successfully pulled company targets into
447
+ * `companies/manifest.yaml`. Targets that are personal, incomplete, not
448
+ * materialized on disk, or not a verifiably active company are ignored.
449
+ *
450
+ * Every one of those filters applies on BOTH paths. The paths differ only in
451
+ * where the liveness evidence comes from: a fresh `getEntity` fetch when one is
452
+ * injected, or the type/status the fanout plan captured when it is not.
453
+ */
454
+ export async function reconcileCompanyManifest(
455
+ options: ManifestReconcileOptions,
456
+ ): Promise<ManifestReconcileResult> {
457
+ const companiesDir = path.join(options.hqRoot, "companies");
458
+ const resolvedTargets: ManifestReconcileEntryTarget[] = [];
459
+ const getEntity = options.getEntity;
460
+
461
+ for (const target of options.targets) {
143
462
  if (
144
- entry.name === entity.name &&
145
- entry.cloud_uid === entity.uid &&
146
- entry.bucket_name === entity.bucketName
463
+ target.personalMode === true ||
464
+ !options.completedCompanySlugs.has(target.slug) ||
465
+ !hasCompanyDirectory(companiesDir, target.slug)
147
466
  ) {
148
467
  continue;
149
468
  }
150
- companies[slug] = {
151
- ...entry,
152
- name: entity.name,
153
- cloud_uid: entity.uid,
154
- bucket_name: entity.bucketName,
155
- };
156
- changed = true;
469
+
470
+ if (getEntity === undefined) {
471
+ // Plan-carried path. The liveness rule is NOT relaxed here — it is
472
+ // applied to the type/status the plan captured off `entity.get`. A target
473
+ // with no such evidence fails closed and never reaches the manifest.
474
+ if (!isLiveTargetSnapshot(target)) continue;
475
+ resolvedTargets.push({
476
+ slug: target.slug,
477
+ uid: target.uid,
478
+ ...(target.name === undefined ? {} : { name: target.name }),
479
+ ...(target.bucketName === undefined ? {} : { bucketName: target.bucketName }),
480
+ });
481
+ continue;
482
+ }
483
+
484
+ try {
485
+ const entity = await getEntity(target.uid);
486
+ if (isLiveCompany(entity, target.uid)) {
487
+ resolvedTargets.push({
488
+ slug: target.slug,
489
+ uid: entity.uid,
490
+ ...(entity.name === undefined ? {} : { name: entity.name }),
491
+ ...(entity.bucketName === undefined ? {} : { bucketName: entity.bucketName }),
492
+ });
493
+ }
494
+ } catch (err) {
495
+ // The target is not presently a live, resolvable company. Never mint a
496
+ // manifest entry from stale fanout data — so the target is skipped
497
+ // regardless of WHY the probe failed.
498
+ //
499
+ // But "entity is gone" and "the resolver is broken" are different
500
+ // stories with identical control flow, and only the first is routine.
501
+ // Staying silent on the second is how a systematic resolver failure
502
+ // disguises itself as "joiners never get manifest entries" — the exact
503
+ // bug class this module exists to prevent.
504
+ if (!isExpectedLookupFailure(err)) {
505
+ options.reportDiagnostic?.({
506
+ event: "runner.manifest_reconcile.entity_probe_failed",
507
+ message: "unexpected error resolving company entity; target skipped",
508
+ err,
509
+ context: { slug: target.slug, uid: target.uid },
510
+ });
511
+ }
512
+ }
157
513
  }
158
514
 
159
- if (changed) writeManifestAtomically(manifestPath, document);
515
+ if (resolvedTargets.length === 0) return emptyResult();
516
+
517
+ return reconcileManifest(options.hqRoot, resolvedTargets);
160
518
  }