claude code agent 227
24b903aaf3
The git-sync converter + engine source lived only on the #119 branch; develop had just the dead compiled build/. Bring the whole package (src + ~700 tests) onto develop under CI, with NO consumer wired — git-sync stays fully inert in develop (nothing in apps/server imports it), so runtime behavior is unchanged. This unblocks #293 (extract the shared converter package from the landed source) and lets #119's functionality land LAST, already writing the canonical format (per the #326 landing order). - packages/git-sync: src (lib converter + engine) + test corpus + configs. - Remove develop's dead committed packages/git-sync/build/; gitignore it (built in CI/Docker via pnpm build, never committed — no src/build drift). - pnpm-lock.yaml: add the @docmost/git-sync importer (a missing workspace package in the lock is a CI blocker). `pnpm install --frozen-lockfile` passes. - NO server integration / loader / Dockerfile runtime changes (those come with #119 at step 6). Verified: tsc clean; vitest 711 passed | 1 expected-fail, 0 failures, 0 type errors; pnpm --frozen-lockfile EXIT 0; apps/server has no git-sync import. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
16 lines
653 B
JSON
16 lines
653 B
JSON
{
|
|
// Test-infra tsconfig used ONLY by vitest's `test.typecheck` pass (Finding #1).
|
|
// The build tsconfig (`tsconfig.json`) scopes the compiler to `src/**` with
|
|
// `rootDir: ./src`, so it never type-checks the `test/` tree. This config
|
|
// inherits the same strict compiler options but widens the file set to the
|
|
// type-test files so `vitest run` can run `tsc` over them. It is NOT used by
|
|
// `npm run build` (that still uses `tsconfig.json`), so it has no effect on the
|
|
// shipped output.
|
|
"extends": "./tsconfig.json",
|
|
"compilerOptions": {
|
|
"noEmit": true,
|
|
"rootDir": "."
|
|
},
|
|
"include": ["test/**/*.test-d.ts", "src/**/*"]
|
|
}
|