@sayoriqwq/effect-harness 0.0.1 → 0.0.2

package/dist/src/platform/ManagedFiles.js

@@ -1,59 +0,0 @@
-import * as Effect from 'effect/Effect';
-import * as FileSystem from 'effect/FileSystem';
-import * as Path from 'effect/Path';
-import { HarnessError } from "../harness/Errors.js";
-export const ensureDirectory = Effect.fnUntraced(function* (targetPath, options, changes) {
-    const fs = yield* FileSystem.FileSystem;
-    const exists = yield* fs.exists(targetPath);
-    if (exists) {
-        return;
-    }
-    changes.push(`create directory ${targetPath}`);
-    if (!options.dryRun) {
-        yield* fs.makeDirectory(targetPath, { recursive: true });
-    }
-});
-export const writeManagedFile = Effect.fnUntraced(function* (targetPath, content, options, changes) {
-    const fs = yield* FileSystem.FileSystem;
-    const path = yield* Path.Path;
-    const exists = yield* fs.exists(targetPath);
-    const current = exists ? yield* fs.readFileString(targetPath) : undefined;
-    if (current === content) {
-        return;
-    }
-    changes.push(`${exists ? 'update' : 'create'} ${targetPath}`);
-    if (!options.dryRun) {
-        yield* fs.makeDirectory(path.dirname(targetPath), { recursive: true });
-        yield* fs.writeFileString(targetPath, content);
-    }
-});
-function replaceTokens(text, replacements) {
-    let next = text;
-    for (const [key, value] of Object.entries(replacements)) {
-        next = next.replaceAll(key, value);
-    }
-    return next;
-}
-export function copyRuntimeDirectory(source, target, replacements, options, changes) {
-    return Effect.gen(function* () {
-        const fs = yield* FileSystem.FileSystem;
-        const path = yield* Path.Path;
-        const exists = yield* fs.exists(source);
-        if (!exists) {
-            return yield* new HarnessError({ message: `Missing runtime source: ${source}` });
-        }
-        const entries = yield* fs.readDirectory(source);
-        for (const child of entries) {
-            const sourcePath = path.join(source, child);
-            const targetPath = path.join(target, child);
-            const entry = yield* fs.stat(sourcePath);
-            if (entry.type === 'Directory') {
-                yield* copyRuntimeDirectory(sourcePath, targetPath, replacements, options, changes);
-                continue;
-            }
-            const content = replaceTokens(yield* fs.readFileString(sourcePath), replacements);
-            yield* writeManagedFile(targetPath, content, options, changes);
-        }
-    });
-}
-//# sourceMappingURL=ManagedFiles.js.map

package/dist/src/platform/ManagedFiles.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"ManagedFiles.js","sourceRoot":"","sources":["../../../src/platform/ManagedFiles.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,MAAM,MAAM,eAAe,CAAA;AACvC,OAAO,KAAK,UAAU,MAAM,mBAAmB,CAAA;AAC/C,OAAO,KAAK,IAAI,MAAM,aAAa,CAAA;AACnC,OAAO,EAAE,YAAY,EAAE,MAAM,sBAAsB,CAAA;AAEnD,MAAM,CAAC,MAAM,eAAe,GAAG,MAAM,CAAC,UAAU,CAAC,QAAQ,CAAC,EACxD,UAAkB,EAClB,OAA4B,EAC5B,OAAsB;IAEtB,MAAM,EAAE,GAAG,KAAK,CAAC,CAAC,UAAU,CAAC,UAAU,CAAA;IACvC,MAAM,MAAM,GAAG,KAAK,CAAC,CAAC,EAAE,CAAC,MAAM,CAAC,UAAU,CAAC,CAAA;IAC3C,IAAI,MAAM,EAAE,CAAC;QACX,OAAM;IACR,CAAC;IAED,OAAO,CAAC,IAAI,CAAC,oBAAoB,UAAU,EAAE,CAAC,CAAA;IAC9C,IAAI,CAAC,OAAO,CAAC,MAAM,EAAE,CAAC;QACpB,KAAK,CAAC,CAAC,EAAE,CAAC,aAAa,CAAC,UAAU,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAA;IAC1D,CAAC;AACH,CAAC,CAAC,CAAA;AAEF,MAAM,CAAC,MAAM,gBAAgB,GAAG,MAAM,CAAC,UAAU,CAAC,QAAQ,CAAC,EACzD,UAAkB,EAClB,OAAe,EACf,OAA4B,EAC5B,OAAsB;IAEtB,MAAM,EAAE,GAAG,KAAK,CAAC,CAAC,UAAU,CAAC,UAAU,CAAA;IACvC,MAAM,IAAI,GAAG,KAAK,CAAC,CAAC,IAAI,CAAC,IAAI,CAAA;IAC7B,MAAM,MAAM,GAAG,KAAK,CAAC,CAAC,EAAE,CAAC,MAAM,CAAC,UAAU,CAAC,CAAA;IAC3C,MAAM,OAAO,GAAG,MAAM,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,EAAE,CAAC,cAAc,CAAC,UAAU,CAAC,CAAC,CAAC,CAAC,SAAS,CAAA;IACzE,IAAI,OAAO,KAAK,OAAO,EAAE,CAAC;QACxB,OAAM;IACR,CAAC;IAED,OAAO,CAAC,IAAI,CAAC,GAAG,MAAM,CAAC,CAAC,CAAC,QAAQ,CAAC,CAAC,CAAC,QAAQ,IAAI,UAAU,EAAE,CAAC,CAAA;IAC7D,IAAI,CAAC,OAAO,CAAC,MAAM,EAAE,CAAC;QACpB,KAAK,CAAC,CAAC,EAAE,CAAC,aAAa,CAAC,IAAI,CAAC,OAAO,CAAC,UAAU,CAAC,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAA;QACtE,KAAK,CAAC,CAAC,EAAE,CAAC,eAAe,CAAC,UAAU,EAAE,OAAO,CAAC,CAAA;IAChD,CAAC;AACH,CAAC,CAAC,CAAA;AAEF,SAAS,aAAa,CAAC,IAAY,EAAE,YAA8C;IACjF,IAAI,IAAI,GAAG,IAAI,CAAA;IACf,KAAK,MAAM,CAAC,GAAG,EAAE,KAAK,CAAC,IAAI,MAAM,CAAC,OAAO,CAAC,YAAY,CAAC,EAAE,CAAC;QACxD,IAAI,GAAG,IAAI,CAAC,UAAU,CAAC,GAAG,EAAE,KAAK,CAAC,CAAA;IACpC,CAAC;IACD,OAAO,IAAI,CAAA;AACb,CAAC;AAED,MAAM,UAAU,oBAAoB,CAClC,MAAc,EACd,MAAc,EACd,YAA8C,EAC9C,OAA4B,EAC5B,OAAsB;IAEtB,OAAO,MAAM,CAAC,GAAG,CAAC,QAAQ,CAAC;QACzB,MAAM,EAAE,GAAG,KAAK,CAAC,CAAC,UAAU,CAAC,UAAU,CAAA;QACvC,MAAM,IAAI,GAAG,KAAK,CAAC,CAAC,IAAI,CAAC,IAAI,CAAA;QAC7B,MAAM,MAAM,GAAG,KAAK,CAAC,CAAC,EAAE,CAAC,MAAM,CAAC,MAAM,CAAC,CAAA;QACvC,IAAI,CAAC,MAAM,EAAE,CAAC;YACZ,OAAO,KAAK,CAAC,CAAC,IAAI,YAAY,CAAC,EAAE,OAAO,EAAE,2BAA2B,MAAM,EAAE,EAAE,CAAC,CAAA;QAClF,CAAC;QAED,MAAM,OAAO,GAAG,KAAK,CAAC,CAAC,EAAE,CAAC,aAAa,CAAC,MAAM,CAAC,CAAA;QAC/C,KAAK,MAAM,KAAK,IAAI,OAAO,EAAE,CAAC;YAC5B,MAAM,UAAU,GAAG,IAAI,CAAC,IAAI,CAAC,MAAM,EAAE,KAAK,CAAC,CAAA;YAC3C,MAAM,UAAU,GAAG,IAAI,CAAC,IAAI,CAAC,MAAM,EAAE,KAAK,CAAC,CAAA;YAC3C,MAAM,KAAK,GAAG,KAAK,CAAC,CAAC,EAAE,CAAC,IAAI,CAAC,UAAU,CAAC,CAAA;YACxC,IAAI,KAAK,CAAC,IAAI,KAAK,WAAW,EAAE,CAAC;gBAC/B,KAAK,CAAC,CAAC,oBAAoB,CAAC,UAAU,EAAE,UAAU,EAAE,YAAY,EAAE,OAAO,EAAE,OAAO,CAAC,CAAA;gBACnF,SAAQ;YACV,CAAC;YAED,MAAM,OAAO,GAAG,aAAa,CAAC,KAAK,CAAC,CAAC,EAAE,CAAC,cAAc,CAAC,UAAU,CAAC,EAAE,YAAY,CAAC,CAAA;YACjF,KAAK,CAAC,CAAC,gBAAgB,CAAC,UAAU,EAAE,OAAO,EAAE,OAAO,EAAE,OAAO,CAAC,CAAA;QAChE,CAAC;IACH,CAAC,CAAC,CAAA;AACJ,CAAC","sourcesContent":["import type * as PlatformError from 'effect/PlatformError'\nimport type { ManagedWriteOptions } from '../harness/Model.ts'\nimport * as Effect from 'effect/Effect'\nimport * as FileSystem from 'effect/FileSystem'\nimport * as Path from 'effect/Path'\nimport { HarnessError } from '../harness/Errors.ts'\n\nexport const ensureDirectory = Effect.fnUntraced(function* (\n  targetPath: string,\n  options: ManagedWriteOptions,\n  changes: Array<string>,\n) {\n  const fs = yield* FileSystem.FileSystem\n  const exists = yield* fs.exists(targetPath)\n  if (exists) {\n    return\n  }\n\n  changes.push(`create directory ${targetPath}`)\n  if (!options.dryRun) {\n    yield* fs.makeDirectory(targetPath, { recursive: true })\n  }\n})\n\nexport const writeManagedFile = Effect.fnUntraced(function* (\n  targetPath: string,\n  content: string,\n  options: ManagedWriteOptions,\n  changes: Array<string>,\n) {\n  const fs = yield* FileSystem.FileSystem\n  const path = yield* Path.Path\n  const exists = yield* fs.exists(targetPath)\n  const current = exists ? yield* fs.readFileString(targetPath) : undefined\n  if (current === content) {\n    return\n  }\n\n  changes.push(`${exists ? 'update' : 'create'} ${targetPath}`)\n  if (!options.dryRun) {\n    yield* fs.makeDirectory(path.dirname(targetPath), { recursive: true })\n    yield* fs.writeFileString(targetPath, content)\n  }\n})\n\nfunction replaceTokens(text: string, replacements: Readonly<Record<string, string>>): string {\n  let next = text\n  for (const [key, value] of Object.entries(replacements)) {\n    next = next.replaceAll(key, value)\n  }\n  return next\n}\n\nexport function copyRuntimeDirectory(\n  source: string,\n  target: string,\n  replacements: Readonly<Record<string, string>>,\n  options: ManagedWriteOptions,\n  changes: Array<string>,\n): Effect.Effect<void, Error | PlatformError.PlatformError, FileSystem.FileSystem | Path.Path> {\n  return Effect.gen(function* () {\n    const fs = yield* FileSystem.FileSystem\n    const path = yield* Path.Path\n    const exists = yield* fs.exists(source)\n    if (!exists) {\n      return yield* new HarnessError({ message: `Missing runtime source: ${source}` })\n    }\n\n    const entries = yield* fs.readDirectory(source)\n    for (const child of entries) {\n      const sourcePath = path.join(source, child)\n      const targetPath = path.join(target, child)\n      const entry = yield* fs.stat(sourcePath)\n      if (entry.type === 'Directory') {\n        yield* copyRuntimeDirectory(sourcePath, targetPath, replacements, options, changes)\n        continue\n      }\n\n      const content = replaceTokens(yield* fs.readFileString(sourcePath), replacements)\n      yield* writeManagedFile(targetPath, content, options, changes)\n    }\n  })\n}\n"]}

package/guide/default-capabilities.md

@@ -1,38 +0,0 @@
-# Default Harness Capabilities
-
-这份 guide 给人读，用来理解 `effect-harness` 默认补充了哪些官方 source 之外的工程保护。
-这些能力不是 Effect API 教程，也不是业务模板；它们来自 target/self practice feedback，
-并且已经落到 runtime、guardrail、verifier 或 repo-local skill。
-
-## 当前默认能力
-
-### Assertion-based tsgo suggestion cleanup
-
-`@effect/tsgo` suggestion 代表类型边界需要表达清楚。harness 默认要求优先用明确 return type、
-命名 result union/helper、`satisfies`、`Effect.satisfiesSuccessType` 或
-`Function.satisfies` 表达边界。
-
-默认保护：
-
-- target runtime 的 `effect-code` skill 会提示 agent 不要用 assertion 消音。
-- `effect-harness guardrails` 会拒绝 recurring assertion cleanup shapes。
-- `pnpm effect:verify` 和 `pnpm verify` 会执行这些 guardrails。
-
-会被拒绝的典型形态：
-
-- `Effect.orElseSucceed(() => [] as ...)`
-- `Effect.succeed(null as ...)`
-- ad-hoc `{ ok: true/false as const }` result wrappers
-
-确实来自第三方 IO 或不可表达外部边界时，可以使用局部 assertion，但应该先在 Effect 外声明边界，
-不要用 assertion 让 diagnostic 消失。
-
-## 新增默认能力
-
-新增默认能力前，先把 evidence 放进 `harness/feedback/index.md` 的 intake。
-只有同时满足这些条件才提升：
-
-- 官方 source 没有解释或捕获这个 practice failure。
-- 问题 business-neutral，并能跨 Effect targets 复用。
-- landing 是 guide、runtime、guardrail、verifier 或 repo-local skill。
-- drift 时有明确验证命令会失败。

package/guide/index.md

@@ -1,49 +0,0 @@
-# Effect Harness Guide
-
-这个目录是给人读的 guide 层。它帮助维护者和目标仓库用户理解 harness 怎么运作、
-从哪里补信息、以及实践问题如何反馈回来。
-
-如果你是在执行任务的 agent，优先读取 harness contract 层：
-
-- `harness/index.md`
-- `harness/exposure.md`
-- `harness/feedback/index.md`
-- `harness/target-agent-contract.md`
-- `repos/effect/LLMS.md`
-- `repos/effect.subtree.json`
-
-## 层级划分
-
-| Layer | Audience | Writing style | Files |
-| --- | --- | --- | --- |
-| Guide | 人 | 解释背景、路径和判断方式，优先可读性。 | `guide/` |
-| Harness contract | agent | 明确规则、输入、输出、验证命令和禁止事项。 | `harness/`、CLI/verifier |
-| Official source | 人和 agent | Effect 语义真源。 | `repos/effect/`、`@effect/tsgo` |
-
-Guide 可以解释为什么这样设计；harness contract 必须让 agent 知道具体该读什么、改什么、
-跑什么验证、哪些内容不能提升。
-
-## 阅读路径
-
-新接入目标仓库的人先读：
-
-- [Setup Guide](./setup.md)
-- [Default Harness Capabilities](./default-capabilities.md)
-
-维护本仓库的人先读：
-
-- [Default Harness Capabilities](./default-capabilities.md)
-- `harness/feedback/index.md`
-- `harness/exposure.md`
-
-## Feedback Loop
-
-实践反馈可以来自外部 target，也可以来自本仓库自己的 CLI/runtime/verifier 使用。
-反馈先进入 intake；只有能变成 reusable harness contract 的内容才提升。
-
-提升后的落点必须明确：
-
-- guide：帮助人理解怎么使用或判断。
-- runtime：由 `effect-harness init` 投递给 target。
-- guardrail/verifier：把 recurring failure 变成会失败的检查。
-- repo-local skill：维护本仓库 harness contract 的流程。

package/guide/setup.md

@@ -1,64 +0,0 @@
-# Setup Guide
-
-这份 guide 给刚接入 `effect-harness` 的人读。它解释 init 之后发生了什么，以及遇到缺口时
-应该去哪里补信息。
-
-## Init 做什么
-
-在目标仓库运行：
-
-```bash
-effect-harness init
-pnpm install
-pnpm effect:status
-pnpm effect:verify
-pnpm verify
-```
-
-`effect-harness init` 会写入：
-
-- `.effect-harness.json`
-- `package.json` scripts：`effect:status`、`effect:verify`
-- `tsconfig.json` 的 `@effect/language-service` plugin
-- `.codex/skills/effect-code/`
-- `.codex/skills/effect-feedback/`
-- `.codex/agents/effect-worker.md`
-- `AGENTS.md` 里的 harness route
-
-这些是 target runtime。目标仓库不需要复制本仓库的 `.codex/skills/`。
-`.effect-harness.json` 记录 harness root、可执行 commands、route、source pin 和 package baseline，
-agent 后续应先读它，再运行 target scripts。
-需要派出 focused Effect subagent 时，使用 `.codex/agents/effect-worker.md`。
-
-## 从哪里补信息
-
-Effect API、pattern、testing 和 migration 先读官方 source：
-
-- `repos/effect/LLMS.md`
-- `repos/effect/ai-docs/src/`
-- `repos/effect/migration/v3-to-v4.md`
-- patched `tsgo --noEmit`
-
-想理解 harness 默认提供了哪些补充保护，读：
-
-- [Default Harness Capabilities](./default-capabilities.md)
-
-agent 执行任务时读 harness contract：
-
-- `harness/index.md`
-- `harness/exposure.md`
-- `harness/feedback/index.md`
-- `harness/target-agent-contract.md`
-
-## 如何反馈回来
-
-如果目标仓库遇到 recurring Effect practice failure：
-
-1. 先检查官方 source 是否已经覆盖。
-2. 如果官方 source 已覆盖，直接 route 回官方 source。
-3. 如果没有覆盖，并且问题 business-neutral、可复用，用 target 的
-   `.codex/skills/effect-feedback/` 记录到 `.codex/effect-feedback/`。
-4. 维护者再判断是否提升到 `effect-harness/harness/feedback/`。
-
-能提升的反馈必须落成 guide、runtime、guardrail、verifier 或 repo-local skill。业务示例、
-产品语义、release ritual 和项目形态不进入 harness。

package/harness/default-capabilities.md

@@ -1,32 +0,0 @@
-# Default Harness Capabilities
-
-This is the agent-facing contract for default harness supplements. Human-readable explanation lives in
-`guide/default-capabilities.md`.
-
-## Assertion-based tsgo suggestion cleanup
-
-Treat `@effect/tsgo` suggestions as type-boundary work, not assertion cleanup.
-
-Preferred shapes:
-
-- explicit return types
-- named discriminated union helpers
-- `satisfies`
-- `Effect.satisfiesSuccessType`
-- `Function.satisfies`
-- `Schema.Finite` where applicable
-
-Rejected recurring shapes:
-
-- `Effect.orElseSucceed(() => [] as ...)`
-- `Effect.succeed(null as ...)`
-- ad-hoc `{ ok: true/false as const }` result wrappers
-
-Landing surfaces:
-
-- `harness/runtime/codex/skills/effect-code/SKILL.md`
-- `src/harness/GuardrailRules.ts`
-- `pnpm effect:verify`
-
-Exceptions must be explicit third-party IO or external boundary assertions, declared outside the Effect
-fallback or lifted value.

package/harness/exposure.md

@@ -1,46 +0,0 @@
-# Harness Exposure Boundary
-
-这份文件定义 `effect-harness` 允许向外暴露什么。
-
-本仓库只暴露稳定、business-neutral 的 harness contract：
-
-- pinned official Effect source 和 package baseline
-- official source drift status
-- `effect-harness init` 投递的 target runtime
-- target `AGENTS.md` route fragment
-- guardrails 和 verifier contracts
-- reusable practice feedback intake
-
-它不暴露 target business examples、product semantics、project shape、local distribution machinery
-或 upstream maintainer-only workflow。
-
-`publish` 只服务本仓库 npm package / CLI 分发，不是 target repo ritual。npm tarball 包含
-`repos/effect/` 是有意暴露：CLI、verifier、target route 和 agent 都需要 pinned official
-source/reference 与 `repos/effect.subtree.json` 保持同包可读。
-
-## Allowed Exposure
-
-| Surface | 是否投递给 target | Contract owner |
-| --- | --- | --- |
-| `repos/effect/LLMS.md` route | 是，作为 reference | official Effect source |
-| `harness/runtime/codex/` | 是，由 init 复制 | `effect-harness` |
-| `effect:status` / `effect:verify` scripts | 是，由 init 写入 | `src/harness/Init.ts` |
-| `.effect-harness.json` | 是，由 init 写入 | target verifier |
-| `harness/feedback/index.md` | 不直接复制 | harness maintainers |
-| `.codex/skills/` | 否 | repo-local maintenance only |
-
-Target setup 细节见 [target-agent-contract.md](./target-agent-contract.md)。
-Official source classification 见 [official-inventory.md](./official-inventory.md)。
-
-## Promotion Gate
-
-新增 exposure route 前必须回答：
-
-1. official Effect source 或 `@effect/tsgo` 是否已经提供 semantic rule 或 diagnostic？
-2. 哪个 pinned upstream artifact 能证明？
-3. 证据来自 external target，还是 harness-as-target practice？
-4. 这是 reusable harness contract，而不是 target business shape 吗？
-5. landing 是 guide、route、target runtime、guardrail、verifier 还是 repo-local skill？
-6. 后续 drift 由哪个 verifier 或 review path 捕获？
-
-只有通过这个 gate 的内容才属于本仓库。

package/harness/feedback/index.md

@@ -1,60 +0,0 @@
-# Harness Feedback
-
-这是 Effect harness 的 practice-to-contract feedback contract，给 agent 和维护者执行判断时读取。
-人类理解默认补充能力时读 `guide/default-capabilities.md`。
-
-Feedback 可以来自外部 target projects，也可以来自本仓库自己的 CLI/runtime/verifier dogfood。
-它不改写 Effect API 语义；Effect API 教学、业务示例、项目形态和 release ritual 不进入这里。
-官方 source 已覆盖的内容直接 route 到 pinned source。
-
-## Intake Rule
-
-新增 feedback item 前，先使用 target runtime 的 `.codex/skills/effect-feedback/` 或本仓库
-`.codex/skills/effect-feedback-maintainer/` 做判断。只有同时满足这些条件才写入：
-
-- target project 或本仓库 self dogfood 给出了 recurring Effect practice failure 的具体证据
-- `repos/effect/LLMS.md`, `repos/effect/ai-docs/src/`, `repos/effect/migration/v3-to-v4.md`,
-  pinned source 和 `@effect/tsgo` diagnostics 没有解释或捕获它
-- 问题是 business-neutral，并能跨 Effect targets 复用
-- landing 是 harness route、target runtime contract、guardrail、verifier 或 skill update
-
-不要添加 upstream maintainer-only workflow、project-specific product examples、local machine
-paths、downstream project shape details 或 generic Effect API tutorials。
-
-## Intake Entry Format
-
-这是本仓库的 feedback 记录格式，不是官方 Effect 格式。它只用于判断一个 practice failure
-是否应该进入 harness contract。
-
-```markdown
-## <short issue name>
-
-- Evidence:
-- Official coverage check:
-- Missing harness contract:
-- Proposed landing:
-- Verifier or guardrail:
-- Status:
-```
-
-## Default Harness Capabilities
-
-这一节记录已经由 harness 默认提供的补充能力。它们来自 practice feedback，但已经落成
-runtime、guardrail、verifier 或 repo-local skill，不再只是待判断 intake。
-
-### Assertion-based tsgo suggestion cleanup
-
-- Evidence: A target update produced non-blocking `@effect/tsgo` suggestions. The first cleanup used
-  `Effect.orElseSucceed(() => [] as ...)`, `Effect.succeed(null as ...)`, and
-  `{ ok: false as const }` result wrappers instead of declaring the type boundary.
-- Official coverage check: The pinned Effect source shows typed `orElseSucceed` fallbacks,
-  `Effect.fn(...)` transform arguments, and `satisfies` helpers, but it does not give target agents
-  a harness-level rule for avoiding assertion-based suggestion cleanup.
-- Missing harness contract: Target agents need to distinguish soft review guidance from hard verifier
-  failures when a tsgo suggestion can be silenced with `as`.
-- Proposed landing: Add target skill guidance for type-boundary fixes and an AST guardrail for the
-  recurring assertion-silencing shapes.
-- Verifier or guardrail: `effect-harness guardrails` rejects assertion fallback cleanup in
-  `Effect.orElseSucceed`, asserted values lifted directly by `Effect.succeed`, and ad-hoc
-  `ok: true/false as const` result wrappers.
-- Status: Landed.

package/harness/official-inventory.md

@@ -1,85 +0,0 @@
-# Effect Official Harness Inventory
-
-这份文档记录 pin 住的 Effect source 中哪些文件可以作为 coding agents 和 LLM-assisted
-Effect development 的依据。
-
-Pinned source：
-
-```text
-repos/effect @ 95545bdc334f4cd27a14f3308e68114e5bed92f2
-```
-
-## Role
-
-pin 住的 Effect repository 是 Effect API、patterns、examples、testing guidance、
-migration map 和 diagnostics 的唯一真源。本仓库不重写 Effect 语义；它把真源转成
-可投递、可验证、可回流改进的 harness contract。
-
-## Source Classification
-
-harness 在向 target 暴露 upstream material 前，必须先分类：
-
-| Class | Upstream surface | Decision |
-| --- | --- | --- |
-| Authoritative guide | `repos/effect/LLMS.md` | Effect application coding guidance 的 single source of truth。 |
-| Authoritative guide | `repos/effect/ai-docs/src/` | 需要 examples 或 context 时读取。 |
-| Authoritative guide | `repos/effect/migration/v3-to-v4.md` | v3-to-v4 import/API migration 的 source of truth。 |
-| Reference only | `repos/effect/.patterns/effect.md` | 只在 narrow pitfalls 适用于 downstream app code 时参考。 |
-| Reference only | `repos/effect/.patterns/testing.md` | 解决 testing 冲突；target verifier 应体现相关规则。 |
-| Reference only | `repos/effect/packages/effect/MCP.md` | 只在维护 Effect worker、MCP route 或 tool server 时使用。 |
-| Reference only | `repos/effect/package.json` 和 `tsconfig*.json` | 理解官方 `tsgo` 和 validation setup，不复制 repo-maintenance scripts。 |
-| Maintainer-only | `repos/effect/AGENTS.md` | 官方 repo operating policy，不是 downstream coding guide。 |
-| Do not promote | `repos/effect/.agents/skills/*` | Effect maintainer skills，不默认安装或暴露给 target projects。 |
-| Do not promote | `repos/effect/.specs/*` | Effect maintainer feature specs，不是通用 harness guidance。 |
-| Do not promote | package-specific docgen 和 validation configs | 内部 publishing/docs machinery，不是 downstream defaults。 |
-
-不属于 authoritative guide 的文件，不应在没有 promotion decision 时复制、安装或暴露给
-target projects。
-
-## Upstream Surfaces
-
-| Surface | Role | Harness implication |
-| --- | --- | --- |
-| `repos/effect/LLMS.md` | 从 `ai-docs/src` 生成的 LLM coding guide，覆盖 services、errors、resources、runtime、testing、HTTP、CLI、AI、cluster 等。 | 第一 Effect coding reference；本地 docs 只 route，不替代。 |
-| `repos/effect/ai-docs/src/` | `LLMS.md` 的 source examples。 | 当 `LLMS.md` 太压缩时读取。 |
-| `repos/effect/migration/v3-to-v4.md` | migration-agent import/API rename map。 | 适配 v3 code 时优先使用。 |
-| `repos/effect/.patterns/effect.md` | narrow pitfalls：`Effect.gen`、terminal `return yield*`、`Context.Service` 等。 | reference only；只把 target-relevant pitfalls 转为 guardrails。 |
-| `repos/effect/.patterns/testing.md` | testing rules：`it.effect`、pure test、禁止 `Effect.runSync`、优先 `assert` from `@effect/vitest`、`TestClock`。 | reference only；verifier 跟随官方。 |
-| `repos/effect/packages/effect/MCP.md` | Effect-native MCP server guide。 | 只服务 MCP/worker route 维护。 |
-| `repos/effect/package.json` 和 `tsconfig*.json` | 官方 validation scripts 与 `@effect/language-service` / `tsgo` setup。 | 确认 `tsgo` diagnostic path；target 可以更严格。 |
-
-## Coverage
-
-对 application-style Effect code，upstream coverage 包含：
-
-- coding style：`Effect.gen`、`Effect.fn`、terminal `return yield*`、tagged errors
-- service style：`Context.Service`、`Layer.effect`、`Layer.unwrap`、`Layer.provideMerge`
-- runtime entrypoints：`NodeRuntime.runMain`、`Layer.launch`、`NodeServices.layer`
-- testing：`@effect/vitest`、`it.effect`、`TestClock`、shared layers
-- integration：`ManagedRuntime`、bridge code、child processes
-- operational concerns：schedules、retries、logging、tracing、Otlp modules
-- boundaries：HTTP client/server、CLI、streams、AI modules、cluster entities
-- migration：v3-to-v4 import 和 symbol maps
-
-修改 Effect repo 自身的 agent workflow 不属于默认 downstream harness surface：
-
-- `AGENTS.md` 里的 local workflow 和 validation matrix
-- package-specific validation commands
-- JSDoc skill 和 custom JSDoc linting
-- scratchpad extraction
-- `.specs/` 下的 complex feature specs
-
-## Promotion Boundary
-
-这份 inventory 只分类 official source surface。是否提升 practice feedback，按
-[exposure.md](./exposure.md) 和 [feedback/index.md](./feedback/index.md) 判断。
-
-## Harness Contract
-
-- coding agents 首先读取 `repos/effect/LLMS.md`。
-- 用 `repos/effect/ai-docs/src/` 和 `repos/effect/migration/v3-to-v4.md` 做 supporting official source。
-- 不默认暴露 `repos/effect/AGENTS.md`、`repos/effect/.agents/skills/`、`repos/effect/.specs/`。
-- 本仓库自身和外部 target 都可以产生 reusable practice evidence。
-- upstream docs 无法机械保护的 target constraints 进入 verifier 或 guardrail。
-- 面向用户的 examples 和业务项目形态不进入本仓库。
-- 本仓库只暴露 contracts，不做业务分发实现。

package/harness/runtime/codex/AGENTS.fragment.md

@@ -1,28 +0,0 @@
-# Effect Harness
-
-This repo uses `__EFFECT_HARNESS_ROOT__` as its Effect harness root.
-
-Before writing non-trivial Effect code, read:
-
-- `__EFFECT_HARNESS_ROOT__/repos/effect/LLMS.md`
-- `__EFFECT_HARNESS_ROOT__/harness/index.md`
-- `__EFFECT_HARNESS_ROOT__/repos/effect.subtree.json`
-- `.effect-harness.json`
-
-Runtime skills and agents installed by the harness:
-
-- Use `.codex/skills/effect-code/SKILL.md` for Effect implementation and review.
-- Use `.codex/skills/effect-feedback/SKILL.md` for reusable target feedback.
-- Use `.codex/agents/effect-worker.md` when delegating focused Effect subagent work.
-
-Use:
-
-```bash
-pnpm effect:status
-pnpm effect:verify
-pnpm verify
-```
-
-Do not import from `__EFFECT_HARNESS_ROOT__/repos/effect`.
-Do not copy effect-harness `.codex/skills`; this target only uses the runtime installed under
-`.codex/`.

package/harness/runtime/codex/agents/effect-worker.md

@@ -1,26 +0,0 @@
-# Effect Worker
-
-Use this worker configuration when delegating focused Effect implementation or review in this target repo.
-
-## Inputs
-
-- Target repo instructions and current task.
-- `.effect-harness.json`.
-- `.codex/skills/effect-code/SKILL.md`.
-- `__EFFECT_HARNESS_ROOT__/repos/effect/LLMS.md`.
-- `__EFFECT_HARNESS_ROOT__/harness/index.md`.
-- Patched `tsgo --noEmit` diagnostics.
-
-## Responsibilities
-
-- Implement or review Effect code against the pinned official guide.
-- Prefer official source and diagnostics over memory.
-- Keep target business logic in the target repo.
-- Report reusable harness gaps through `.codex/skills/effect-feedback`.
-- Report changed files and verification output to the parent agent.
-
-## Hard Stops
-
-- Do not import from `__EFFECT_HARNESS_ROOT__/repos/effect`.
-- Do not update the harness source pin.
-- Do not copy effect-harness maintainer skills into this repo.

package/harness/runtime/codex/skills/effect-code/SKILL.md

@@ -1,72 +0,0 @@
----
-name: effect-code
-description: "Use in an Effect target repo when writing, reviewing, or debugging Effect v4 beta code against the linked effect-harness official pin. Covers Effect services, runtime entrypoints, tests, CLI/HTTP/process boundaries, @effect/tsgo diagnostics, and focused Effect subagent delegation. Not for updating effect-harness, changing the source pin, or writing generic TypeScript unrelated to Effect."
-when_to_use: "Effect code, Effect review, Effect tests, Effect runtime, @effect/tsgo diagnostic, Effect subagent"
-dispatch_intent: "Write or review target Effect code against the pinned harness"
----
-
-# Effect Code
-
-Use this skill for target-local Effect code work against the linked `effect-harness`.
-
-## Capability
-
-Drive Effect implementation and review through the pinned official source, target runtime contract, and
-patched diagnostics instead of memory, stale examples, or copied harness internals.
-
-Pressure scenario: an agent imports from `repos/effect`, uses old v3 patterns, silences `@effect/tsgo`
-with assertions, writes plain Vitest tests, or delegates Effect work without passing the target runtime
-agent contract.
-
-## Trigger
-
-Use when the task touches Effect services, layers, runtime entrypoints, tests, CLI/HTTP/process
-integration, `@effect/tsgo` diagnostics, or focused Effect review in this target repo.
-
-Do not use for updating `effect-harness`, refreshing `repos/effect`, generic TypeScript cleanup, or target
-business decisions that do not require Effect guidance.
-
-## Soft Boundary
-
-- Target repo instructions and current code shape come first.
-- Official pinned source beats local memory.
-- Delegate focused Effect implementation or review with `.codex/agents/effect-worker.md` when a subagent is useful.
-- Keep target business logic in the target repo; only reusable harness gaps go to feedback.
-
-## Hard Boundary
-
-- Do not import from `__EFFECT_HARNESS_ROOT__/repos/effect`.
-- Do not copy effect-harness maintainer skills into the target.
-- Use installed packages: `effect`, `@effect/platform-node`, `@effect/vitest`.
-- Use patched `tsgo --noEmit` as the primary Effect diagnostic loop.
-- Use `assert` from `@effect/vitest`; do not use `expect`.
-
-## Workflow
-
-1. Read target instructions and existing code.
-2. Read official/harness sources in this order:
-   - `__EFFECT_HARNESS_ROOT__/repos/effect/LLMS.md`
-   - `__EFFECT_HARNESS_ROOT__/repos/effect/ai-docs/src/`
-   - `__EFFECT_HARNESS_ROOT__/repos/effect/migration/v3-to-v4.md`
-   - `__EFFECT_HARNESS_ROOT__/harness/index.md`
-   - `.effect-harness.json`
-3. Use `Context.Service` for services on this baseline.
-4. Treat `@effect/tsgo` suggestions as type-boundary work, not assertion cleanup.
-5. Prefer `Schema.Finite`, explicit fallback return types, named result unions/helpers, `satisfies`,
-   `Effect.satisfiesSuccessType`, or `Function.satisfies`.
-6. Pass `Effect.fn` transforms as extra arguments to `Effect.fn(...)`; do not `.pipe(...)` transforms onto
-   an `Effect.fn` declaration.
-7. If delegating to an Effect subagent, give it `.codex/agents/effect-worker.md`, the target task, and the
-   relevant files/tests; require it to report changed files and verification.
-
-## Validation
-
-Before reporting completion, run:
-
-```bash
-pnpm effect:status
-pnpm effect:verify
-pnpm verify
-```
-
-Report any reusable harness gap through `$effect-feedback`.

package/harness/runtime/codex/skills/effect-code/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: Effect Code
-  short_description: 编写和审查 Effect v4 beta 代码
-  default_prompt: 使用 $effect-code，并按 .codex/agents/effect-worker.md 作为 Effect 子任务配置。

package/harness/runtime/codex/skills/effect-feedback/SKILL.md

@@ -1,66 +0,0 @@
----
-name: effect-feedback
-description: "Use in an Effect target repo when a recurring Effect practice failure, @effect/tsgo gap, guardrail gap, verifier mismatch, or workaround may be reusable for effect-harness. Not for product-specific examples, generic Effect API tutorials, or issues already covered by the pinned official source."
-when_to_use: "Effect feedback, recurring Effect pitfall, @effect/tsgo gap, guardrail gap, verifier mismatch, reusable harness gap"
-dispatch_intent: "Capture reusable target practice feedback for effect-harness"
----
-
-# Effect Feedback
-
-Use this skill to capture target-local evidence that may improve `effect-harness`.
-
-## Capability
-
-Separate reusable harness gaps from target business issues by checking pinned official source first, then
-recording a local feedback item with enough evidence for a maintainer to promote or reject.
-
-Pressure scenario: an agent upstreams a product-specific workaround, copies official docs into the harness,
-or loses a real repeated target failure because it was never written as evidence.
-
-## Trigger
-
-Use when this target hits a recurring Effect pitfall, `@effect/tsgo` diagnostic gap, guardrail gap,
-verifier mismatch, or local workaround that might apply across Effect targets.
-
-Do not use when official source already explains the issue, when the issue is product-specific, or when the
-task is ordinary Effect implementation.
-
-## Soft Boundary
-
-- Feedback starts as target-local evidence under `.codex/effect-feedback/`.
-- Promotion to `effect-harness` requires maintainer judgment.
-- Business examples, product semantics, release rituals, and target project shape stay in the target repo.
-
-## Hard Boundary
-
-- Check pinned official source before writing feedback.
-- Do not bypass `repos/effect/LLMS.md`, `repos/effect/ai-docs/src/`, `repos/effect/migration/v3-to-v4.md`,
-  `repos/effect/`, or patched `tsgo --noEmit`.
-- Do not copy upstream maintainer-only workflow from `repos/effect/AGENTS.md`,
-  `repos/effect/.agents/skills/*`, or `repos/effect/.specs/*`.
-
-## Workflow
-
-1. Record concrete evidence from this repo: error, diff, test, log, command output, or failed agent loop.
-2. Check official pinned sources and diagnostics.
-3. If official source covers it, route to that source and do not create feedback.
-4. If the gap is reusable and business-neutral, write a local entry in `.codex/effect-feedback/`.
-5. Ask the maintainer whether to upstream it to `__EFFECT_HARNESS_ROOT__/harness/feedback/index.md`.
-
-## Local Entry
-
-```markdown
-## <issue>
-
-- Evidence:
-- Official coverage check:
-- Missing harness contract:
-- Proposed landing:
-- Verifier or guardrail:
-- Status:
-```
-
-## Validation
-
-The entry must state the official coverage check and a proposed landing as route, runtime contract,
-guardrail, verifier, or harness skill update.

package/harness/runtime/codex/skills/effect-feedback/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: Effect Feedback
-  short_description: 记录 Effect target 实践反馈
-  default_prompt: 使用 $effect-feedback，把 target repo 的 Effect 踩坑整理成反馈条目。