dominds 0.1.0

package/dist/tools/prompts/team_mgmt.en.md

@@ -0,0 +1,70 @@
+# team-mgmt: manage `.minds/` (prepare-first + single apply)
+
+You have read/write access to `.minds/**`, but this toolset **only operates within the `.minds/` subtree** (it should not touch other workspace files).
+
+## Principles
+
+- Incremental edits (preferred): use `team_mgmt_prepare_*` to generate reviewable YAML + diff + `hunk_id`, then write via `team_mgmt_apply_file_modification({ "hunk_id": "<hunk_id>" })`.
+- Parallelism constraint: multiple tool calls in one generation step may run in parallel; **prepare → apply must be two steps**.
+- Exception (create): `team_mgmt_create_new_file` only creates a new file (empty content allowed). It does not do incremental edits and does not use prepare/apply; it refuses to overwrite existing files.
+- Exception (overwrite): `team_mgmt_overwrite_entire_file` writes immediately (no prepare/apply). It requires `known_old_total_lines/known_old_total_bytes` guardrails; use `team_mgmt_read_file` to read `total_lines/size_bytes` from the YAML header.
+- Normalization: each line ends with `\\n` (including the last line); the tool may add a trailing newline and report it in `normalized.*`.
+
+## read_file output fields (important)
+
+The YAML header from `team_mgmt_read_file` includes:
+
+- `total_lines`: total line count (empty file is 0); can be used for `team_mgmt_overwrite_entire_file.known_old_total_lines`
+- `size_bytes`: byte size (stat().size); can be used for `team_mgmt_overwrite_entire_file.known_old_total_bytes`
+
+## Path rules (important)
+
+- This toolset resolves `path` under `.minds/` (e.g. `team.yaml` resolves to `.minds/team.yaml`).
+- Any path that resolves outside `.minds/` after normalization is rejected.
+
+## Which tool to use
+
+- Read/locate: `team_mgmt_read_file` / `team_mgmt_list_dir` / `team_mgmt_ripgrep_*`
+- Create a new file (empty allowed): `team_mgmt_create_new_file({ path, content })`
+- Small edits (line range): `team_mgmt_prepare_file_range_edit({ path, range, content, existing_hunk_id })`
+- Append to EOF: `team_mgmt_prepare_file_append({ path, content, create, existing_hunk_id })`
+- Anchor insertion: `team_mgmt_prepare_file_insert_after|team_mgmt_prepare_file_insert_before({ path, anchor, content, occurrence, match, existing_hunk_id })`
+- Block replace between anchors: `team_mgmt_prepare_file_block_replace({ path, start_anchor, end_anchor, content, existing_hunk_id, occurrence, include_anchors, match, require_unique, strict })`
+- Apply: `team_mgmt_apply_file_modification({ hunk_id })`
+- After editing `.minds/team.yaml`: always run `team_mgmt_validate_team_cfg({})` and clear all Problems panel errors before proceeding.
+
+> Note: some providers (e.g. Codex) require all function-tool parameter fields to be present (schema all required).
+> If you use such a provider but semantically want “unset / default”, use sentinel values; otherwise most providers can omit optional fields:
+>
+> - `existing_hunk_id: ""` means generate a new hunk.
+> - `occurrence: ""` or `0` means occurrence is not specified.
+> - `match: ""` means default `contains` (note: `match` is the match mode).
+
+## Apply semantics (context_match)
+
+- `exact`: file matches the prepare context exactly.
+- `fuzz`: file drifted but still safe to apply; the output includes `file_changed_since_preview` and digests for review.
+- `rejected`: cannot locate uniquely or unsafe; re-prepare.
+
+## Two-step template
+
+1. Prepare:
+
+```text
+Call the function tool `team_mgmt_prepare_file_range_edit` with:
+{ "path": "team.yaml", "range": "10~12", "content": "..." }
+```
+
+2. Apply (must be a separate step):
+
+```text
+Call the function tool `team_mgmt_apply_file_modification` with:
+{ "hunk_id": "<hunk_id>" }
+```
+
+## Create an empty file example
+
+```text
+Call the function tool `team_mgmt_create_new_file` with:
+{ "path": "team/domains/new-domain.md", "content": "" }
+```

package/dist/tools/prompts/team_mgmt.zh.md

@@ -0,0 +1,70 @@
+# team-mgmt：管理 `.minds/`（prepare-first + single apply）
+
+你拥有对 `.minds/**` 的读写能力，但该 toolset **只允许操作 `.minds/` 子树**（不会也不应触碰工作区其他文件）。
+
+## 总原则
+
+- 增量编辑（推荐）：用 `team_mgmt_prepare_*` 先生成可复核的 YAML + diff + `hunk_id`，再用 `team_mgmt_apply_file_modification({ "hunk_id": "<hunk_id>" })` 显式写入。
+- 并行约束：同一轮生成中的多个工具调用可能并行执行；**prepare → apply 必须分两轮**。
+- 例外（创建）：`team_mgmt_create_new_file` 只负责创建新文件（允许空内容），不做增量编辑、不走 prepare/apply；若文件已存在会拒绝（避免误用覆盖写入语义）。
+- 例外（整文件覆盖）：`team_mgmt_overwrite_entire_file` 会直接写盘（不走 prepare/apply），必须提供 `known_old_total_lines/known_old_total_bytes` 作为对账护栏；建议先用 `team_mgmt_read_file` 从 YAML header 读取 `total_lines/size_bytes` 再填写。
+- 规范化：写入遵循“每行以 `\\n` 结尾（含最后一行）”；必要时会补齐并通过输出字段呈现（例如 `normalized_trailing_newline_added` / `normalized.*`）。
+
+## read_file 输出字段（重要）
+
+`team_mgmt_read_file` 的 YAML header 会给出：
+
+- `total_lines`：总行数（空文件为 0），可直接填入 `team_mgmt_overwrite_entire_file.known_old_total_lines`
+- `size_bytes`：字节数（等于 stat().size），可直接填入 `team_mgmt_overwrite_entire_file.known_old_total_bytes`
+
+## 路径规则（重要）
+
+- 该 toolset 会把 `path` 解析到 `.minds/` 下：例如 `team.yaml` 会被解析为 `.minds/team.yaml`。
+- 任何最终解析不在 `.minds/` 内的路径都会被拒绝。
+
+## 该用哪个工具
+
+- 读取定位：`team_mgmt_read_file` / `team_mgmt_list_dir` / `team_mgmt_ripgrep_*`
+- 创建新文件（允许空内容）：`team_mgmt_create_new_file({ path, content })`
+- 小改动（行号范围）：`team_mgmt_prepare_file_range_edit({ path, range, content, existing_hunk_id })`
+- 末尾追加：`team_mgmt_prepare_file_append({ path, content, create, existing_hunk_id })`
+- 锚点插入：`team_mgmt_prepare_file_insert_after|team_mgmt_prepare_file_insert_before({ path, anchor, content, occurrence, match, existing_hunk_id })`
+- 双锚点块替换：`team_mgmt_prepare_file_block_replace({ path, start_anchor, end_anchor, content, existing_hunk_id, occurrence, include_anchors, match, require_unique, strict })`
+- 应用写入：`team_mgmt_apply_file_modification({ hunk_id })`
+- 修改完 `.minds/team.yaml`：务必运行 `team_mgmt_validate_team_cfg({})`，并清空 Problems 面板里的 team.yaml 错误后再继续。
+
+> 注意：有些 provider（例如 Codex）会要求函数工具参数字段都“必填”（schema 全 required）。  
+> 如果你用的是这类 provider，但语义上想表达“未指定/使用默认”，再用哨兵值；否则（大多数 provider）省略可选字段即可：
+>
+> - `existing_hunk_id: ""`：不覆写旧规划（生成新 hunk）。
+> - `occurrence: ""` 或 `0`：不指定 occurrence。
+> - `match: ""`：默认 `contains`（注意：`match` 是 match mode，不是要匹配的文本/正则）。
+
+## apply 语义（context_match）
+
+- `exact`：文件与 prepare 时一致，或在原位匹配成功。
+- `fuzz`：文件有漂移但仍能安全应用；此时输出会给出 `file_changed_since_preview` 与（planned/current）digest 便于复核。
+- `rejected`：无法唯一定位/不安全，必须重新 prepare。
+
+## 两步模板（复制即用）
+
+1. Prepare：
+
+```text
+Call the function tool `team_mgmt_prepare_file_range_edit` with:
+{ "path": "team.yaml", "range": "10~12", "content": "..." }
+```
+
+2. Apply（必须单独一轮）：
+
+```text
+Call the function tool `team_mgmt_apply_file_modification` with:
+{ "hunk_id": "<hunk_id>" }
+```
+
+## 创建空文件示例
+
+```text
+Call the function tool `team_mgmt_create_new_file` with:
+{ "path": "team/domains/new-domain.md", "content": "" }
+```

package/dist/tools/prompts/ws_mod.en.md

@@ -0,0 +1,86 @@
+# ws_mod: unified text-editing workflow (prepare-first + single apply)
+
+You have read/write access to the workspace, but **all incremental text edits must be prepared first, then applied**: generate reviewable diff/evidence + `hunk_id`, then confirm the write.
+
+## Principles
+
+- Incremental edits: use `prepare_*` to generate an applyable hunk, then write via `apply_file_modification`.
+- Legacy tools are removed (no compatibility layer): `append_file` / `insert_after` / `insert_before` / `replace_block` / `apply_block_replace`.
+- Constraint: paths under `*.tsk/` are encapsulated Taskdocs; file tools cannot access them.
+- Parallelism constraint: multiple tool calls in one generation step may run in parallel; **prepare → apply must be two steps**.
+- Output is YAML + unified diff (scan-friendly) with `summary` + `evidence`/`apply_evidence`.
+- Normalization: all writes follow “each line ends with `\n` (including the last line)”; missing EOF newline will be added and shown in `normalized.*`.
+- Exception: `overwrite_entire_file` overwrites an existing file (writes immediately; does not use prepare/apply). It requires `known_old_total_lines/known_old_total_bytes` guardrails (read `total_lines/size_bytes` from the YAML header of `read_file`). It also rejects diff/patch-like content by default unless `content_format=diff|patch`. Use it only for “small content (<100 lines)” or “intentional reset/generated output”; otherwise prefer prepare/apply.
+- Exception: `create_new_file` only creates a new file (empty content allowed). It does not do incremental edits and does not use prepare/apply; it refuses to overwrite existing files.
+
+## Which `prepare_*` to use
+
+- Precise range edits: `prepare_file_range_edit({ path, range, content, existing_hunk_id })`
+- Append to EOF: `prepare_file_append({ path, content, create, existing_hunk_id })`
+- Anchor insertion: `prepare_file_insert_after|prepare_file_insert_before({ path, anchor, content, occurrence, match, existing_hunk_id })`
+- Block replace between anchors: `prepare_file_block_replace({ path, start_anchor, end_anchor, content, existing_hunk_id, occurrence, include_anchors, match, require_unique, strict })`
+- Create a new file (empty allowed): `create_new_file({ path, content })`
+
+> Note: some providers (e.g. Codex) require all function-tool parameters to be present (schema all required).
+> If you use such a provider but semantically want “unset / default”, use sentinel values; otherwise most providers can omit optional fields:
+>
+> - `existing_hunk_id: ""` means generate a new hunk (do not overwrite an existing plan).
+> - `occurrence: ""` or `0` means occurrence is not specified.
+> - `match: ""` means default `contains` (note: `match` is the match mode, not the text to match).
+
+## hunk id rules (important)
+
+- `prepare_*` generates `hunk_id` (TTL = 1 hour); apply can only use an unexpired hunk.
+- Expired/unused hunks have no side effects; they are cleaned up automatically.
+- Some prepare tools accept `existing_hunk_id` to overwrite the same prepared hunk; **custom new ids are not supported**.
+
+## Apply semantics (context_match)
+
+- `exact`: file matches the prepared context exactly.
+- `fuzz`: file drifted but target can still be located safely.
+- `rejected`: target is not unique or unsafe; re-prepare.
+
+## Two-step template
+
+1. Prepare (returns `hunk_id` + unified diff):
+
+```text
+Call the function tool `prepare_file_insert_after` with:
+{ "path": "docs/spec.md", "anchor": "## Configuration", "content": "### Defaults\\n- provider: codex\\n" }
+```
+
+2. Apply (must be a separate step):
+
+```text
+Call the function tool `apply_file_modification` with:
+{ "hunk_id": "<hunk_id>" }
+```
+
+## Examples
+
+- Append to EOF:
+
+```text
+Call the function tool `prepare_file_append` with:
+{ "path": "notes/prompt.md", "content": "## Tools\\n- Use prepare_* + apply_file_modification for incremental edits.\\n" }
+```
+
+- Line range replacement (`content` can be empty to delete the range):
+
+```text
+Call the function tool `prepare_file_range_edit` with:
+{ "path": "README.md", "range": "10~12", "content": "New line 10\\nNew line 11\\n" }
+```
+
+- Block replace:
+
+```text
+Call the function tool `prepare_file_block_replace` with:
+{ "path": "docs/spec.md", "start_anchor": "## Start", "end_anchor": "## End", "content": "NEW BLOCK LINE 1\\nNEW BLOCK LINE 2\\n" }
+```
+
+## Common failures and next steps
+
+- `ANCHOR_AMBIGUOUS`: anchor appears multiple times and occurrence was not specified; set `occurrence` or use a range (`prepare_file_range_edit`).
+- `ANCHOR_NOT_FOUND`: anchor not found; locate via `read_file` / `ripgrep_snippets`.
+- apply `context_match: rejected`: file drift made the target non-unique; re-prepare (narrow range or add more context).

package/dist/tools/prompts/ws_mod.zh.md

@@ -0,0 +1,87 @@
+# ws_mod：文本编辑统一工作流（prepare-first + single apply）
+
+你拥有工作区读写能力，但**所有增量文本编辑必须先 prepare，再 apply**：先生成可复核的 diff/evidence + `hunk_id`，再显式确认写入。
+
+## 总原则
+
+- 增量编辑：通过 `prepare_*` 生成可 apply 的 hunk；然后用 `apply_file_modification` 写入。
+- 旧工具已移除（无兼容层）：`append_file` / `insert_after` / `insert_before` / `replace_block` / `apply_block_replace`。
+- 约束：`*.tsk/` 下的路径属于封装差遣牒，文件工具不可访问。
+- 并行约束：同一轮生成中的多个工具调用可能并行执行；**prepare → apply 必须分两轮**（除非未来有顺序编排器）。
+- 输出以 YAML + unified diff 为主：低注意力可复核（`summary` + `evidence`/`apply_evidence`）。
+- 规范化：所有写入遵循“每行以 `\n` 结尾（含最后一行）”；EOF 换行会被补齐并通过 `normalized.*` 字段呈现。
+- 例外：`overwrite_entire_file` 是“整文件覆盖写入”的函数工具（会直接写盘，不走 prepare/apply）。它要求提供 `known_old_total_lines/known_old_total_bytes` 作为对账护栏（建议从 `read_file` 的 YAML header 读取 `total_lines/size_bytes`），并且在正文疑似 diff/patch 且未显式声明 `content_format=diff|patch` 时默认拒绝。仅用于“新内容很小（例如 <100 行）”或“明确为重置/生成物”的场景；其他情况优先 prepare/apply。
+  - 复制参数建议：对账参数请直接用 `read_file` 的 `total_lines/size_bytes`。
+- 例外：`create_new_file` 只负责“创建新文件”（允许空内容），不做增量编辑、不走 prepare/apply；若文件已存在会拒绝（避免误用覆盖写入语义）。
+
+## 该用哪个 `prepare_*`
+
+- 精确范围改动（行号范围）：`prepare_file_range_edit({ path, range, content, existing_hunk_id })`
+- 末尾追加：`prepare_file_append({ path, content, create, existing_hunk_id })`
+- 锚点插入：`prepare_file_insert_after|prepare_file_insert_before({ path, anchor, content, occurrence, match, existing_hunk_id })`
+- 双锚点块替换：`prepare_file_block_replace({ path, start_anchor, end_anchor, content, existing_hunk_id, occurrence, include_anchors, match, require_unique, strict })`
+- 创建新文件（允许空内容）：`create_new_file({ path, content })`
+
+> 注意：有些 provider（例如 Codex）会要求所有函数工具参数字段都“必填”（schema 全 required）。  
+> 如果你用的是这类 provider，但语义上想表达“未指定/使用默认”，再用哨兵值；否则（大多数 provider）省略可选字段即可：
+>
+> - `existing_hunk_id: ""` 表示不覆写旧规划（生成新 hunk）。
+> - `occurrence: ""` 或 `0` 表示不指定 occurrence（当候选不唯一时会被要求显式指定）。
+> - `match: ""` 表示默认 `contains`（注意：`match` 是 match mode，不是要匹配的文本/正则）。
+
+## hunk id 规则（重要）
+
+- `prepare_*` 会生成 `hunk_id`（TTL=1 小时）；apply 只能用仍然存在的 hunk。
+- 过期/未使用的 hunk **不会产生任何副作用**，会在运行时自动清理；你只需要关注“自己最后一次想 apply 的那个 hunk_id”。
+- 部分 prepare 工具支持 `existing_hunk_id` 作为“覆写同一 prepare”的方式；**不支持自定义新 id**。
+
+## apply 语义（context_match）
+
+- `exact`：文件内容与 prepare 时一致或在原位匹配成功。
+- `fuzz`：文件有漂移，但仍能唯一定位目标并安全应用。
+- `rejected`：无法唯一定位或不安全；必须重新 prepare。
+
+## 两步模板（复制即用）
+
+1. Prepare（返回 `hunk_id` + unified diff）：
+
+```text
+Call the function tool `prepare_file_insert_after` with:
+{ "path": "docs/spec.md", "anchor": "## Configuration", "content": "### Defaults\\n- provider: codex\\n" }
+```
+
+2. Apply（必须单独一轮/单独一步）：
+
+```text
+Call the function tool `apply_file_modification` with:
+{ "hunk_id": "<hunk_id>" }
+```
+
+## 示例
+
+- 末尾追加：
+
+```text
+Call the function tool `prepare_file_append` with:
+{ "path": "notes/prompt.md", "content": "## Tools\\n- Use prepare_* + apply_file_modification for incremental edits.\\n" }
+```
+
+- 行号范围替换（`content` 可为空字符串表示删除）：
+
+```text
+Call the function tool `prepare_file_range_edit` with:
+{ "path": "README.md", "range": "10~12", "content": "New line 10\\nNew line 11\\n" }
+```
+
+- 双锚点块替换：
+
+```text
+Call the function tool `prepare_file_block_replace` with:
+{ "path": "docs/spec.md", "start_anchor": "## Start", "end_anchor": "## End", "content": "NEW BLOCK LINE 1\\nNEW BLOCK LINE 2\\n" }
+```
+
+## 常见失败与下一步
+
+- `ANCHOR_AMBIGUOUS`：锚点多次出现且未指定 occurrence；请指定 occurrence 或改用行号范围（`prepare_file_range_edit`）。
+- `ANCHOR_NOT_FOUND`：锚点未找到；必要时先 `read_file` 或用 `ripgrep_snippets` 定位。
+- apply `context_match: rejected`：文件变化导致无法唯一定位；请重新 prepare（缩小范围或增加上下文）。

package/dist/tools/registry-snapshot.js

@@ -0,0 +1,31 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.createToolsRegistrySnapshot = createToolsRegistrySnapshot;
+const time_1 = require("../shared/utils/time");
+const registry_1 = require("./registry");
+function createToolsRegistrySnapshot() {
+    const toolsets = [];
+    for (const [toolsetName, tools] of registry_1.toolsetsRegistry.entries()) {
+        const meta = (0, registry_1.getToolsetMeta)(toolsetName);
+        const descriptionI18n = meta ? meta.descriptionI18n : undefined;
+        const source = meta?.source ?? 'dominds';
+        toolsets.push({
+            name: toolsetName,
+            source,
+            descriptionI18n,
+            tools: tools.map(toolToInfo),
+        });
+    }
+    return {
+        toolsets,
+        timestamp: (0, time_1.formatUnifiedTimestamp)(new Date()),
+    };
+}
+function toolToInfo(tool) {
+    return {
+        name: tool.name,
+        kind: 'func',
+        description: tool.description,
+        descriptionI18n: tool.descriptionI18n,
+    };
+}

package/dist/tools/registry.js

@@ -0,0 +1,121 @@
+"use strict";
+var __importDefault = (this && this.__importDefault) || function (mod) {
+    return (mod && mod.__esModule) ? mod : { "default": mod };
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.reminderOwnersRegistry = exports.toolsetMetaRegistry = exports.toolsetsRegistry = exports.toolsRegistry = void 0;
+exports.registerTool = registerTool;
+exports.unregisterTool = unregisterTool;
+exports.getTool = getTool;
+exports.listTools = listTools;
+exports.registerToolset = registerToolset;
+exports.unregisterToolset = unregisterToolset;
+exports.setToolsetMeta = setToolsetMeta;
+exports.getToolsetMeta = getToolsetMeta;
+exports.getToolsetPromptI18n = getToolsetPromptI18n;
+exports.getToolset = getToolset;
+exports.listToolsets = listToolsets;
+exports.registerReminderOwner = registerReminderOwner;
+exports.unregisterReminderOwner = unregisterReminderOwner;
+exports.getReminderOwner = getReminderOwner;
+exports.listReminderOwners = listReminderOwners;
+/**
+ * Module: tools/registry
+ *
+ * Global registries for tools and toolsets with helpers and built-in initialization.
+ */
+const fs_1 = __importDefault(require("fs"));
+const path_1 = __importDefault(require("path"));
+// Global public registry of tools, shared across the application
+exports.toolsRegistry = new Map();
+// Global public registry of toolsets, shared across the application
+exports.toolsetsRegistry = new Map();
+exports.toolsetMetaRegistry = new Map();
+// Global public registry of ReminderOwner instances, shared across the application
+exports.reminderOwnersRegistry = new Map();
+// Register a tool object by name
+function registerTool(tool) {
+    exports.toolsRegistry.set(tool.name, tool);
+}
+// Unregister a tool by name
+function unregisterTool(name) {
+    exports.toolsRegistry.delete(name);
+}
+// Retrieve a tool by name
+function getTool(name) {
+    return exports.toolsRegistry.get(name);
+}
+// List all registered tools
+function listTools() {
+    return Array.from(exports.toolsRegistry.values());
+}
+// Register a toolset by name with a list of tool objects
+function registerToolset(name, tools) {
+    exports.toolsetsRegistry.set(name, tools);
+}
+// Unregister a toolset by name
+function unregisterToolset(name) {
+    exports.toolsetsRegistry.delete(name);
+    exports.toolsetMetaRegistry.delete(name);
+}
+function setToolsetMeta(name, meta) {
+    exports.toolsetMetaRegistry.set(name, meta);
+}
+function getToolsetMeta(name) {
+    return exports.toolsetMetaRegistry.get(name);
+}
+function getToolsetPromptI18n(name) {
+    const meta = getToolsetMeta(name);
+    if (!meta)
+        return undefined;
+    if (meta.promptI18n)
+        return meta.promptI18n;
+    if (!meta.promptFilesI18n)
+        return undefined;
+    const enPath = meta.promptFilesI18n.en;
+    const zhPath = meta.promptFilesI18n.zh;
+    if (!enPath || !zhPath)
+        return undefined;
+    const tryRead = (relPath) => {
+        const abs = path_1.default.resolve(__dirname, relPath);
+        try {
+            return fs_1.default.readFileSync(abs, 'utf8');
+        }
+        catch {
+            return '';
+        }
+    };
+    const en = tryRead(enPath);
+    const zh = tryRead(zhPath);
+    if (en.trim() === '' || zh.trim() === '')
+        return undefined;
+    return { en, zh };
+}
+// Retrieve a toolset by name (returns array of tool objects)
+function getToolset(name) {
+    return exports.toolsetsRegistry.get(name);
+}
+// List all registered toolsets
+function listToolsets() {
+    return Object.fromEntries(exports.toolsetsRegistry.entries());
+}
+// Register a ReminderOwner by unique name
+function registerReminderOwner(owner, name) {
+    const ownerName = name || owner.name;
+    if (!ownerName) {
+        throw new Error('ReminderOwner must have a name property or name must be provided explicitly');
+    }
+    exports.reminderOwnersRegistry.set(ownerName, owner);
+}
+// Unregister a ReminderOwner by name
+function unregisterReminderOwner(name) {
+    exports.reminderOwnersRegistry.delete(name);
+}
+// Retrieve a ReminderOwner by name
+function getReminderOwner(name) {
+    return exports.reminderOwnersRegistry.get(name);
+}
+// List all registered ReminderOwners
+function listReminderOwners() {
+    return new Map(exports.reminderOwnersRegistry);
+}