@things-factory/worklist 10.1.247 → 10.1.248

package/dist-server/controllers/activity-approval/save.js

@@ -1,56 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.save = save;
-const shell_1 = require("@things-factory/shell");
-const check_authority_js_1 = require("./check-authority.js");
-const approval_line_js_1 = require("./approval-line.js");
-const opinion_js_1 = require("./opinion.js");
-const activity_approval_js_1 = require("../../service/activity-approval/activity-approval.js");
-const activity_thread_js_1 = require("../../service/activity-thread/activity-thread.js");
-const common_js_1 = require("../common.js");
-async function save({ id, comment }, context) {
-    const { domain, user, tx } = context.state;
-    var repository = (0, shell_1.getRepository)(activity_approval_js_1.ActivityApproval, tx);
-    var activityApproval = await repository.findOne({
-        where: { domain: { id: domain.id }, id }
-    });
-    if (!activityApproval) {
-        throw new Error(context.t('error.activity-approval not found', {
-            activityApproval: id
-        }));
-    }
-    await (0, check_authority_js_1.checkAuthority)(activityApproval, context);
-    /*
-     * ── 결정이 끝난 결재의 의견은 고쳐 쓰지 않는다 (2026-09-02) ────────────────
-     * `checkAuthority` 는 **누구인지만** 본다. 그래서 이미 승인·반려한 사람이 자기 행의 의견을 나중에
-     * 다시 쓸 수 있었고, 흔적은 `updatedAt` 뿐이었다. 승인 기록을 뒤에서 고쳐 쓰는 것은 규제 산업이
-     * 금지하는 바로 그 행위다 — 이 저장소가 옛 판정 표기를 고치지 않고 읽는 자리에서 흡수하는 것과
-     * 같은 이유다(§`isApproved`).
-     *
-     * **참조는 반대다.** 참조가 결재를 막지 않는다는 것의 뜻이 이것이다 — 결정이 끝난 뒤에도 의견을
-     * 말할 수 있고, 화면은 그것을 「결정 후 의견」으로 보여 준다. 막으면 참조자가 휴가에서 돌아와
-     * 할 수 있는 일이 없다.
-     */
-    if ((0, approval_line_js_1.isTerminated)(activityApproval.judgment) && !(0, approval_line_js_1.isReferenceStep)(activityApproval)) {
-        throw new Error(context.t('error.approval already decided', {
-            defaultValue: '이미 결정된 결재의 의견은 고칠 수 없습니다 — 결정 기록은 뒤에서 고쳐 쓰지 않습니다'
-        }));
-    }
-    const result = await repository.save({
-        ...activityApproval,
-        ...(0, opinion_js_1.stampedComment)(comment),
-        updater: user
-    });
-    /*
-     * **`tx` 를 넘긴다.** 넘기지 않으면 요청 트랜잭션 밖에서 읽고, 이 트랜잭션이 방금 고친 값을 못 본다.
-     * 그 낡은 스레드가 그대로 `causedBy` 로 넘어가 인스턴스 상태 판정에 쓰인다.
-     *
-     * 지금은 이 함수가 스레드를 안 고쳐서 드러나지 않는다. 드러나지 않는 것과 맞는 것은 다르다.
-     */
-    const activityThread = await (0, shell_1.getRepository)(activity_thread_js_1.ActivityThread, tx).findOneBy({
-        id: activityApproval.activityThreadId
-    });
-    await (0, common_js_1.updateActivityInstanceState)(activityThread?.activityInstanceId, { causedBy: [activityThread] }, context);
-    return result;
-}
-//# sourceMappingURL=save.js.map

package/dist-server/controllers/activity-approval/save.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"save.js","sourceRoot":"","sources":["../../../server/controllers/activity-approval/save.ts"],"names":[],"mappings":";;AAQA,oBA4DC;AApED,iDAAqD;AACrD,6DAAqD;AACrD,yDAAkE;AAClE,6CAA6C;AAC7C,+FAAuF;AACvF,yFAAiF;AACjF,4CAA0D;AAEnD,KAAK,UAAU,IAAI,CACxB,EAAE,EAAE,EAAE,OAAO,EAAmC,EAChD,OAAwB;IAExB,MAAM,EAAE,MAAM,EAAE,IAAI,EAAE,EAAE,EAAE,GAAG,OAAO,CAAC,KAAK,CAAA;IAE1C,IAAI,UAAU,GAAG,IAAA,qBAAa,EAAC,uCAAgB,EAAE,EAAE,CAAC,CAAA;IAEpD,IAAI,gBAAgB,GAAG,MAAM,UAAU,CAAC,OAAO,CAAC;QAC9C,KAAK,EAAE,EAAE,MAAM,EAAE,EAAE,EAAE,EAAE,MAAM,CAAC,EAAE,EAAE,EAAE,EAAE,EAAE;KACzC,CAAC,CAAA;IAEF,IAAI,CAAC,gBAAgB,EAAE,CAAC;QACtB,MAAM,IAAI,KAAK,CACb,OAAO,CAAC,CAAC,CAAC,mCAAmC,EAAE;YAC7C,gBAAgB,EAAE,EAAE;SACrB,CAAC,CACH,CAAA;IACH,CAAC;IAED,MAAM,IAAA,mCAAc,EAAC,gBAAgB,EAAE,OAAO,CAAC,CAAA;IAE/C;;;;;;;;;;OAUG;IACH,IAAI,IAAA,+BAAY,EAAC,gBAAgB,CAAC,QAAQ,CAAC,IAAI,CAAC,IAAA,kCAAe,EAAC,gBAAuB,CAAC,EAAE,CAAC;QACzF,MAAM,IAAI,KAAK,CACb,OAAO,CAAC,CAAC,CAAC,gCAAgC,EAAE;YAC1C,YAAY,EAAE,kDAAkD;SACjE,CAAC,CACH,CAAA;IACH,CAAC;IAED,MAAM,MAAM,GAAG,MAAM,UAAU,CAAC,IAAI,CAAC;QACnC,GAAG,gBAAgB;QACnB,GAAG,IAAA,2BAAc,EAAC,OAAO,CAAC;QAC1B,OAAO,EAAE,IAAI;KACd,CAAC,CAAA;IAEF;;;;;OAKG;IACH,MAAM,cAAc,GAAG,MAAM,IAAA,qBAAa,EAAC,mCAAc,EAAE,EAAE,CAAC,CAAC,SAAS,CAAC;QACvE,EAAE,EAAE,gBAAgB,CAAC,gBAAgB;KACtC,CAAC,CAAA;IAEF,MAAM,IAAA,uCAA2B,EAAC,cAAc,EAAE,kBAAkB,EAAE,EAAE,QAAQ,EAAE,CAAC,cAAc,CAAC,EAAE,EAAE,OAAO,CAAC,CAAA;IAE9G,OAAO,MAAM,CAAA;AACf,CAAC","sourcesContent":["import { getRepository } from '@things-factory/shell'\nimport { checkAuthority } from './check-authority.js'\nimport { isReferenceStep, isTerminated } from './approval-line.js'\nimport { stampedComment } from './opinion.js'\nimport { ActivityApproval } from '../../service/activity-approval/activity-approval.js'\nimport { ActivityThread } from '../../service/activity-thread/activity-thread.js'\nimport { updateActivityInstanceState } from '../common.js'\n\nexport async function save(\n  { id, comment }: { id: string; comment: string },\n  context: ResolverContext\n): Promise<ActivityApproval> {\n  const { domain, user, tx } = context.state\n\n  var repository = getRepository(ActivityApproval, tx)\n\n  var activityApproval = await repository.findOne({\n    where: { domain: { id: domain.id }, id }\n  })\n\n  if (!activityApproval) {\n    throw new Error(\n      context.t('error.activity-approval not found', {\n        activityApproval: id\n      })\n    )\n  }\n\n  await checkAuthority(activityApproval, context)\n\n  /*\n   * ── 결정이 끝난 결재의 의견은 고쳐 쓰지 않는다 (2026-09-02) ────────────────\n   * `checkAuthority` 는 **누구인지만** 본다. 그래서 이미 승인·반려한 사람이 자기 행의 의견을 나중에\n   * 다시 쓸 수 있었고, 흔적은 `updatedAt` 뿐이었다. 승인 기록을 뒤에서 고쳐 쓰는 것은 규제 산업이\n   * 금지하는 바로 그 행위다 — 이 저장소가 옛 판정 표기를 고치지 않고 읽는 자리에서 흡수하는 것과\n   * 같은 이유다(§`isApproved`).\n   *\n   * **참조는 반대다.** 참조가 결재를 막지 않는다는 것의 뜻이 이것이다 — 결정이 끝난 뒤에도 의견을\n   * 말할 수 있고, 화면은 그것을 「결정 후 의견」으로 보여 준다. 막으면 참조자가 휴가에서 돌아와\n   * 할 수 있는 일이 없다.\n   */\n  if (isTerminated(activityApproval.judgment) && !isReferenceStep(activityApproval as any)) {\n    throw new Error(\n      context.t('error.approval already decided', {\n        defaultValue: '이미 결정된 결재의 의견은 고칠 수 없습니다 — 결정 기록은 뒤에서 고쳐 쓰지 않습니다'\n      })\n    )\n  }\n\n  const result = await repository.save({\n    ...activityApproval,\n    ...stampedComment(comment),\n    updater: user\n  })\n\n  /*\n   * **`tx` 를 넘긴다.** 넘기지 않으면 요청 트랜잭션 밖에서 읽고, 이 트랜잭션이 방금 고친 값을 못 본다.\n   * 그 낡은 스레드가 그대로 `causedBy` 로 넘어가 인스턴스 상태 판정에 쓰인다.\n   *\n   * 지금은 이 함수가 스레드를 안 고쳐서 드러나지 않는다. 드러나지 않는 것과 맞는 것은 다르다.\n   */\n  const activityThread = await getRepository(ActivityThread, tx).findOneBy({\n    id: activityApproval.activityThreadId\n  })\n\n  await updateActivityInstanceState(activityThread?.activityInstanceId, { causedBy: [activityThread] }, context)\n\n  return result\n}\n"]}

package/dist-server/controllers/activity-approval/seat-standing.d.ts

@@ -1,66 +0,0 @@
-/**
- * 결재선의 자리마다 **설 사람이 있나** — 상신하는 순간에 본다.
- *
- * 상신자는 자기 상신의 결재자가 될 수 있다(2026-10-23 사용자: 「상신자는 결재자가 될 수 없다는 원칙을
- * 제거하라」 — ADR-0052 ② 를 거둠). 그래서 여기 남은 물음은 하나다: 결재 자리에 **아무도** 못 서는가.
- *
- * ── 왜 올리는 순간에 보나 ─────────────────────────────────────────────────
- * 결재선의 결재 자리는 차례로 **전부** 판정을 받아야 끝난다. 한 자리만 막혀도 그 건은 거기서 영영
- * 선다. 올릴 때 막으면 **고칠 수 있는 사람이 보는 자리**에서 걸리고, 무엇을 고쳐야 하는지 그 자리에서
- * 말할 수 있다.
- *
- * ── 낱말은 자리를 선언하는 방법을 따른다 ─────────────────────────────────
- *   approval-line-missing     결재선 자체가 없다        (§`approval-expectation.ts`)
- *   approval-role-empty       지목한 역할에 사람이 0명
- *   approval-person-missing   지목한 사람 자리가 안 풀린다
- * 관리자가 할 일이 다르므로 사유를 합치지 않는다. (2026-09-16, 아키텍트 판정)
- */
-/** 이 자리가 판정하는 자리인가 — 빈 값은 결재다(`ApprovalLineItem.participation` 과 같은 규약). */
-export declare function judges(participation?: string | null): boolean;
-/** 결재 자리 하나와, 거기 설 수 있는 사람들. 역할 자리면 그 역할을 가진 사람 전부. */
-export type JudgeableSeat = {
-    /** 사람이 세는 차례 — 1차 결재, 2차 결재. 거절 문구가 이 수를 말한다. */
-    order: number;
-    /** 역할로 건 자리인가 사람으로 건 자리인가 — **거절 사유가 갈린다.** */
-    kind: 'role' | 'person';
-    /** 그 자리에 설 수 있는 사람들의 id. 역할 자리면 그 역할을 가진 사람 전부. */
-    couldJudge: string[];
-    /** 화면에 낼 자리 이름 — 역할 이름이나 사람 이름. */
-    name?: string;
-    /**
-     * 그 자리가 **가리키던 식별자.** 안 풀리는 자리를 고치려면 「누구 자리였는지」를 알아야 한다 —
-     * 이름은 못 찾으면 비는데 가리키던 값은 결재선에 그대로 남아 있다.
-     */
-    pointsAt?: string;
-};
-/** 거절 사유 하나와, 그 사유로 막힌 자리들. */
-export type SeatRefusal = {
-    because: 'approval-role-empty' | 'approval-person-missing';
-    seats: {
-        order: number;
-        name?: string;
-        pointsAt?: string;
-    }[];
-};
-export type StandingVerdict = {
-    ok: true;
-} | {
-    ok: false;
-    refusals: SeatRefusal[];
-};
-/**
- * 이 결재선을 올려도 되나 — 결재 자리마다 설 사람이 하나라도 있나.
- *
- * 사유가 둘이면 **둘 다 돌려준다.** 하나씩 말하면 관리자가 하나 고치고 다시 걸린다.
- */
-export declare function judgeSeatsStand(input: {
-    /** **결재 자리만.** 참조는 판정하지 않으므로 여기 오지 않는다. */
-    seats: JudgeableSeat[];
-}): StandingVerdict;
-export declare function standingBroken(verdict: StandingVerdict): verdict is Extract<StandingVerdict, {
-    ok: false;
-}>;
-/** 사유마다 문구가 다르다 — 관리자가 할 일이 다르기 때문이다. */
-export declare const STANDING_REFUSAL_KEYS: {
-    [because in SeatRefusal['because']]: string;
-};

package/dist-server/controllers/activity-approval/seat-standing.js

@@ -1,57 +0,0 @@
-"use strict";
-/**
- * 결재선의 자리마다 **설 사람이 있나** — 상신하는 순간에 본다.
- *
- * 상신자는 자기 상신의 결재자가 될 수 있다(2026-10-23 사용자: 「상신자는 결재자가 될 수 없다는 원칙을
- * 제거하라」 — ADR-0052 ② 를 거둠). 그래서 여기 남은 물음은 하나다: 결재 자리에 **아무도** 못 서는가.
- *
- * ── 왜 올리는 순간에 보나 ─────────────────────────────────────────────────
- * 결재선의 결재 자리는 차례로 **전부** 판정을 받아야 끝난다. 한 자리만 막혀도 그 건은 거기서 영영
- * 선다. 올릴 때 막으면 **고칠 수 있는 사람이 보는 자리**에서 걸리고, 무엇을 고쳐야 하는지 그 자리에서
- * 말할 수 있다.
- *
- * ── 낱말은 자리를 선언하는 방법을 따른다 ─────────────────────────────────
- *   approval-line-missing     결재선 자체가 없다        (§`approval-expectation.ts`)
- *   approval-role-empty       지목한 역할에 사람이 0명
- *   approval-person-missing   지목한 사람 자리가 안 풀린다
- * 관리자가 할 일이 다르므로 사유를 합치지 않는다. (2026-09-16, 아키텍트 판정)
- */
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.STANDING_REFUSAL_KEYS = void 0;
-exports.judges = judges;
-exports.judgeSeatsStand = judgeSeatsStand;
-exports.standingBroken = standingBroken;
-/** 이 자리가 판정하는 자리인가 — 빈 값은 결재다(`ApprovalLineItem.participation` 과 같은 규약). */
-function judges(participation) {
-    return participation !== 'reference';
-}
-/**
- * 이 결재선을 올려도 되나 — 결재 자리마다 설 사람이 하나라도 있나.
- *
- * 사유가 둘이면 **둘 다 돌려준다.** 하나씩 말하면 관리자가 하나 고치고 다시 걸린다.
- */
-function judgeSeatsStand(input) {
-    const { seats } = input;
-    const named = (of) => of.map(({ order, name, pointsAt }) => ({ order, name, pointsAt }));
-    /* 역할을 지목했는데 그 역할에 사람이 없다. */
-    const roleEmpty = seats.filter(seat => seat.kind === 'role' && seat.couldJudge.length === 0);
-    /* 지목한 사람이 안 풀린다 — 없어진 직원을 가리키는 자리다. 역할 문제가 아니므로 다른 낱말이다. */
-    const personMissing = seats.filter(seat => seat.kind === 'person' && seat.couldJudge.length === 0);
-    const refusals = [];
-    if (roleEmpty.length) {
-        refusals.push({ because: 'approval-role-empty', seats: named(roleEmpty) });
-    }
-    if (personMissing.length) {
-        refusals.push({ because: 'approval-person-missing', seats: named(personMissing) });
-    }
-    return refusals.length ? { ok: false, refusals } : { ok: true };
-}
-function standingBroken(verdict) {
-    return !verdict.ok;
-}
-/** 사유마다 문구가 다르다 — 관리자가 할 일이 다르기 때문이다. */
-exports.STANDING_REFUSAL_KEYS = {
-    'approval-role-empty': 'error.approval line names a role that nobody holds',
-    'approval-person-missing': 'error.approval line names a person who cannot be found'
-};
-//# sourceMappingURL=seat-standing.js.map

package/dist-server/controllers/activity-approval/seat-standing.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"seat-standing.js","sourceRoot":"","sources":["../../../server/controllers/activity-approval/seat-standing.ts"],"names":[],"mappings":";AAAA;;;;;;;;;;;;;;;;GAgBG;;;AAGH,wBAEC;AAgCD,0CAyBC;AAED,wCAEC;AAhED,4EAA4E;AAC5E,SAAgB,MAAM,CAAC,aAA6B;IAClD,OAAO,aAAa,KAAK,WAAW,CAAA;AACtC,CAAC;AA2BD;;;;GAIG;AACH,SAAgB,eAAe,CAAC,KAG/B;IACC,MAAM,EAAE,KAAK,EAAE,GAAG,KAAK,CAAA;IAEvB,MAAM,KAAK,GAAG,CAAC,EAAmB,EAAE,EAAE,CAAC,EAAE,CAAC,GAAG,CAAC,CAAC,EAAE,KAAK,EAAE,IAAI,EAAE,QAAQ,EAAE,EAAE,EAAE,CAAC,CAAC,EAAE,KAAK,EAAE,IAAI,EAAE,QAAQ,EAAE,CAAC,CAAC,CAAA;IAEzG,6BAA6B;IAC7B,MAAM,SAAS,GAAG,KAAK,CAAC,MAAM,CAAC,IAAI,CAAC,EAAE,CAAC,IAAI,CAAC,IAAI,KAAK,MAAM,IAAI,IAAI,CAAC,UAAU,CAAC,MAAM,KAAK,CAAC,CAAC,CAAA;IAE5F,4DAA4D;IAC5D,MAAM,aAAa,GAAG,KAAK,CAAC,MAAM,CAAC,IAAI,CAAC,EAAE,CAAC,IAAI,CAAC,IAAI,KAAK,QAAQ,IAAI,IAAI,CAAC,UAAU,CAAC,MAAM,KAAK,CAAC,CAAC,CAAA;IAElG,MAAM,QAAQ,GAAkB,EAAE,CAAA;IAElC,IAAI,SAAS,CAAC,MAAM,EAAE,CAAC;QACrB,QAAQ,CAAC,IAAI,CAAC,EAAE,OAAO,EAAE,qBAAqB,EAAE,KAAK,EAAE,KAAK,CAAC,SAAS,CAAC,EAAE,CAAC,CAAA;IAC5E,CAAC;IAED,IAAI,aAAa,CAAC,MAAM,EAAE,CAAC;QACzB,QAAQ,CAAC,IAAI,CAAC,EAAE,OAAO,EAAE,yBAAyB,EAAE,KAAK,EAAE,KAAK,CAAC,aAAa,CAAC,EAAE,CAAC,CAAA;IACpF,CAAC;IAED,OAAO,QAAQ,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,EAAE,KAAK,EAAE,QAAQ,EAAE,CAAC,CAAC,CAAC,EAAE,EAAE,EAAE,IAAI,EAAE,CAAA;AACjE,CAAC;AAED,SAAgB,cAAc,CAAC,OAAwB;IACrD,OAAO,CAAC,OAAO,CAAC,EAAE,CAAA;AACpB,CAAC;AAED,yCAAyC;AAC5B,QAAA,qBAAqB,GAAoD;IACpF,qBAAqB,EAAE,oDAAoD;IAC3E,yBAAyB,EAAE,wDAAwD;CACpF,CAAA","sourcesContent":["/**\n * 결재선의 자리마다 **설 사람이 있나** — 상신하는 순간에 본다.\n *\n * 상신자는 자기 상신의 결재자가 될 수 있다(2026-10-23 사용자: 「상신자는 결재자가 될 수 없다는 원칙을\n * 제거하라」 — ADR-0052 ② 를 거둠). 그래서 여기 남은 물음은 하나다: 결재 자리에 **아무도** 못 서는가.\n *\n * ── 왜 올리는 순간에 보나 ─────────────────────────────────────────────────\n * 결재선의 결재 자리는 차례로 **전부** 판정을 받아야 끝난다. 한 자리만 막혀도 그 건은 거기서 영영\n * 선다. 올릴 때 막으면 **고칠 수 있는 사람이 보는 자리**에서 걸리고, 무엇을 고쳐야 하는지 그 자리에서\n * 말할 수 있다.\n *\n * ── 낱말은 자리를 선언하는 방법을 따른다 ─────────────────────────────────\n *   approval-line-missing     결재선 자체가 없다        (§`approval-expectation.ts`)\n *   approval-role-empty       지목한 역할에 사람이 0명\n *   approval-person-missing   지목한 사람 자리가 안 풀린다\n * 관리자가 할 일이 다르므로 사유를 합치지 않는다. (2026-09-16, 아키텍트 판정)\n */\n\n/** 이 자리가 판정하는 자리인가 — 빈 값은 결재다(`ApprovalLineItem.participation` 과 같은 규약). */\nexport function judges(participation?: string | null): boolean {\n  return participation !== 'reference'\n}\n\n/** 결재 자리 하나와, 거기 설 수 있는 사람들. 역할 자리면 그 역할을 가진 사람 전부. */\nexport type JudgeableSeat = {\n  /** 사람이 세는 차례 — 1차 결재, 2차 결재. 거절 문구가 이 수를 말한다. */\n  order: number\n  /** 역할로 건 자리인가 사람으로 건 자리인가 — **거절 사유가 갈린다.** */\n  kind: 'role' | 'person'\n  /** 그 자리에 설 수 있는 사람들의 id. 역할 자리면 그 역할을 가진 사람 전부. */\n  couldJudge: string[]\n  /** 화면에 낼 자리 이름 — 역할 이름이나 사람 이름. */\n  name?: string\n  /**\n   * 그 자리가 **가리키던 식별자.** 안 풀리는 자리를 고치려면 「누구 자리였는지」를 알아야 한다 —\n   * 이름은 못 찾으면 비는데 가리키던 값은 결재선에 그대로 남아 있다.\n   */\n  pointsAt?: string\n}\n\n/** 거절 사유 하나와, 그 사유로 막힌 자리들. */\nexport type SeatRefusal = {\n  because: 'approval-role-empty' | 'approval-person-missing'\n  seats: { order: number; name?: string; pointsAt?: string }[]\n}\n\nexport type StandingVerdict = { ok: true } | { ok: false; refusals: SeatRefusal[] }\n\n/**\n * 이 결재선을 올려도 되나 — 결재 자리마다 설 사람이 하나라도 있나.\n *\n * 사유가 둘이면 **둘 다 돌려준다.** 하나씩 말하면 관리자가 하나 고치고 다시 걸린다.\n */\nexport function judgeSeatsStand(input: {\n  /** **결재 자리만.** 참조는 판정하지 않으므로 여기 오지 않는다. */\n  seats: JudgeableSeat[]\n}): StandingVerdict {\n  const { seats } = input\n\n  const named = (of: JudgeableSeat[]) => of.map(({ order, name, pointsAt }) => ({ order, name, pointsAt }))\n\n  /* 역할을 지목했는데 그 역할에 사람이 없다. */\n  const roleEmpty = seats.filter(seat => seat.kind === 'role' && seat.couldJudge.length === 0)\n\n  /* 지목한 사람이 안 풀린다 — 없어진 직원을 가리키는 자리다. 역할 문제가 아니므로 다른 낱말이다. */\n  const personMissing = seats.filter(seat => seat.kind === 'person' && seat.couldJudge.length === 0)\n\n  const refusals: SeatRefusal[] = []\n\n  if (roleEmpty.length) {\n    refusals.push({ because: 'approval-role-empty', seats: named(roleEmpty) })\n  }\n\n  if (personMissing.length) {\n    refusals.push({ because: 'approval-person-missing', seats: named(personMissing) })\n  }\n\n  return refusals.length ? { ok: false, refusals } : { ok: true }\n}\n\nexport function standingBroken(verdict: StandingVerdict): verdict is Extract<StandingVerdict, { ok: false }> {\n  return !verdict.ok\n}\n\n/** 사유마다 문구가 다르다 — 관리자가 할 일이 다르기 때문이다. */\nexport const STANDING_REFUSAL_KEYS: { [because in SeatRefusal['because']]: string } = {\n  'approval-role-empty': 'error.approval line names a role that nobody holds',\n  'approval-person-missing': 'error.approval line names a person who cannot be found'\n}\n"]}

package/dist-server/controllers/activity-installation/activity-installation-controller.d.ts

@@ -1,79 +0,0 @@
-import { EntityManager } from 'typeorm';
-import { Domain } from '@things-factory/shell';
-import { Activity } from '../../service/activity/activity.js';
-import { InstallableActivity } from '../../service/installable-activity/installable-activity.js';
-import { ActivityReadiness } from '../../service/installable-activity/activity-readiness.js';
-/**
- * 등록된 양식을 **도메인에 실제로 세운다.**
- *
- * ── 왜 함수로 내놓나 ───────────────────────────────────────────────────────
- * 앞서는 이 일이 화면 뮤테이션 안에만 있었다. 그래서 양식을 세우는 길이 **사람이 화면에서 누르는 것
- * 하나뿐**이었고, 새로 배포하거나 도메인을 하나 더 만들 때마다 그 클릭을 기억해야 했다. 기억하지
- * 못하면 그 기능이 오류 보고 없이 없다.
- *
- * 앱이 「내 기능이 서려면 이 양식이 있어야 한다」를 아는 경우가 있다. 그런 앱은 기동할 때 스스로
- * 세울 수 있어야 한다. 언제 세울지는 앱이 정하고, 세우는 방법은 여기가 한 벌만 갖는다.
- *
- * ── 있는 것을 덮되 결재선은 건드리지 않는다 ────────────────────────────────
- * 이미 있으면 양식의 선언(모델 · 보는 화면 · 시작 방식)으로 덮는다. 버전이 오르면 그 값이 따라와야
- * 하기 때문이다.
- *
- * 그런데 **결재선은 양식의 것이 아니라 그 현장의 것**이다. 누가 결재하는지는 공장이 정한다. 그래서
- * 양식에 결재선 선언이 없으면 이미 있는 결재선이 그대로 남는다 — 버전을 올릴 때마다 결재자가 지워지면
- * 그 뒤로 상신이 곧 완료가 된다.
- */
-export declare function installActivity(name: string, domain: Domain, options?: {
-    manager?: EntityManager;
-    user?: any;
-}): Promise<Activity>;
-/**
- * Work a module has identified as a person's decision and **has not built.**
- *
- * Deliberately not an InstallableActivity. A template with no callback can be installed and
- * issued, and then someone approves a request and nothing happens — on the twin side that means a
- * person presses approve and no equipment moves. So these live in their own registry: the catalog
- * reads them, `installActivity` cannot reach them.
- *
- * They belong on the screen because the catalog is the plan of record. The question "what is left"
- * should be answered where people look, not in one person's head.
- */
-export type IntendedActivity = {
-    /** What the activity's `name` will be once it exists. */
-    key: string;
-    /** What the catalog shows. The activity's own name is usually not a sentence a person reads. */
-    label: string;
-    category?: string;
-    /** What this work is, for the person who will receive it. Draft wording is fine. */
-    guide?: string[];
-    readiness: ActivityReadiness;
-};
-export declare class ActivityInstallations {
-    static templates: {
-        [name: string]: InstallableActivity;
-    };
-    /** Keyed separately from `templates`, so nothing here can be installed by mistake. */
-    static intended: {
-        [key: string]: IntendedActivity;
-    };
-    static installActivityTemplate(template: InstallableActivity): void;
-    /**
-     * Declare work that should reach someone's worklist and does not yet.
-     *
-     * A module calls this for each item it has identified. When the real thing is built, delete the
-     * call and register the template instead — the catalog row moves from 예정 to 동작 확인됨 on its
-     * own.
-     */
-    static declareIntendedActivity(intended: IntendedActivity): void;
-    static get(name: string): InstallableActivity;
-    static list(): InstallableActivity[];
-    static listIntended(): IntendedActivity[];
-    /**
-     * 액티비티인스턴스의 변화가 발생했을 때, 호출되는 콜백함수
-     * @param name 액티비티인스턴스가 속한 액티비티명
-     * @param activityInstance 해당 액티비티인스턴스
-     * @param activityThreads 액티비티인스턴스의 변화를 일으킨 원인이 되는 액티비티쓰레드들
-     * @param context 서비스 컨텍스트 : domain, user, translation, ..
-     * @returns
-     */
-    static callback(name: string, activityInstance: any, activityThreads: any[], context: ResolverContext): Promise<void>;
-}

package/dist-server/controllers/activity-installation/activity-installation-controller.js

@@ -1,99 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.ActivityInstallations = void 0;
-exports.installActivity = installActivity;
-const shell_1 = require("@things-factory/shell");
-const activity_js_1 = require("../../service/activity/activity.js");
-const registry_conflict_js_1 = require("./registry-conflict.js");
-const decision_key_declaration_js_1 = require("../../service/activity/decision-key-declaration.js");
-const installable_to_activity_js_1 = require("./installable-to-activity.js");
-/**
- * 등록된 양식을 **도메인에 실제로 세운다.**
- *
- * ── 왜 함수로 내놓나 ───────────────────────────────────────────────────────
- * 앞서는 이 일이 화면 뮤테이션 안에만 있었다. 그래서 양식을 세우는 길이 **사람이 화면에서 누르는 것
- * 하나뿐**이었고, 새로 배포하거나 도메인을 하나 더 만들 때마다 그 클릭을 기억해야 했다. 기억하지
- * 못하면 그 기능이 오류 보고 없이 없다.
- *
- * 앱이 「내 기능이 서려면 이 양식이 있어야 한다」를 아는 경우가 있다. 그런 앱은 기동할 때 스스로
- * 세울 수 있어야 한다. 언제 세울지는 앱이 정하고, 세우는 방법은 여기가 한 벌만 갖는다.
- *
- * ── 있는 것을 덮되 결재선은 건드리지 않는다 ────────────────────────────────
- * 이미 있으면 양식의 선언(모델 · 보는 화면 · 시작 방식)으로 덮는다. 버전이 오르면 그 값이 따라와야
- * 하기 때문이다.
- *
- * 그런데 **결재선은 양식의 것이 아니라 그 현장의 것**이다. 누가 결재하는지는 공장이 정한다. 그래서
- * 양식에 결재선 선언이 없으면 이미 있는 결재선이 그대로 남는다 — 버전을 올릴 때마다 결재자가 지워지면
- * 그 뒤로 상신이 곧 완료가 된다.
- */
-async function installActivity(name, domain, options = {}) {
-    const template = ActivityInstallations.get(name);
-    if (!template) {
-        /*
-         * 없는 이름을 세울 수는 없다. 조용히 넘기면 부르는 쪽은 세운 줄 알고, 그 기능은 없는 채로 선다.
-         */
-        throw new Error(`installActivity: there is no installable activity named "${name}". ` +
-            `known: ${ActivityInstallations.list()
-                .map(one => one.name)
-                .join(', ')}`);
-    }
-    const { manager, user } = options;
-    const repository = (0, shell_1.getRepository)(activity_js_1.Activity, manager);
-    const existing = await repository.findOneBy({ domain: { id: domain.id }, name });
-    return await repository.save({
-        ...(existing ?? {}),
-        ...(0, installable_to_activity_js_1.activityRowFrom)(template),
-        state: activity_js_1.ActivityStatus.Released,
-        domain,
-        creator: existing ? existing.creator : user,
-        updater: user
-    });
-}
-class ActivityInstallations {
-    static { this.templates = {}; }
-    /** Keyed separately from `templates`, so nothing here can be installed by mistake. */
-    static { this.intended = {}; }
-    static installActivityTemplate(template) {
-        (0, registry_conflict_js_1.assertNotDeclaredIntended)(template.name, ActivityInstallations.intended);
-        (0, registry_conflict_js_1.assertDoorSlugIsFree)(template.name, decision_key_declaration_js_1.doorSlug, ActivityInstallations.templates);
-        ActivityInstallations.templates[template.name] = template;
-    }
-    /**
-     * Declare work that should reach someone's worklist and does not yet.
-     *
-     * A module calls this for each item it has identified. When the real thing is built, delete the
-     * call and register the template instead — the catalog row moves from 예정 to 동작 확인됨 on its
-     * own.
-     */
-    static declareIntendedActivity(intended) {
-        (0, registry_conflict_js_1.assertNotAlreadyInstalled)(intended.key, ActivityInstallations.templates);
-        ActivityInstallations.intended[intended.key] = intended;
-    }
-    static get(name) {
-        return ActivityInstallations.templates[name];
-    }
-    static list() {
-        return Object.values(ActivityInstallations.templates);
-    }
-    static listIntended() {
-        return Object.values(ActivityInstallations.intended);
-    }
-    /**
-     * 액티비티인스턴스의 변화가 발생했을 때, 호출되는 콜백함수
-     * @param name 액티비티인스턴스가 속한 액티비티명
-     * @param activityInstance 해당 액티비티인스턴스
-     * @param activityThreads 액티비티인스턴스의 변화를 일으킨 원인이 되는 액티비티쓰레드들
-     * @param context 서비스 컨텍스트 : domain, user, translation, ..
-     * @returns
-     */
-    static async callback(name, activityInstance, activityThreads, context) {
-        const installableActivity = ActivityInstallations.templates[name];
-        if (!installableActivity) {
-            return;
-        }
-        const { callback } = installableActivity;
-        callback && (await callback(activityInstance, { causedBy: activityThreads }, context));
-    }
-}
-exports.ActivityInstallations = ActivityInstallations;
-//# sourceMappingURL=activity-installation-controller.js.map

package/dist-server/controllers/activity-installation/activity-installation-controller.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"activity-installation-controller.js","sourceRoot":"","sources":["../../../server/controllers/activity-installation/activity-installation-controller.ts"],"names":[],"mappings":";;;AA8BA,0CAgCC;AA5DD,iDAA6D;AAE7D,oEAA6E;AAG7E,iEAAmH;AACnH,oGAA6E;AAC7E,6EAA8D;AAE9D;;;;;;;;;;;;;;;;;;GAkBG;AACI,KAAK,UAAU,eAAe,CACnC,IAAY,EACZ,MAAc,EACd,UAAmD,EAAE;IAErD,MAAM,QAAQ,GAAG,qBAAqB,CAAC,GAAG,CAAC,IAAI,CAAC,CAAA;IAEhD,IAAI,CAAC,QAAQ,EAAE,CAAC;QACd;;WAEG;QACH,MAAM,IAAI,KAAK,CACb,4DAA4D,IAAI,KAAK;YACnE,UAAU,qBAAqB,CAAC,IAAI,EAAE;iBACnC,GAAG,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,CAAC,IAAI,CAAC;iBACpB,IAAI,CAAC,IAAI,CAAC,EAAE,CAClB,CAAA;IACH,CAAC;IAED,MAAM,EAAE,OAAO,EAAE,IAAI,EAAE,GAAG,OAAO,CAAA;IACjC,MAAM,UAAU,GAAG,IAAA,qBAAa,EAAC,sBAAQ,EAAE,OAAO,CAAC,CAAA;IAEnD,MAAM,QAAQ,GAAG,MAAM,UAAU,CAAC,SAAS,CAAC,EAAE,MAAM,EAAE,EAAE,EAAE,EAAE,MAAM,CAAC,EAAE,EAAE,EAAE,IAAI,EAAE,CAAC,CAAA;IAEhF,OAAO,MAAM,UAAU,CAAC,IAAI,CAAC;QAC3B,GAAG,CAAC,QAAQ,IAAI,EAAE,CAAC;QACnB,GAAG,IAAA,4CAAe,EAAC,QAAQ,CAAC;QAC5B,KAAK,EAAE,4BAAc,CAAC,QAAQ;QAC9B,MAAM;QACN,OAAO,EAAE,QAAQ,CAAC,CAAC,CAAE,QAAgB,CAAC,OAAO,CAAC,CAAC,CAAC,IAAI;QACpD,OAAO,EAAE,IAAI;KACF,CAAC,CAAA;AAChB,CAAC;AAwBD,MAAa,qBAAqB;aACzB,cAAS,GAA4C,EAAE,CAAA;IAE9D,sFAAsF;aAC/E,aAAQ,GAAwC,EAAE,CAAA;IAEzD,MAAM,CAAC,uBAAuB,CAAC,QAA6B;QAC1D,IAAA,gDAAyB,EAAC,QAAQ,CAAC,IAAI,EAAE,qBAAqB,CAAC,QAAQ,CAAC,CAAA;QACxE,IAAA,2CAAoB,EAAC,QAAQ,CAAC,IAAI,EAAE,sCAAQ,EAAE,qBAAqB,CAAC,SAAS,CAAC,CAAA;QAE9E,qBAAqB,CAAC,SAAS,CAAC,QAAQ,CAAC,IAAI,CAAC,GAAG,QAAQ,CAAA;IAC3D,CAAC;IAED;;;;;;OAMG;IACH,MAAM,CAAC,uBAAuB,CAAC,QAA0B;QACvD,IAAA,gDAAyB,EAAC,QAAQ,CAAC,GAAG,EAAE,qBAAqB,CAAC,SAAS,CAAC,CAAA;QAExE,qBAAqB,CAAC,QAAQ,CAAC,QAAQ,CAAC,GAAG,CAAC,GAAG,QAAQ,CAAA;IACzD,CAAC;IAED,MAAM,CAAC,GAAG,CAAC,IAAY;QACrB,OAAO,qBAAqB,CAAC,SAAS,CAAC,IAAI,CAAC,CAAA;IAC9C,CAAC;IAED,MAAM,CAAC,IAAI;QACT,OAAO,MAAM,CAAC,MAAM,CAAC,qBAAqB,CAAC,SAAS,CAAC,CAAA;IACvD,CAAC;IAED,MAAM,CAAC,YAAY;QACjB,OAAO,MAAM,CAAC,MAAM,CAAC,qBAAqB,CAAC,QAAQ,CAAC,CAAA;IACtD,CAAC;IAED;;;;;;;OAOG;IACH,MAAM,CAAC,KAAK,CAAC,QAAQ,CAAC,IAAY,EAAE,gBAAqB,EAAE,eAAsB,EAAE,OAAwB;QACzG,MAAM,mBAAmB,GAAG,qBAAqB,CAAC,SAAS,CAAC,IAAI,CAAC,CAAA;QACjE,IAAI,CAAC,mBAAmB,EAAE,CAAC;YACzB,OAAM;QACR,CAAC;QAED,MAAM,EAAE,QAAQ,EAAE,GAAG,mBAAmB,CAAA;QAExC,QAAQ,IAAI,CAAC,MAAM,QAAQ,CAAC,gBAAgB,EAAE,EAAE,QAAQ,EAAE,eAAe,EAAE,EAAE,OAAO,CAAC,CAAC,CAAA;IACxF,CAAC;;AAvDH,sDAwDC","sourcesContent":["import { EntityManager } from 'typeorm'\n\nimport { Domain, getRepository } from '@things-factory/shell'\n\nimport { Activity, ActivityStatus } from '../../service/activity/activity.js'\nimport { InstallableActivity } from '../../service/installable-activity/installable-activity.js'\nimport { ActivityReadiness } from '../../service/installable-activity/activity-readiness.js'\nimport { assertDoorSlugIsFree, assertNotAlreadyInstalled, assertNotDeclaredIntended } from './registry-conflict.js'\nimport { doorSlug } from '../../service/activity/decision-key-declaration.js'\nimport { activityRowFrom } from './installable-to-activity.js'\n\n/**\n * 등록된 양식을 **도메인에 실제로 세운다.**\n *\n * ── 왜 함수로 내놓나 ───────────────────────────────────────────────────────\n * 앞서는 이 일이 화면 뮤테이션 안에만 있었다. 그래서 양식을 세우는 길이 **사람이 화면에서 누르는 것\n * 하나뿐**이었고, 새로 배포하거나 도메인을 하나 더 만들 때마다 그 클릭을 기억해야 했다. 기억하지\n * 못하면 그 기능이 오류 보고 없이 없다.\n *\n * 앱이 「내 기능이 서려면 이 양식이 있어야 한다」를 아는 경우가 있다. 그런 앱은 기동할 때 스스로\n * 세울 수 있어야 한다. 언제 세울지는 앱이 정하고, 세우는 방법은 여기가 한 벌만 갖는다.\n *\n * ── 있는 것을 덮되 결재선은 건드리지 않는다 ────────────────────────────────\n * 이미 있으면 양식의 선언(모델 · 보는 화면 · 시작 방식)으로 덮는다. 버전이 오르면 그 값이 따라와야\n * 하기 때문이다.\n *\n * 그런데 **결재선은 양식의 것이 아니라 그 현장의 것**이다. 누가 결재하는지는 공장이 정한다. 그래서\n * 양식에 결재선 선언이 없으면 이미 있는 결재선이 그대로 남는다 — 버전을 올릴 때마다 결재자가 지워지면\n * 그 뒤로 상신이 곧 완료가 된다.\n */\nexport async function installActivity(\n  name: string,\n  domain: Domain,\n  options: { manager?: EntityManager; user?: any } = {}\n): Promise<Activity> {\n  const template = ActivityInstallations.get(name)\n\n  if (!template) {\n    /*\n     * 없는 이름을 세울 수는 없다. 조용히 넘기면 부르는 쪽은 세운 줄 알고, 그 기능은 없는 채로 선다.\n     */\n    throw new Error(\n      `installActivity: there is no installable activity named \"${name}\". ` +\n        `known: ${ActivityInstallations.list()\n          .map(one => one.name)\n          .join(', ')}`\n    )\n  }\n\n  const { manager, user } = options\n  const repository = getRepository(Activity, manager)\n\n  const existing = await repository.findOneBy({ domain: { id: domain.id }, name })\n\n  return await repository.save({\n    ...(existing ?? {}),\n    ...activityRowFrom(template),\n    state: ActivityStatus.Released,\n    domain,\n    creator: existing ? (existing as any).creator : user,\n    updater: user\n  } as Activity)\n}\n\n/**\n * Work a module has identified as a person's decision and **has not built.**\n *\n * Deliberately not an InstallableActivity. A template with no callback can be installed and\n * issued, and then someone approves a request and nothing happens — on the twin side that means a\n * person presses approve and no equipment moves. So these live in their own registry: the catalog\n * reads them, `installActivity` cannot reach them.\n *\n * They belong on the screen because the catalog is the plan of record. The question \"what is left\"\n * should be answered where people look, not in one person's head.\n */\nexport type IntendedActivity = {\n  /** What the activity's `name` will be once it exists. */\n  key: string\n  /** What the catalog shows. The activity's own name is usually not a sentence a person reads. */\n  label: string\n  category?: string\n  /** What this work is, for the person who will receive it. Draft wording is fine. */\n  guide?: string[]\n  readiness: ActivityReadiness\n}\n\nexport class ActivityInstallations {\n  static templates: { [name: string]: InstallableActivity } = {}\n\n  /** Keyed separately from `templates`, so nothing here can be installed by mistake. */\n  static intended: { [key: string]: IntendedActivity } = {}\n\n  static installActivityTemplate(template: InstallableActivity) {\n    assertNotDeclaredIntended(template.name, ActivityInstallations.intended)\n    assertDoorSlugIsFree(template.name, doorSlug, ActivityInstallations.templates)\n\n    ActivityInstallations.templates[template.name] = template\n  }\n\n  /**\n   * Declare work that should reach someone's worklist and does not yet.\n   *\n   * A module calls this for each item it has identified. When the real thing is built, delete the\n   * call and register the template instead — the catalog row moves from 예정 to 동작 확인됨 on its\n   * own.\n   */\n  static declareIntendedActivity(intended: IntendedActivity) {\n    assertNotAlreadyInstalled(intended.key, ActivityInstallations.templates)\n\n    ActivityInstallations.intended[intended.key] = intended\n  }\n\n  static get(name: string): InstallableActivity {\n    return ActivityInstallations.templates[name]\n  }\n\n  static list(): InstallableActivity[] {\n    return Object.values(ActivityInstallations.templates)\n  }\n\n  static listIntended(): IntendedActivity[] {\n    return Object.values(ActivityInstallations.intended)\n  }\n\n  /**\n   * 액티비티인스턴스의 변화가 발생했을 때, 호출되는 콜백함수\n   * @param name 액티비티인스턴스가 속한 액티비티명\n   * @param activityInstance 해당 액티비티인스턴스\n   * @param activityThreads 액티비티인스턴스의 변화를 일으킨 원인이 되는 액티비티쓰레드들\n   * @param context 서비스 컨텍스트 : domain, user, translation, ..\n   * @returns\n   */\n  static async callback(name: string, activityInstance: any, activityThreads: any[], context: ResolverContext) {\n    const installableActivity = ActivityInstallations.templates[name]\n    if (!installableActivity) {\n      return\n    }\n\n    const { callback } = installableActivity\n\n    callback && (await callback(activityInstance, { causedBy: activityThreads }, context))\n  }\n}\n"]}

package/dist-server/controllers/activity-installation/call-webhook.d.ts

@@ -1,3 +0,0 @@
-import { EntityManager } from 'typeorm';
-import { Domain } from '@things-factory/shell';
-export declare function callWebhook(domain: Domain, tag: string, data: any, tx?: EntityManager): Promise<void>;

package/dist-server/controllers/activity-installation/call-webhook.js

@@ -1,42 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.callWebhook = callWebhook;
-const tslib_1 = require("tslib");
-const node_fetch_1 = tslib_1.__importDefault(require("node-fetch"));
-const auth_base_1 = require("@things-factory/auth-base");
-const shell_1 = require("@things-factory/shell");
-async function callWebhook(domain, tag, data, tx) {
-    /*
-      TODO webhook callback의 다양한 subscription 조건을 지원한다.
-      - activity의 client에 해당하는 application
-      - activityInstance의 starter에 해당하는 application
-      - 모든 이벤트를 받고자하는 application
-      - 특정 activity들의 이벤트를 받고자하는 application
-    */
-    const applications = await (tx ? tx.getRepository(auth_base_1.Application) : (0, shell_1.getRepository)(auth_base_1.Application)).findBy({
-        domain: { id: domain.id }
-    });
-    const options = {
-        method: 'post',
-        headers: {
-            'x-things-factory-domain': domain.name,
-            'Content-Type': 'application/json'
-        },
-        body: {
-            tag,
-            data
-        }
-    };
-    try {
-        applications
-            .filter(app => app.webhook)
-            .every(app => {
-            const webhook = app.webhook;
-            (0, node_fetch_1.default)(webhook, options);
-        });
-    }
-    catch (err) {
-        console.error(err);
-    }
-}
-//# sourceMappingURL=call-webhook.js.map

package/dist-server/controllers/activity-installation/call-webhook.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"call-webhook.js","sourceRoot":"","sources":["../../../server/controllers/activity-installation/call-webhook.ts"],"names":[],"mappings":";;AAMA,kCAmCC;;AAzCD,oEAA8B;AAG9B,yDAAuD;AACvD,iDAA6D;AAEtD,KAAK,UAAU,WAAW,CAAC,MAAc,EAAE,GAAW,EAAE,IAAS,EAAE,EAAkB;IAC1F;;;;;;MAME;IAEF,MAAM,YAAY,GAAG,MAAM,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC,aAAa,CAAC,uBAAW,CAAC,CAAC,CAAC,CAAC,IAAA,qBAAa,EAAC,uBAAW,CAAC,CAAC,CAAC,MAAM,CAAC;QAClG,MAAM,EAAE,EAAE,EAAE,EAAE,MAAM,CAAC,EAAE,EAAE;KAC1B,CAAC,CAAA;IACF,MAAM,OAAO,GAAG;QACd,MAAM,EAAE,MAAM;QACd,OAAO,EAAE;YACP,yBAAyB,EAAE,MAAM,CAAC,IAAI;YACtC,cAAc,EAAE,kBAAkB;SACnC;QACD,IAAI,EAAE;YACJ,GAAG;YACH,IAAI;SACE;KACT,CAAA;IAED,IAAI,CAAC;QACH,YAAY;aACT,MAAM,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,CAAC,OAAO,CAAC;aAC1B,KAAK,CAAC,GAAG,CAAC,EAAE;YACX,MAAM,OAAO,GAAG,GAAG,CAAC,OAAO,CAAA;YAE3B,IAAA,oBAAK,EAAC,OAAO,EAAE,OAAO,CAAC,CAAA;QACzB,CAAC,CAAC,CAAA;IACN,CAAC;IAAC,OAAO,GAAG,EAAE,CAAC;QACb,OAAO,CAAC,KAAK,CAAC,GAAG,CAAC,CAAA;IACpB,CAAC;AACH,CAAC","sourcesContent":["import fetch from 'node-fetch'\n\nimport { EntityManager } from 'typeorm'\nimport { Application } from '@things-factory/auth-base'\nimport { Domain, getRepository } from '@things-factory/shell'\n\nexport async function callWebhook(domain: Domain, tag: string, data: any, tx?: EntityManager) {\n  /* \n    TODO webhook callback의 다양한 subscription 조건을 지원한다. \n    - activity의 client에 해당하는 application\n    - activityInstance의 starter에 해당하는 application\n    - 모든 이벤트를 받고자하는 application\n    - 특정 activity들의 이벤트를 받고자하는 application\n  */\n\n  const applications = await (tx ? tx.getRepository(Application) : getRepository(Application)).findBy({\n    domain: { id: domain.id }\n  })\n  const options = {\n    method: 'post',\n    headers: {\n      'x-things-factory-domain': domain.name,\n      'Content-Type': 'application/json'\n    },\n    body: {\n      tag,\n      data\n    } as any\n  }\n\n  try {\n    applications\n      .filter(app => app.webhook)\n      .every(app => {\n        const webhook = app.webhook\n\n        fetch(webhook, options)\n      })\n  } catch (err) {\n    console.error(err)\n  }\n}\n"]}

package/dist-server/controllers/activity-installation/installable-to-activity.d.ts

@@ -1,77 +0,0 @@
-/**
- * The template fields that belong on the Activity row, named one by one.
- *
- * ── Why not spread the template ───────────────────────────────────────────
- * installActivity used `{ ...(template as any) }`. A template field with no column on Activity was
- * dropped by the save, which reported success — and `as any` meant the types said nothing about it.
- * Nine fields were being handed over with no home: activity, approvalSteps, callback, category,
- * guide, label, provider, readiness, release.
- *
- * `label` was the one that hurt. It is the display name a person reads, and it reached exactly one
- * screen — the catalog, which reads the template registry directly — while every screen reading the
- * row showed the instance name instead. decisionKeys only worked because a column happened to be
- * added for it in the same change; the next field would have been left to the same luck.
- *
- * Naming the fields buys three things: a new template field has to be wired here on purpose, the
- * eight that stay behind are recorded as catalog-only rather than lost, and the two `as any` casts
- * go away. (2026-09-10, architect's ruling)
- *
- * ── What stays in the template registry, and why ──────────────────────────
- *   activity        the installed row itself, attached by the catalog query. Writing it back would
- *                   be a row pointing at itself
- *   approvalSteps   counted per domain by the catalog query from the line that is actually set up
- *   callback        a function
- *   category        how the catalog groups it
- *   guide           what the work is, for the catalog's reader
- *   provider        which module registered it
- *   readiness       how far along the registering module says it is
- *   release         which version registered it
- *
- * Each of those is answered by the registry, which is loaded in every process that serves the
- * catalog. Copying them to the row would make a second copy that goes stale on the next release.
- *
- * ── The template shape is spelled out, not imported ───────────────────────
- * InstallableActivity carries type-graphql decorators, and the test runner strips types without
- * reading them, so importing it takes the whole test file down. That happened three times in one
- * day — to search-key-declaration, to decision-key-declaration, and here.
- */
-type TemplateFields = {
-    [field: string]: unknown;
-};
-export declare const ACTIVITY_ROW_FIELDS: readonly ["name", "label", "description", "activityType", "priority", "startingType", "multiple", "model", "decisionKeys", "uiType", "uiSource", "viewType", "viewSource", "reportType", "reportSource", "thumbnail"];
-/**
- * The part of a template that is stored on the Activity row.
- *
- * A field the template left undefined is not copied, so installing again does not blank a value
- * somebody edited on the row — `save` with an explicit undefined writes null. That protection is
- * real: the activity list screen lets a domain edit viewType and viewSource on the row, and
- * installActivity runs at every boot. A field the template set to null is copied, because null is
- * how a template says the value is gone.
- *
- * ── So leaving a field out is not the same as clearing it ─────────────────
- * A template that stops providing something has to say so, because silence means "keep whatever the
- * row has":
- *
- *   viewSource: undefined   the template says nothing — the row keeps its value
- *   viewSource: null        the template says there is none — the row is cleared
- *
- * plant hit this: they removed two viewSource declarations, the rows kept pointing at elements that
- * no longer existed, and approvers met a screen that could not load. (2026-09-11)
- *
- * ── Why null and not an empty string ──────────────────────────────────────
- * The rule was first written as `viewSource: ''`, and for a string field that does clear it. But
- * five of the sixteen fields carried here are not strings — priority is a number, multiple and
- * activityType and startingType are enums, model and decisionKeys are json — and none of them has
- * an empty string. `priority: ''` puts a non-number in an integer column; `decisionKeys: ''` puts a
- * string where the screen expects an array and every declared slot disappears with no error. A rule
- * that only holds for two thirds of the list is the kind that gets applied to the other third.
- *
- * null is the one signal that reads the same on all sixteen, and it says "there is none" rather
- * than naming a value that happens to be falsy. It needs nothing here: the copy below asks only
- * whether the template said anything, so null crosses over and the save writes NULL.
- *
- * An empty string still clears a string field — it is a value, and it lands in the column. It is
- * simply not the rule. (2026-09-16, answering the architect)
- */
-export declare function activityRowFrom(template: object | undefined): TemplateFields;
-export {};

package/dist-server/controllers/activity-installation/installable-to-activity.js

@@ -1,68 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.ACTIVITY_ROW_FIELDS = void 0;
-exports.activityRowFrom = activityRowFrom;
-exports.ACTIVITY_ROW_FIELDS = [
-    'name',
-    'label',
-    'description',
-    'activityType',
-    'priority',
-    'startingType',
-    'multiple',
-    'model',
-    'decisionKeys',
-    'uiType',
-    'uiSource',
-    'viewType',
-    'viewSource',
-    'reportType',
-    'reportSource',
-    'thumbnail'
-];
-/**
- * The part of a template that is stored on the Activity row.
- *
- * A field the template left undefined is not copied, so installing again does not blank a value
- * somebody edited on the row — `save` with an explicit undefined writes null. That protection is
- * real: the activity list screen lets a domain edit viewType and viewSource on the row, and
- * installActivity runs at every boot. A field the template set to null is copied, because null is
- * how a template says the value is gone.
- *
- * ── So leaving a field out is not the same as clearing it ─────────────────
- * A template that stops providing something has to say so, because silence means "keep whatever the
- * row has":
- *
- *   viewSource: undefined   the template says nothing — the row keeps its value
- *   viewSource: null        the template says there is none — the row is cleared
- *
- * plant hit this: they removed two viewSource declarations, the rows kept pointing at elements that
- * no longer existed, and approvers met a screen that could not load. (2026-09-11)
- *
- * ── Why null and not an empty string ──────────────────────────────────────
- * The rule was first written as `viewSource: ''`, and for a string field that does clear it. But
- * five of the sixteen fields carried here are not strings — priority is a number, multiple and
- * activityType and startingType are enums, model and decisionKeys are json — and none of them has
- * an empty string. `priority: ''` puts a non-number in an integer column; `decisionKeys: ''` puts a
- * string where the screen expects an array and every declared slot disappears with no error. A rule
- * that only holds for two thirds of the list is the kind that gets applied to the other third.
- *
- * null is the one signal that reads the same on all sixteen, and it says "there is none" rather
- * than naming a value that happens to be falsy. It needs nothing here: the copy below asks only
- * whether the template said anything, so null crosses over and the save writes NULL.
- *
- * An empty string still clears a string field — it is a value, and it lands in the column. It is
- * simply not the rule. (2026-09-16, answering the architect)
- */
-function activityRowFrom(template) {
-    const fields = (template ?? {});
-    const row = {};
-    for (const field of exports.ACTIVITY_ROW_FIELDS) {
-        const value = fields[field];
-        if (value !== undefined) {
-            row[field] = value;
-        }
-    }
-    return row;
-}
-//# sourceMappingURL=installable-to-activity.js.map

package/dist-server/controllers/activity-installation/installable-to-activity.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"installable-to-activity.js","sourceRoot":"","sources":["../../../server/controllers/activity-installation/installable-to-activity.ts"],"names":[],"mappings":";;;AA2FA,0CAaC;AAlEY,QAAA,mBAAmB,GAAG;IACjC,MAAM;IACN,OAAO;IACP,aAAa;IACb,cAAc;IACd,UAAU;IACV,cAAc;IACd,UAAU;IACV,OAAO;IACP,cAAc;IACd,QAAQ;IACR,UAAU;IACV,UAAU;IACV,YAAY;IACZ,YAAY;IACZ,cAAc;IACd,WAAW;CACH,CAAA;AAEV;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAiCG;AACH,SAAgB,eAAe,CAAC,QAA4B;IAC1D,MAAM,MAAM,GAAG,CAAC,QAAQ,IAAI,EAAE,CAAmB,CAAA;IACjD,MAAM,GAAG,GAAmB,EAAE,CAAA;IAE9B,KAAK,MAAM,KAAK,IAAI,2BAAmB,EAAE,CAAC;QACxC,MAAM,KAAK,GAAG,MAAM,CAAC,KAAK,CAAC,CAAA;QAE3B,IAAI,KAAK,KAAK,SAAS,EAAE,CAAC;YACxB,GAAG,CAAC,KAAK,CAAC,GAAG,KAAK,CAAA;QACpB,CAAC;IACH,CAAC;IAED,OAAO,GAAG,CAAA;AACZ,CAAC","sourcesContent":["/**\n * The template fields that belong on the Activity row, named one by one.\n *\n * ── Why not spread the template ───────────────────────────────────────────\n * installActivity used `{ ...(template as any) }`. A template field with no column on Activity was\n * dropped by the save, which reported success — and `as any` meant the types said nothing about it.\n * Nine fields were being handed over with no home: activity, approvalSteps, callback, category,\n * guide, label, provider, readiness, release.\n *\n * `label` was the one that hurt. It is the display name a person reads, and it reached exactly one\n * screen — the catalog, which reads the template registry directly — while every screen reading the\n * row showed the instance name instead. decisionKeys only worked because a column happened to be\n * added for it in the same change; the next field would have been left to the same luck.\n *\n * Naming the fields buys three things: a new template field has to be wired here on purpose, the\n * eight that stay behind are recorded as catalog-only rather than lost, and the two `as any` casts\n * go away. (2026-09-10, architect's ruling)\n *\n * ── What stays in the template registry, and why ──────────────────────────\n *   activity        the installed row itself, attached by the catalog query. Writing it back would\n *                   be a row pointing at itself\n *   approvalSteps   counted per domain by the catalog query from the line that is actually set up\n *   callback        a function\n *   category        how the catalog groups it\n *   guide           what the work is, for the catalog's reader\n *   provider        which module registered it\n *   readiness       how far along the registering module says it is\n *   release         which version registered it\n *\n * Each of those is answered by the registry, which is loaded in every process that serves the\n * catalog. Copying them to the row would make a second copy that goes stale on the next release.\n *\n * ── The template shape is spelled out, not imported ───────────────────────\n * InstallableActivity carries type-graphql decorators, and the test runner strips types without\n * reading them, so importing it takes the whole test file down. That happened three times in one\n * day — to search-key-declaration, to decision-key-declaration, and here.\n */\ntype TemplateFields = { [field: string]: unknown }\nexport const ACTIVITY_ROW_FIELDS = [\n  'name',\n  'label',\n  'description',\n  'activityType',\n  'priority',\n  'startingType',\n  'multiple',\n  'model',\n  'decisionKeys',\n  'uiType',\n  'uiSource',\n  'viewType',\n  'viewSource',\n  'reportType',\n  'reportSource',\n  'thumbnail'\n] as const\n\n/**\n * The part of a template that is stored on the Activity row.\n *\n * A field the template left undefined is not copied, so installing again does not blank a value\n * somebody edited on the row — `save` with an explicit undefined writes null. That protection is\n * real: the activity list screen lets a domain edit viewType and viewSource on the row, and\n * installActivity runs at every boot. A field the template set to null is copied, because null is\n * how a template says the value is gone.\n *\n * ── So leaving a field out is not the same as clearing it ─────────────────\n * A template that stops providing something has to say so, because silence means \"keep whatever the\n * row has\":\n *\n *   viewSource: undefined   the template says nothing — the row keeps its value\n *   viewSource: null        the template says there is none — the row is cleared\n *\n * plant hit this: they removed two viewSource declarations, the rows kept pointing at elements that\n * no longer existed, and approvers met a screen that could not load. (2026-09-11)\n *\n * ── Why null and not an empty string ──────────────────────────────────────\n * The rule was first written as `viewSource: ''`, and for a string field that does clear it. But\n * five of the sixteen fields carried here are not strings — priority is a number, multiple and\n * activityType and startingType are enums, model and decisionKeys are json — and none of them has\n * an empty string. `priority: ''` puts a non-number in an integer column; `decisionKeys: ''` puts a\n * string where the screen expects an array and every declared slot disappears with no error. A rule\n * that only holds for two thirds of the list is the kind that gets applied to the other third.\n *\n * null is the one signal that reads the same on all sixteen, and it says \"there is none\" rather\n * than naming a value that happens to be falsy. It needs nothing here: the copy below asks only\n * whether the template said anything, so null crosses over and the save writes NULL.\n *\n * An empty string still clears a string field — it is a value, and it lands in the column. It is\n * simply not the rule. (2026-09-16, answering the architect)\n */\nexport function activityRowFrom(template: object | undefined): TemplateFields {\n  const fields = (template ?? {}) as TemplateFields\n  const row: TemplateFields = {}\n\n  for (const field of ACTIVITY_ROW_FIELDS) {\n    const value = fields[field]\n\n    if (value !== undefined) {\n      row[field] = value\n    }\n  }\n\n  return row\n}\n"]}