@things-factory/station 10.1.33

package/dist-server/service/station/station-screen-control-withdrawal.js

@@ -0,0 +1,128 @@
+"use strict";
+/**
+ * **통제 문서의 통제를 거두는 일** — 켜는 것만 막고 끄는 것을 열어 두면 통제가 한 방향으로만 선다.
+ *
+ * ═══════════════════════════════════════════════════════════════════════════
+ * ── 무엇이 열려 있었나 ─────────────────────────────────────────────────────
+ * 통제를 **켤 때**는 결재선이 있어야 했다(`turnsControlOn`). 그런데 `controlled: false` 로 저장하거나
+ * spec 을 지우는 데는 관문이 없었고, 발행 관문은 통제가 아닌 화면을 그대로 통과시킨다
+ * (`station-screen-publish-subscriber.ts` — `if (!spec?.controlled) return`). 그래서 화면을 만드는
+ * 권한만 든 작성자가 통제를 끄고 **서명 없는 도안을 발행**할 수 있었다.
+ *
+ * 판정(ADR-0047 ⑨): **결재로 세운 것은 결재로 거둔다.** 통제를 끄는 것과 통제 중인 spec 을 지우는
+ * 것은 발행 승인과 **같은 결재선**을 지난다. 끄는 것이 결재를 지났다면 발행 관문의 그 return 은
+ * 정당하다 — 그래서 관문은 그대로 둔다.
+ *
+ * ── 여기 있는 것 ──────────────────────────────────────────────────────────
+ * 판단만 둔다. DB 를 읽는 것은 부르는 쪽의 일이다 — 이 판단이 틀리면 통제 문서가 뚫리는데, 그것을
+ * 확인하는 시험이 DB·보드·spec·결재를 다 세운 뒤에야 물을 수 있으면 안 묻게 된다.
+ * ═══════════════════════════════════════════════════════════════════════════
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.STATION_SCREEN_SPEC_CONTENT = exports.WITHDRAWAL_REVERSIBILITY = exports.CONTROL_WITHDRAWAL_ACTIONS = void 0;
+exports.turnsControlOff = turnsControlOff;
+exports.whyNotWithdraw = whyNotWithdraw;
+exports.withdrawalReversibility = withdrawalReversibility;
+exports.controlWithdrawalRequestName = controlWithdrawalRequestName;
+exports.assertWithdrawalRaisable = assertWithdrawalRaisable;
+exports.stationScreenSpecBefore = stationScreenSpecBefore;
+const worklist_1 = require("@things-factory/worklist");
+const shell_1 = require("@things-factory/shell");
+/** 거두는 방식 둘 — 상신 때 정하고, 승인 때 그대로 한다. */
+exports.CONTROL_WITHDRAWAL_ACTIONS = ['turn-off', 'delete'];
+/**
+ * Both are reversible (ADR-0064, conditions for `reversible`): turning control on again and saving the
+ * settings again are the paired operations, releases are kept by board and not by the settings row's id,
+ * and the delete raise carries the settings as they were (`stationScreenSpecBefore`), so the approval
+ * record holds what to set up again.
+ */
+exports.WITHDRAWAL_REVERSIBILITY = {
+    'turn-off': 'reversible',
+    delete: 'reversible'
+};
+/**
+ * 이 저장이 통제를 **끄는** 저장인가.
+ *
+ * `after` 가 비어 있으면 끄는 것이 아니다 — 흐름만 저장하는 요청은 `controlled` 를 안 싣는다
+ * (§`saveStationScreenSpec`). 그것을 끄는 것으로 읽으면 통제 문서를 고칠 수조차 없게 된다.
+ */
+function turnsControlOff(before, after) {
+    return !!before && after === false;
+}
+/**
+ * 승인된 지금 **상신 때 굳힌 것을 그대로 할 수 있는가** — 할 수 없으면 그 사유.
+ *
+ * `standing` 은 콜백이 **상신 때 굳힌 id 로** 다시 읽은 spec 이다. boardId 로 다시 찾지 않는다 — 그
+ * 사이 지우고 새로 만든 spec 은 결재자가 본 것이 아니다.
+ */
+function whyNotWithdraw(standing) {
+    if (!standing) {
+        return 'control-withdrawal-spec-gone';
+    }
+    if (!standing.controlled) {
+        return 'control-already-off';
+    }
+    return undefined;
+}
+/**
+ * 되돌릴 수 있는가 — **방식마다 다르다.**
+ *
+ * 끄는 것은 다시 켤 수 있다. 다만 꺼져 있던 동안 서명 없이 나간 판은 되돌아오지 않는다. 지우는 것은
+ * 흐름·요구 축·통제 표시가 함께 사라져 되돌릴 길이 없다 — 다시 만드는 것은 새로 짓는 일이다.
+ */
+function withdrawalReversibility(action) {
+    return {
+        reversible: exports.WITHDRAWAL_REVERSIBILITY[action] === 'reversible',
+        caveat: action === 'delete'
+            ? '결재 기록에 남은 화면 설정으로 다시 세울 수 있습니다. 통제를 다시 켜는 것도 결재를 거칩니다.'
+            : '통제는 다시 켤 수 있습니다. 꺼져 있는 동안 서명 없이 발행된 버전은 되돌아오지 않습니다.'
+    };
+}
+/** 상신 이름 — 읽는 쪽과 올리는 쪽이 같은 이름을 써야 겹친 상신을 찾는다. */
+function controlWithdrawalRequestName(boardId) {
+    return `통제 해제 승인 ${boardId}`;
+}
+/**
+ * 올려도 되는가 — **안 되면 던진다.** 리졸버에는 조건이 없고 이 함수를 부르기만 한다.
+ *
+ * ── 왜 판단이 던지나 ───────────────────────────────────────────────────────
+ * 리졸버에 `if (refusal) throw` 를 두면, 그 조건이 죽어도(`if (false && …)`) 글자는 남는다. 글자로
+ * 문을 세는 분류기(`irreversible-doors-refuse.test.ts`)는 그것을 「거절한다」로 읽는다 — 거절하는 글자가
+ * 있는지를 셀 뿐 거절이 **도는지**는 못 본다. 그 층은 거동 시험이 맡는다
+ * (`station-screen-control-withdrawal.test.ts`, 아키텍트 2026-09-17). 조건을 이 함수 하나에 모아야 거동
+ * 시험이 부르는 것이 곧 상신이 부르는 것이 된다.
+ */
+function assertWithdrawalRaisable(reading) {
+    if (!reading.reason?.trim()) {
+        throw new shell_1.Refusal('control-withdrawal-reason-missing', {}, 'enter the reason for withdrawing control.');
+    }
+    if (!reading.spec) {
+        throw new shell_1.Refusal('station-spec-missing', {}, 'the screen settings were not found.');
+    }
+    if (!reading.spec.controlled) {
+        throw new shell_1.Refusal('control-not-on', {}, 'this screen is not a controlled document.');
+    }
+    if (reading.waiting) {
+        throw new shell_1.Refusal('control-withdrawal-already-raised', {}, 'a control withdrawal for this screen is already awaiting approval.');
+    }
+    if (!reading.installed) {
+        throw new shell_1.Refusal('control-withdrawal-door-missing', {}, 'the control withdrawal approval form is not installed in this plant.');
+    }
+    const refusal = reading.line.refusal;
+    if (!refusal) {
+        return;
+    }
+    /* The line is the screen release line, judged by the same function as turning control on (ADR-0047 ②). */
+    throw (0, worklist_1.approvalLineRefusal)(refusal);
+}
+/** The settings' content columns — what a person needs to set the same screen up again. */
+exports.STATION_SCREEN_SPEC_CONTENT = ['boardId', 'requires', 'target', 'controlled', 'kind', 'flow'];
+/**
+ * The settings as they were before deletion, carried in the approval record. It is what makes the delete
+ * branch reversible: the flow, read axes and control mark stay readable after the row is gone
+ * (ADR-0064, condition ③ for `reversible`).
+ */
+function stationScreenSpecBefore(spec) {
+    return Object.fromEntries(exports.STATION_SCREEN_SPEC_CONTENT.map(column => [column, spec[column] ?? null]));
+}
+//# sourceMappingURL=station-screen-control-withdrawal.js.map

package/dist-server/service/station/station-screen-control-withdrawal.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"station-screen-control-withdrawal.js","sourceRoot":"","sources":["../../../server/service/station/station-screen-control-withdrawal.ts"],"names":[],"mappings":";AAAA;;;;;;;;;;;;;;;;;;GAkBG;;;AAuCH,0CAEC;AAQD,wCAYC;AAQD,0DAQC;AAGD,oEAEC;AAwBD,4DA6BC;AAUD,0DAEC;AAjJD,uDAAyF;AACzF,iDAAmE;AAEnE,wCAAwC;AAC3B,QAAA,0BAA0B,GAAG,CAAC,UAAU,EAAE,QAAQ,CAAU,CAAA;AAIzE;;;;;GAKG;AACU,QAAA,wBAAwB,GAAmD;IACtF,UAAU,EAAE,YAAY;IACxB,MAAM,EAAE,YAAY;CACrB,CAAA;AAcD;;;;;GAKG;AACH,SAAgB,eAAe,CAAC,MAAkC,EAAE,KAAiC;IACnG,OAAO,CAAC,CAAC,MAAM,IAAI,KAAK,KAAK,KAAK,CAAA;AACpC,CAAC;AAED;;;;;GAKG;AACH,SAAgB,cAAc,CAC5B,QAA4D;IAE5D,IAAI,CAAC,QAAQ,EAAE,CAAC;QACd,OAAO,8BAA8B,CAAA;IACvC,CAAC;IAED,IAAI,CAAC,QAAQ,CAAC,UAAU,EAAE,CAAC;QACzB,OAAO,qBAAqB,CAAA;IAC9B,CAAC;IAED,OAAO,SAAS,CAAA;AAClB,CAAC;AAED;;;;;GAKG;AACH,SAAgB,uBAAuB,CAAC,MAA+B;IACrE,OAAO;QACL,UAAU,EAAE,gCAAwB,CAAC,MAAM,CAAC,KAAK,YAAY;QAC7D,MAAM,EACJ,MAAM,KAAK,QAAQ;YACjB,CAAC,CAAC,wDAAwD;YAC1D,CAAC,CAAC,qDAAqD;KAC5D,CAAA;AACH,CAAC;AAED,iDAAiD;AACjD,SAAgB,4BAA4B,CAAC,OAAe;IAC1D,OAAO,YAAY,OAAO,EAAE,CAAA;AAC9B,CAAC;AAcD;;;;;;;;;GASG;AACH,SAAgB,wBAAwB,CAAC,OAA+B;IACtE,IAAI,CAAC,OAAO,CAAC,MAAM,EAAE,IAAI,EAAE,EAAE,CAAC;QAC5B,MAAM,IAAI,eAAO,CAAC,mCAAmC,EAAE,EAAE,EAAE,2CAA2C,CAAC,CAAA;IACzG,CAAC;IAED,IAAI,CAAC,OAAO,CAAC,IAAI,EAAE,CAAC;QAClB,MAAM,IAAI,eAAO,CAAC,sBAAsB,EAAE,EAAE,EAAE,qCAAqC,CAAC,CAAA;IACtF,CAAC;IAED,IAAI,CAAC,OAAO,CAAC,IAAI,CAAC,UAAU,EAAE,CAAC;QAC7B,MAAM,IAAI,eAAO,CAAC,gBAAgB,EAAE,EAAE,EAAE,2CAA2C,CAAC,CAAA;IACtF,CAAC;IAED,IAAI,OAAO,CAAC,OAAO,EAAE,CAAC;QACpB,MAAM,IAAI,eAAO,CAAC,mCAAmC,EAAE,EAAE,EAAE,oEAAoE,CAAC,CAAA;IAClI,CAAC;IAED,IAAI,CAAC,OAAO,CAAC,SAAS,EAAE,CAAC;QACvB,MAAM,IAAI,eAAO,CAAC,iCAAiC,EAAE,EAAE,EAAE,sEAAsE,CAAC,CAAA;IAClI,CAAC;IAED,MAAM,OAAO,GAAG,OAAO,CAAC,IAAI,CAAC,OAAO,CAAA;IAEpC,IAAI,CAAC,OAAO,EAAE,CAAC;QACb,OAAM;IACR,CAAC;IAED,0GAA0G;IAC1G,MAAM,IAAA,8BAAmB,EAAC,OAAO,CAAC,CAAA;AACpC,CAAC;AAED,2FAA2F;AAC9E,QAAA,2BAA2B,GAAG,CAAC,SAAS,EAAE,UAAU,EAAE,QAAQ,EAAE,YAAY,EAAE,MAAM,EAAE,MAAM,CAAU,CAAA;AAEnH;;;;GAIG;AACH,SAAgB,uBAAuB,CAAC,IAA4E;IAClH,OAAO,MAAM,CAAC,WAAW,CAAC,mCAA2B,CAAC,GAAG,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC,MAAM,EAAE,IAAI,CAAC,MAAM,CAAC,IAAI,IAAI,CAAC,CAAC,CAAC,CAAA;AACtG,CAAC","sourcesContent":["/**\n * **통제 문서의 통제를 거두는 일** — 켜는 것만 막고 끄는 것을 열어 두면 통제가 한 방향으로만 선다.\n *\n * ═══════════════════════════════════════════════════════════════════════════\n * ── 무엇이 열려 있었나 ─────────────────────────────────────────────────────\n * 통제를 **켤 때**는 결재선이 있어야 했다(`turnsControlOn`). 그런데 `controlled: false` 로 저장하거나\n * spec 을 지우는 데는 관문이 없었고, 발행 관문은 통제가 아닌 화면을 그대로 통과시킨다\n * (`station-screen-publish-subscriber.ts` — `if (!spec?.controlled) return`). 그래서 화면을 만드는\n * 권한만 든 작성자가 통제를 끄고 **서명 없는 도안을 발행**할 수 있었다.\n *\n * 판정(ADR-0047 ⑨): **결재로 세운 것은 결재로 거둔다.** 통제를 끄는 것과 통제 중인 spec 을 지우는\n * 것은 발행 승인과 **같은 결재선**을 지난다. 끄는 것이 결재를 지났다면 발행 관문의 그 return 은\n * 정당하다 — 그래서 관문은 그대로 둔다.\n *\n * ── 여기 있는 것 ──────────────────────────────────────────────────────────\n * 판단만 둔다. DB 를 읽는 것은 부르는 쪽의 일이다 — 이 판단이 틀리면 통제 문서가 뚫리는데, 그것을\n * 확인하는 시험이 DB·보드·spec·결재를 다 세운 뒤에야 물을 수 있으면 안 묻게 된다.\n * ═══════════════════════════════════════════════════════════════════════════\n */\n\nimport { approvalLineRefusal, type ApprovalLineStanding } from '@things-factory/worklist'\nimport { Refusal, type Reversibility } from '@things-factory/shell'\n\n/** 거두는 방식 둘 — 상신 때 정하고, 승인 때 그대로 한다. */\nexport const CONTROL_WITHDRAWAL_ACTIONS = ['turn-off', 'delete'] as const\n\nexport type ControlWithdrawalAction = (typeof CONTROL_WITHDRAWAL_ACTIONS)[number]\n\n/**\n * Both are reversible (ADR-0064, conditions for `reversible`): turning control on again and saving the\n * settings again are the paired operations, releases are kept by board and not by the settings row's id,\n * and the delete raise carries the settings as they were (`stationScreenSpecBefore`), so the approval\n * record holds what to set up again.\n */\nexport const WITHDRAWAL_REVERSIBILITY: Record<ControlWithdrawalAction, Reversibility> = {\n  'turn-off': 'reversible',\n  delete: 'reversible'\n}\n\n/**\n * 승인 콜백이 **하지 않고 끝내는** 사유.\n *\n * 상신과 승인 사이에 그 spec 이 바뀔 수 있다. 콜백은 상신 때 굳힌 것만 하고, 그 사이 들어온 변경을\n * 덮지 않는다 — 그러면 조용히 성공하는 대신 이 코드로 멈춘다.\n */\nexport type ControlWithdrawalRefusal =\n  /** 상신 때 가리킨 spec 이 이제 없다. */\n  | 'control-withdrawal-spec-gone'\n  /** 그 spec 은 이미 통제가 아니다 — 거둘 것이 없다. */\n  | 'control-already-off'\n\n/**\n * 이 저장이 통제를 **끄는** 저장인가.\n *\n * `after` 가 비어 있으면 끄는 것이 아니다 — 흐름만 저장하는 요청은 `controlled` 를 안 싣는다\n * (§`saveStationScreenSpec`). 그것을 끄는 것으로 읽으면 통제 문서를 고칠 수조차 없게 된다.\n */\nexport function turnsControlOff(before: boolean | null | undefined, after: boolean | null | undefined): boolean {\n  return !!before && after === false\n}\n\n/**\n * 승인된 지금 **상신 때 굳힌 것을 그대로 할 수 있는가** — 할 수 없으면 그 사유.\n *\n * `standing` 은 콜백이 **상신 때 굳힌 id 로** 다시 읽은 spec 이다. boardId 로 다시 찾지 않는다 — 그\n * 사이 지우고 새로 만든 spec 은 결재자가 본 것이 아니다.\n */\nexport function whyNotWithdraw(\n  standing: { controlled?: boolean | null } | null | undefined\n): ControlWithdrawalRefusal | undefined {\n  if (!standing) {\n    return 'control-withdrawal-spec-gone'\n  }\n\n  if (!standing.controlled) {\n    return 'control-already-off'\n  }\n\n  return undefined\n}\n\n/**\n * 되돌릴 수 있는가 — **방식마다 다르다.**\n *\n * 끄는 것은 다시 켤 수 있다. 다만 꺼져 있던 동안 서명 없이 나간 판은 되돌아오지 않는다. 지우는 것은\n * 흐름·요구 축·통제 표시가 함께 사라져 되돌릴 길이 없다 — 다시 만드는 것은 새로 짓는 일이다.\n */\nexport function withdrawalReversibility(action: ControlWithdrawalAction): { reversible: boolean; caveat: string } {\n  return {\n    reversible: WITHDRAWAL_REVERSIBILITY[action] === 'reversible',\n    caveat:\n      action === 'delete'\n        ? '결재 기록에 남은 화면 설정으로 다시 세울 수 있습니다. 통제를 다시 켜는 것도 결재를 거칩니다.'\n        : '통제는 다시 켤 수 있습니다. 꺼져 있는 동안 서명 없이 발행된 버전은 되돌아오지 않습니다.'\n  }\n}\n\n/** 상신 이름 — 읽는 쪽과 올리는 쪽이 같은 이름을 써야 겹친 상신을 찾는다. */\nexport function controlWithdrawalRequestName(boardId: string): string {\n  return `통제 해제 승인 ${boardId}`\n}\n\n/** 올릴 때 본 것 — 읽는 것은 리졸버가 하고, 이 판단은 DB 를 모른다. */\nexport interface WithdrawalRaiseReading {\n  reason?: string | null\n  spec?: { controlled?: boolean | null } | null\n  /** 같은 화면의 해제가 이미 결재 중인가. */\n  waiting: boolean\n  /** 통제 해제 승인 양식이 이 공장에 섰나. */\n  installed: boolean\n  /** **화면 발행 승인**의 결재선 판정 — 켤 때와 같은 함수가 낸 것(`controlLineStanding`). */\n  line: ApprovalLineStanding\n}\n\n/**\n * 올려도 되는가 — **안 되면 던진다.** 리졸버에는 조건이 없고 이 함수를 부르기만 한다.\n *\n * ── 왜 판단이 던지나 ───────────────────────────────────────────────────────\n * 리졸버에 `if (refusal) throw` 를 두면, 그 조건이 죽어도(`if (false && …)`) 글자는 남는다. 글자로\n * 문을 세는 분류기(`irreversible-doors-refuse.test.ts`)는 그것을 「거절한다」로 읽는다 — 거절하는 글자가\n * 있는지를 셀 뿐 거절이 **도는지**는 못 본다. 그 층은 거동 시험이 맡는다\n * (`station-screen-control-withdrawal.test.ts`, 아키텍트 2026-09-17). 조건을 이 함수 하나에 모아야 거동\n * 시험이 부르는 것이 곧 상신이 부르는 것이 된다.\n */\nexport function assertWithdrawalRaisable(reading: WithdrawalRaiseReading): void {\n  if (!reading.reason?.trim()) {\n    throw new Refusal('control-withdrawal-reason-missing', {}, 'enter the reason for withdrawing control.')\n  }\n\n  if (!reading.spec) {\n    throw new Refusal('station-spec-missing', {}, 'the screen settings were not found.')\n  }\n\n  if (!reading.spec.controlled) {\n    throw new Refusal('control-not-on', {}, 'this screen is not a controlled document.')\n  }\n\n  if (reading.waiting) {\n    throw new Refusal('control-withdrawal-already-raised', {}, 'a control withdrawal for this screen is already awaiting approval.')\n  }\n\n  if (!reading.installed) {\n    throw new Refusal('control-withdrawal-door-missing', {}, 'the control withdrawal approval form is not installed in this plant.')\n  }\n\n  const refusal = reading.line.refusal\n\n  if (!refusal) {\n    return\n  }\n\n  /* The line is the screen release line, judged by the same function as turning control on (ADR-0047 ②). */\n  throw approvalLineRefusal(refusal)\n}\n\n/** The settings' content columns — what a person needs to set the same screen up again. */\nexport const STATION_SCREEN_SPEC_CONTENT = ['boardId', 'requires', 'target', 'controlled', 'kind', 'flow'] as const\n\n/**\n * The settings as they were before deletion, carried in the approval record. It is what makes the delete\n * branch reversible: the flow, read axes and control mark stay readable after the row is gone\n * (ADR-0064, condition ③ for `reversible`).\n */\nexport function stationScreenSpecBefore(spec: Partial<Record<(typeof STATION_SCREEN_SPEC_CONTENT)[number], unknown>>) {\n  return Object.fromEntries(STATION_SCREEN_SPEC_CONTENT.map(column => [column, spec[column] ?? null]))\n}\n"]}

package/dist-server/service/station/station-screen-draft-resolver.d.ts

@@ -0,0 +1,47 @@
+import type { StationFlow } from './station-flow';
+export declare class StationScreenScoreDimensionType {
+    key: string;
+    score: number;
+    max: number;
+    evidence: string;
+}
+export declare class StationScreenScorecardType {
+    score: number;
+    grade: string;
+    blockers: string[];
+    dimensions: StationScreenScoreDimensionType[];
+}
+export declare class StationFlowProblem {
+    level: string;
+    stepId?: string;
+    field?: string;
+    code: string;
+    params?: Record<string, string>;
+    says: string;
+}
+export declare class StationScreenDraft {
+    model: string;
+    requires: string[];
+    problems: StationFlowProblem[];
+    scorecard: StationScreenScorecardType;
+}
+/**
+ * What a flow would draw — **asked before it is saved.**
+ *
+ * ── Why the server draws the preview ──────────────────────────────────────
+ * The seed lays screens out with `screenModel`, and so does saving. If the composer laid its own
+ * preview out in the browser there would be two calculators, and the day they part the author sees
+ * one screen while the plant gets another. That kind of difference does not announce itself — it
+ * shows up as an operator saying the button moved.
+ *
+ * So the composer sends the flow and gets back exactly what would be stored.
+ *
+ * ── The checks ride along ─────────────────────────────────────────────────
+ * `checkFlow` runs here for the same reason, and because the author should not have to press save
+ * to find out that a required argument has nowhere to come from.
+ *
+ * There is no repository here and nothing is written. The whole answer is `draftScreen`.
+ */
+export declare class StationScreenDraftResolver {
+    stationScreenDraft(flow: StationFlow): Promise<StationScreenDraft>;
+}

package/dist-server/service/station/station-screen-draft-resolver.js

@@ -0,0 +1,153 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.StationScreenDraftResolver = exports.StationScreenDraft = exports.StationFlowProblem = exports.StationScreenScorecardType = exports.StationScreenScoreDimensionType = void 0;
+const tslib_1 = require("tslib");
+const type_graphql_1 = require("type-graphql");
+const shell_1 = require("@things-factory/shell");
+const station_screen_layout_1 = require("./station-screen-layout");
+const station_screen_scorecard_1 = require("./station-screen-scorecard");
+let StationScreenScoreDimensionType = class StationScreenScoreDimensionType {
+};
+exports.StationScreenScoreDimensionType = StationScreenScoreDimensionType;
+tslib_1.__decorate([
+    (0, type_graphql_1.Field)(),
+    tslib_1.__metadata("design:type", String)
+], StationScreenScoreDimensionType.prototype, "key", void 0);
+tslib_1.__decorate([
+    (0, type_graphql_1.Field)(),
+    tslib_1.__metadata("design:type", Number)
+], StationScreenScoreDimensionType.prototype, "score", void 0);
+tslib_1.__decorate([
+    (0, type_graphql_1.Field)(),
+    tslib_1.__metadata("design:type", Number)
+], StationScreenScoreDimensionType.prototype, "max", void 0);
+tslib_1.__decorate([
+    (0, type_graphql_1.Field)(),
+    tslib_1.__metadata("design:type", String)
+], StationScreenScoreDimensionType.prototype, "evidence", void 0);
+exports.StationScreenScoreDimensionType = StationScreenScoreDimensionType = tslib_1.__decorate([
+    (0, type_graphql_1.ObjectType)({ description: 'one evidence-bound dimension of a station screen scorecard' })
+], StationScreenScoreDimensionType);
+let StationScreenScorecardType = class StationScreenScorecardType {
+};
+exports.StationScreenScorecardType = StationScreenScorecardType;
+tslib_1.__decorate([
+    (0, type_graphql_1.Field)(),
+    tslib_1.__metadata("design:type", Number)
+], StationScreenScorecardType.prototype, "score", void 0);
+tslib_1.__decorate([
+    (0, type_graphql_1.Field)(),
+    tslib_1.__metadata("design:type", String)
+], StationScreenScorecardType.prototype, "grade", void 0);
+tslib_1.__decorate([
+    (0, type_graphql_1.Field)(type => [String]),
+    tslib_1.__metadata("design:type", Array)
+], StationScreenScorecardType.prototype, "blockers", void 0);
+tslib_1.__decorate([
+    (0, type_graphql_1.Field)(type => [StationScreenScoreDimensionType]),
+    tslib_1.__metadata("design:type", Array)
+], StationScreenScorecardType.prototype, "dimensions", void 0);
+exports.StationScreenScorecardType = StationScreenScorecardType = tslib_1.__decorate([
+    (0, type_graphql_1.ObjectType)({ description: 'quality evidence for this screen draft; it is recomputed by the server' })
+], StationScreenScorecardType);
+let StationFlowProblem = class StationFlowProblem {
+};
+exports.StationFlowProblem = StationFlowProblem;
+tslib_1.__decorate([
+    (0, type_graphql_1.Field)({ description: "'error' — this will not work · 'warning' — this will work and mislead" }),
+    tslib_1.__metadata("design:type", String)
+], StationFlowProblem.prototype, "level", void 0);
+tslib_1.__decorate([
+    (0, type_graphql_1.Field)({ nullable: true, description: 'the step it is about' }),
+    tslib_1.__metadata("design:type", String)
+], StationFlowProblem.prototype, "stepId", void 0);
+tslib_1.__decorate([
+    (0, type_graphql_1.Field)({ nullable: true, description: 'the service field it is about' }),
+    tslib_1.__metadata("design:type", String)
+], StationFlowProblem.prototype, "field", void 0);
+tslib_1.__decorate([
+    (0, type_graphql_1.Field)({ description: "which check this is — the screen says it in the reader's language" }),
+    tslib_1.__metadata("design:type", String)
+], StationFlowProblem.prototype, "code", void 0);
+tslib_1.__decorate([
+    (0, type_graphql_1.Field)(type => shell_1.ScalarObject, { nullable: true, description: 'values to fill into that sentence' }),
+    tslib_1.__metadata("design:type", Object)
+], StationFlowProblem.prototype, "params", void 0);
+tslib_1.__decorate([
+    (0, type_graphql_1.Field)({ description: 'the same thing in Korean, for logs and the scenario tool — not for the screen' }),
+    tslib_1.__metadata("design:type", String)
+], StationFlowProblem.prototype, "says", void 0);
+exports.StationFlowProblem = StationFlowProblem = tslib_1.__decorate([
+    (0, type_graphql_1.ObjectType)({ description: 'something the author should know before this flow goes in front of an operator' })
+], StationFlowProblem);
+let StationScreenDraft = class StationScreenDraft {
+};
+exports.StationScreenDraft = StationScreenDraft;
+tslib_1.__decorate([
+    (0, type_graphql_1.Field)({ description: 'the board model the flow lays out' }),
+    tslib_1.__metadata("design:type", String)
+], StationScreenDraft.prototype, "model", void 0);
+tslib_1.__decorate([
+    (0, type_graphql_1.Field)(type => [String], { description: 'station context axes the drawing would read' }),
+    tslib_1.__metadata("design:type", Array)
+], StationScreenDraft.prototype, "requires", void 0);
+tslib_1.__decorate([
+    (0, type_graphql_1.Field)(type => [StationFlowProblem], { description: 'what the author should know' }),
+    tslib_1.__metadata("design:type", Array)
+], StationScreenDraft.prototype, "problems", void 0);
+tslib_1.__decorate([
+    (0, type_graphql_1.Field)(type => StationScreenScorecardType, { description: 'server-derived quality evidence for this draft' }),
+    tslib_1.__metadata("design:type", StationScreenScorecardType)
+], StationScreenDraft.prototype, "scorecard", void 0);
+exports.StationScreenDraft = StationScreenDraft = tslib_1.__decorate([
+    (0, type_graphql_1.ObjectType)({ description: 'what this flow would draw, without saving anything' })
+], StationScreenDraft);
+/**
+ * What a flow would draw — **asked before it is saved.**
+ *
+ * ── Why the server draws the preview ──────────────────────────────────────
+ * The seed lays screens out with `screenModel`, and so does saving. If the composer laid its own
+ * preview out in the browser there would be two calculators, and the day they part the author sees
+ * one screen while the plant gets another. That kind of difference does not announce itself — it
+ * shows up as an operator saying the button moved.
+ *
+ * So the composer sends the flow and gets back exactly what would be stored.
+ *
+ * ── The checks ride along ─────────────────────────────────────────────────
+ * `checkFlow` runs here for the same reason, and because the author should not have to press save
+ * to find out that a required argument has nowhere to come from.
+ *
+ * There is no repository here and nothing is written. The whole answer is `draftScreen`.
+ */
+let StationScreenDraftResolver = class StationScreenDraftResolver {
+    async stationScreenDraft(flow) {
+        const drafted = (0, station_screen_layout_1.draftScreen)(flow);
+        return {
+            model: drafted.model,
+            requires: drafted.requires,
+            problems: drafted.problems.map(problem => ({
+                level: problem.level,
+                stepId: problem.stepId,
+                field: problem.field,
+                code: problem.code,
+                params: problem.params,
+                says: problem.says
+            })),
+            scorecard: (0, station_screen_scorecard_1.inspectStationScreen)(flow, drafted.problems)
+        };
+    }
+};
+exports.StationScreenDraftResolver = StationScreenDraftResolver;
+tslib_1.__decorate([
+    (0, type_graphql_1.Directive)('@privilege(category: "station", privilege: "query", domainOwnerGranted: true)'),
+    (0, type_graphql_1.Query)(returns => StationScreenDraft, { description: 'lay out a flow without saving it' }),
+    tslib_1.__param(0, (0, type_graphql_1.Arg)('flow', type => shell_1.ScalarObject)),
+    tslib_1.__metadata("design:type", Function),
+    tslib_1.__metadata("design:paramtypes", [Object]),
+    tslib_1.__metadata("design:returntype", Promise)
+], StationScreenDraftResolver.prototype, "stationScreenDraft", null);
+exports.StationScreenDraftResolver = StationScreenDraftResolver = tslib_1.__decorate([
+    (0, type_graphql_1.Resolver)(),
+    (0, type_graphql_1.UseMiddleware)(shell_1.SpeakRefusals)
+], StationScreenDraftResolver);
+//# sourceMappingURL=station-screen-draft-resolver.js.map

package/dist-server/service/station/station-screen-draft-resolver.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"station-screen-draft-resolver.js","sourceRoot":"","sources":["../../../server/service/station/station-screen-draft-resolver.ts"],"names":[],"mappings":";;;;AAAA,+CAAgG;AAEhG,iDAAmE;AAGnE,mEAAqD;AACrD,yEAAiE;AAG1D,IAAM,+BAA+B,GAArC,MAAM,+BAA+B;CAY3C,CAAA;AAZY,0EAA+B;AAE1C;IADC,IAAA,oBAAK,GAAE;;4DACG;AAGX;IADC,IAAA,oBAAK,GAAE;;8DACK;AAGb;IADC,IAAA,oBAAK,GAAE;;4DACG;AAGX;IADC,IAAA,oBAAK,GAAE;;iEACQ;0CAXL,+BAA+B;IAD3C,IAAA,yBAAU,EAAC,EAAE,WAAW,EAAE,4DAA4D,EAAE,CAAC;GAC7E,+BAA+B,CAY3C;AAGM,IAAM,0BAA0B,GAAhC,MAAM,0BAA0B;CAYtC,CAAA;AAZY,gEAA0B;AAErC;IADC,IAAA,oBAAK,GAAE;;yDACK;AAGb;IADC,IAAA,oBAAK,GAAE;;yDACK;AAGb;IADC,IAAA,oBAAK,EAAC,IAAI,CAAC,EAAE,CAAC,CAAC,MAAM,CAAC,CAAC;;4DACN;AAGlB;IADC,IAAA,oBAAK,EAAC,IAAI,CAAC,EAAE,CAAC,CAAC,+BAA+B,CAAC,CAAC;;8DACJ;qCAXlC,0BAA0B;IADtC,IAAA,yBAAU,EAAC,EAAE,WAAW,EAAE,wEAAwE,EAAE,CAAC;GACzF,0BAA0B,CAYtC;AAGM,IAAM,kBAAkB,GAAxB,MAAM,kBAAkB;CAkB9B,CAAA;AAlBY,gDAAkB;AAE7B;IADC,IAAA,oBAAK,EAAC,EAAE,WAAW,EAAE,uEAAuE,EAAE,CAAC;;iDACnF;AAGb;IADC,IAAA,oBAAK,EAAC,EAAE,QAAQ,EAAE,IAAI,EAAE,WAAW,EAAE,sBAAsB,EAAE,CAAC;;kDAChD;AAGf;IADC,IAAA,oBAAK,EAAC,EAAE,QAAQ,EAAE,IAAI,EAAE,WAAW,EAAE,+BAA+B,EAAE,CAAC;;iDAC1D;AAGd;IADC,IAAA,oBAAK,EAAC,EAAE,WAAW,EAAE,mEAAmE,EAAE,CAAC;;gDAChF;AAGZ;IADC,IAAA,oBAAK,EAAC,IAAI,CAAC,EAAE,CAAC,oBAAY,EAAE,EAAE,QAAQ,EAAE,IAAI,EAAE,WAAW,EAAE,mCAAmC,EAAE,CAAC;;kDACnE;AAG/B;IADC,IAAA,oBAAK,EAAC,EAAE,WAAW,EAAE,+EAA+E,EAAE,CAAC;;gDAC5F;6BAjBD,kBAAkB;IAD9B,IAAA,yBAAU,EAAC,EAAE,WAAW,EAAE,gFAAgF,EAAE,CAAC;GACjG,kBAAkB,CAkB9B;AAGM,IAAM,kBAAkB,GAAxB,MAAM,kBAAkB;CAY9B,CAAA;AAZY,gDAAkB;AAE7B;IADC,IAAA,oBAAK,EAAC,EAAE,WAAW,EAAE,mCAAmC,EAAE,CAAC;;iDAC/C;AAGb;IADC,IAAA,oBAAK,EAAC,IAAI,CAAC,EAAE,CAAC,CAAC,MAAM,CAAC,EAAE,EAAE,WAAW,EAAE,6CAA6C,EAAE,CAAC;;oDACtE;AAGlB;IADC,IAAA,oBAAK,EAAC,IAAI,CAAC,EAAE,CAAC,CAAC,kBAAkB,CAAC,EAAE,EAAE,WAAW,EAAE,6BAA6B,EAAE,CAAC;;oDACtD;AAG9B;IADC,IAAA,oBAAK,EAAC,IAAI,CAAC,EAAE,CAAC,0BAA0B,EAAE,EAAE,WAAW,EAAE,gDAAgD,EAAE,CAAC;sCAClG,0BAA0B;qDAAA;6BAX1B,kBAAkB;IAD9B,IAAA,yBAAU,EAAC,EAAE,WAAW,EAAE,oDAAoD,EAAE,CAAC;GACrE,kBAAkB,CAY9B;AAED;;;;;;;;;;;;;;;;GAgBG;AAGI,IAAM,0BAA0B,GAAhC,MAAM,0BAA0B;IAG/B,AAAN,KAAK,CAAC,kBAAkB,CAAoC,IAAiB;QAC3E,MAAM,OAAO,GAAG,IAAA,mCAAW,EAAC,IAAI,CAAC,CAAA;QAEjC,OAAO;YACL,KAAK,EAAE,OAAO,CAAC,KAAK;YACpB,QAAQ,EAAE,OAAO,CAAC,QAAQ;YAC1B,QAAQ,EAAE,OAAO,CAAC,QAAQ,CAAC,GAAG,CAAC,OAAO,CAAC,EAAE,CAAC,CAAC;gBACzC,KAAK,EAAE,OAAO,CAAC,KAAK;gBACpB,MAAM,EAAE,OAAO,CAAC,MAAM;gBACtB,KAAK,EAAE,OAAO,CAAC,KAAK;gBACpB,IAAI,EAAE,OAAO,CAAC,IAAI;gBAClB,MAAM,EAAE,OAAO,CAAC,MAAM;gBACtB,IAAI,EAAE,OAAO,CAAC,IAAI;aACnB,CAAC,CAAC;YACH,SAAS,EAAE,IAAA,+CAAoB,EAAC,IAAI,EAAE,OAAO,CAAC,QAAQ,CAAC;SACxD,CAAA;IACH,CAAC;CACF,CAAA;AApBY,gEAA0B;AAG/B;IAFL,IAAA,wBAAS,EAAC,+EAA+E,CAAC;IAC1F,IAAA,oBAAK,EAAC,OAAO,CAAC,EAAE,CAAC,kBAAkB,EAAE,EAAE,WAAW,EAAE,kCAAkC,EAAE,CAAC;IAChE,mBAAA,IAAA,kBAAG,EAAC,MAAM,EAAE,IAAI,CAAC,EAAE,CAAC,oBAAY,CAAC,CAAA;;;;oEAgB1D;qCAnBU,0BAA0B;IAFtC,IAAA,uBAAQ,GAAE;IACV,IAAA,4BAAa,EAAC,qBAAa,CAAC;GAChB,0BAA0B,CAoBtC","sourcesContent":["import { Arg, Directive, Field, ObjectType, Query, Resolver, UseMiddleware } from 'type-graphql'\n\nimport { ScalarObject, SpeakRefusals } from '@things-factory/shell'\n\nimport type { StationFlow } from './station-flow'\nimport { draftScreen } from './station-screen-layout'\nimport { inspectStationScreen } from './station-screen-scorecard'\n\n@ObjectType({ description: 'one evidence-bound dimension of a station screen scorecard' })\nexport class StationScreenScoreDimensionType {\n  @Field()\n  key: string\n\n  @Field()\n  score: number\n\n  @Field()\n  max: number\n\n  @Field()\n  evidence: string\n}\n\n@ObjectType({ description: 'quality evidence for this screen draft; it is recomputed by the server' })\nexport class StationScreenScorecardType {\n  @Field()\n  score: number\n\n  @Field()\n  grade: string\n\n  @Field(type => [String])\n  blockers: string[]\n\n  @Field(type => [StationScreenScoreDimensionType])\n  dimensions: StationScreenScoreDimensionType[]\n}\n\n@ObjectType({ description: 'something the author should know before this flow goes in front of an operator' })\nexport class StationFlowProblem {\n  @Field({ description: \"'error' — this will not work · 'warning' — this will work and mislead\" })\n  level: string\n\n  @Field({ nullable: true, description: 'the step it is about' })\n  stepId?: string\n\n  @Field({ nullable: true, description: 'the service field it is about' })\n  field?: string\n\n  @Field({ description: \"which check this is — the screen says it in the reader's language\" })\n  code: string\n\n  @Field(type => ScalarObject, { nullable: true, description: 'values to fill into that sentence' })\n  params?: Record<string, string>\n\n  @Field({ description: 'the same thing in Korean, for logs and the scenario tool — not for the screen' })\n  says: string\n}\n\n@ObjectType({ description: 'what this flow would draw, without saving anything' })\nexport class StationScreenDraft {\n  @Field({ description: 'the board model the flow lays out' })\n  model: string\n\n  @Field(type => [String], { description: 'station context axes the drawing would read' })\n  requires: string[]\n\n  @Field(type => [StationFlowProblem], { description: 'what the author should know' })\n  problems: StationFlowProblem[]\n\n  @Field(type => StationScreenScorecardType, { description: 'server-derived quality evidence for this draft' })\n  scorecard: StationScreenScorecardType\n}\n\n/**\n * What a flow would draw — **asked before it is saved.**\n *\n * ── Why the server draws the preview ──────────────────────────────────────\n * The seed lays screens out with `screenModel`, and so does saving. If the composer laid its own\n * preview out in the browser there would be two calculators, and the day they part the author sees\n * one screen while the plant gets another. That kind of difference does not announce itself — it\n * shows up as an operator saying the button moved.\n *\n * So the composer sends the flow and gets back exactly what would be stored.\n *\n * ── The checks ride along ─────────────────────────────────────────────────\n * `checkFlow` runs here for the same reason, and because the author should not have to press save\n * to find out that a required argument has nowhere to come from.\n *\n * There is no repository here and nothing is written. The whole answer is `draftScreen`.\n */\n@Resolver()\n@UseMiddleware(SpeakRefusals)\nexport class StationScreenDraftResolver {\n  @Directive('@privilege(category: \"station\", privilege: \"query\", domainOwnerGranted: true)')\n  @Query(returns => StationScreenDraft, { description: 'lay out a flow without saving it' })\n  async stationScreenDraft(@Arg('flow', type => ScalarObject) flow: StationFlow): Promise<StationScreenDraft> {\n    const drafted = draftScreen(flow)\n\n    return {\n      model: drafted.model,\n      requires: drafted.requires,\n      problems: drafted.problems.map(problem => ({\n        level: problem.level,\n        stepId: problem.stepId,\n        field: problem.field,\n        code: problem.code,\n        params: problem.params,\n        says: problem.says\n      })),\n      scorecard: inspectStationScreen(flow, drafted.problems)\n    }\n  }\n}\n"]}

package/dist-server/service/station/station-screen-layout.d.ts

@@ -0,0 +1,119 @@
+import type { StationFlow, StationProblem } from './station-flow';
+/**
+ * 부품 목록 → things-scene 모델. **자리는 여기서 계산한다.**
+ *
+ * ── 왜 아무도 좌표를 안 드나 ───────────────────────────────────────────────
+ * 부품 하나를 더할 때마다 나머지를 손으로 밀어야 하고, 그렇게 만든 판은 2px 씩 어긋난다. 폼에서
+ * 눈에 걸리는 것이 대개 그 어긋남이다.
+ *
+ * ── 계산기는 **한 벌이다** ─────────────────────────────────────────────────
+ * 시드도 저작면도 여기를 지난다. 두 벌을 두면 시드로 세운 화면과 사람이 만든 화면이 다르게 생기고,
+ * 그때 어느 쪽이 맞는지 아무도 못 정한다. 그래서 이 파일은 시드가 아니라 **station 어휘**에 산다.
+ *
+ * ── 규칙은 하나다: 세로로 쌓고, 짝지을 것만 나란히 ─────────────────────────
+ * 숫자패드와 단추는 여럿이 나란히 놓인다 — 작업자가 손을 옮기는 거리가 짧아야 한다. 나머지는
+ * 한 줄에 하나다.
+ */
+/**
+ * 화면에 놓이는 부품 하나 — **그려지는 것만.**
+ *
+ * 흐름의 단계(`StationStep`)와 다르다. 단계는 「사람이 무엇을 하나」이고 여기는 「무엇이 그려지나」다.
+ * 한 단계가 부품 둘을 낳기도 하고(값 넣기 → 숫자패드), 하나도 안 낳기도 한다(설정).
+ */
+export type StationScreenPart = 
+/** 컨텍스트 축 하나를 값으로. `stationBindingNames()` 가 이름의 유일한 원본이다. */
+{
+    part: 'field';
+    field: string;
+    label?: string;
+    big?: boolean;
+} | {
+    part: 'who';
+    label?: string;
+    prompt?: string;
+} | {
+    part: 'order';
+    label?: string;
+} | {
+    part: 'counts';
+    label?: string;
+} | {
+    part: 'numpad';
+    label?: string;
+    counts?: 'good' | 'scrap';
+    disabled?: boolean;
+} | {
+    part: 'action';
+    label?: string;
+    action: 'start' | 'finish' | 'pause' | 'resume';
+    reasonCode?: string;
+    disabled?: boolean;
+} | {
+    part: 'staged';
+    label?: string;
+    removable?: boolean;
+} | {
+    part: 'directive';
+    label?: string;
+} | {
+    part: 'maintenance';
+    label?: string;
+} | {
+    part: 'context';
+    refreshSeconds?: number;
+};
+/**
+ * 부품에서 모델을 만든다.
+ *
+ * `context` 는 그려지지 않지만 **모델에는 들어간다** — 갱신 주기를 든 부품이라, 없으면 그 화면이
+ * 무엇을 얼마나 자주 읽을지 아무 데도 안 적힌다. 자리는 판 밖에 둔다.
+ */
+export declare function screenModel(parts: StationScreenPart[]): string;
+/**
+ * 흐름 → 그려질 부품.
+ *
+ * ── 단계와 부품은 하나가 아니다 ────────────────────────────────────────────
+ * 「값 넣기」 한 단계가 숫자패드 하나를 낳고, 「보기」 한 단계가 읽는 축 수만큼 값을 낳고, 「설정」은
+ * 하나도 안 낳는다(그려지지 않지만 모델에는 남는다 — 갱신 주기를 든 부품이라).
+ *
+ * ── 이름표가 없으면 축 이름을 쓴다 ─────────────────────────────────────────
+ * 빈 이름표로 두지 않는다. 작업대에서 맨숫자는 가장 자주 오독되는 것이고, 그 오독은 수량을 잘못
+ * 적는 것으로 이어진다.
+ */
+export declare function partsOfFlow(flow: StationFlow): StationScreenPart[];
+/**
+ * 이 실행 단계가 어떤 단추인가.
+ *
+ * 단계의 `status` 출처가 `{ from: 'step' }` 이라는 것은 「단계의 뜻이 정한다」는 말이고, 그 뜻이
+ * 여기서 단추 모양으로도 나온다. 아직 흐름이 그것을 따로 적지 않으므로 이름표에서 읽는다 —
+ * 흐름에 칸이 생기면 그때 그것을 본다.
+ */
+/** 저장하지 않고 흐름이 무엇을 그릴지 — 저작면의 미리보기가 이것을 받는다. */
+export interface StationScreenDraftResult {
+    model: string;
+    requires: string[];
+    problems: StationProblem[];
+}
+/**
+ * 흐름 하나가 낳는 **모든 것**을 한 번에 — 도안 · 읽는 축 · 저작자가 알아야 할 것.
+ *
+ * ── 왜 셋을 묶었나 ────────────────────────────────────────────────────────
+ * 저작면의 미리보기와 저장이 같은 계산을 봐야 한다. 미리보기가 도안만 받고 저장이 축을 따로 세면,
+ * 저작자가 본 화면과 배정 검증이 검사하는 축이 갈릴 수 있다 — 그리고 그 차이는 배정하는 날에야
+ * 드러난다.
+ *
+ * ── 빈 흐름은 오류가 아니다 ───────────────────────────────────────────────
+ * 저작면은 고칠 때마다 묻고, 그중에는 마지막 단계를 지운 편집도 있다. 그때 던지면 화면이 「그리지
+ * 못했습니다」를 말하는데 사실은 그릴 것이 없는 것뿐이다.
+ */
+export declare function draftScreen(flow: StationFlow | null | undefined): StationScreenDraftResult;
+/**
+ * 이 부품들이 읽는 컨텍스트 축.
+ *
+ * `StationScreenSpec.requires` 는 **파생값이다.** 손으로 적으면 부품을 고칠 때 어긋나고, 그러면
+ * 배정 검증이 이미 사실이 아닌 것을 검사한다.
+ *
+ * 흐름 쪽에는 같은 일을 하는 `axesRead` 가 따로 있다 — 들어오는 어휘가 다르기 때문이다(시드는
+ * 부품으로, 저작면은 단계로 들어온다). 규칙이 갈리지 않게 둘 다 여기 계산기 옆에 산다.
+ */
+export declare function axesOfParts(parts: StationScreenPart[]): string[];