/** * `slowcook knowledge add` — α.67 * * Appends an agent-discovered insight to `.brewing/repo-knowledge/ * curated/.md` with structured evidence trails. The shared * primitive every agent (chef / testgen / vibe / brew / human) uses * to contribute to the curated knowledge layer. * * Output line shape: * - ( · PR # · YYYY-MM-DD · last-verified YYYY-MM-DD) * * Why this design (per checkpoint design notes): * - Soft staleness: each entry has evidence (PR + file) + last-verified. * `slowcook knowledge verify` (later alpha) may flag [PRECARIOUS] * when evidence file is substantially rewritten, but never deletes. * - Insights are about CLASSES of problems, not commit snapshots — * "vitest/config not found means deps missing" stays valid even if * vitest.config.ts moves. * * Topic = filename stem under curated/. Standard names so different * agents converge on the same file per concern: * - chef-known-fixes (chef appends fix recipes) * - test-patterns (testgen appends helper-naming, mock idioms) * - design-conventions (vibe appends brand-token decisions) * - brew-patterns (brew records "Component X follows pattern Y") * - recon-shape-contracts (recon emits structural assertions) * - (human-authored or one-off) * * Idempotency: dedup-by-claim. If the SAME claim text already exists * in the topic file, update its last-verified date instead of * appending a duplicate. * * Usage: * slowcook knowledge add chef "vitest/config not found in workflow means pnpm install missing" \ * --evidence-pr 686 --evidence-file .github/workflows/slowcook-chef-on-brew-halt.yml */ export interface KnowledgeAddArgs { repoRoot: string; agent: string; topic: string; claim: string; evidencePr?: number; evidenceFile?: string; date?: string; } export interface KnowledgeAddResult { topicPath: string; action: "appended" | "verified-existing" | "created"; } export declare function knowledgeAddCore(args: KnowledgeAddArgs): KnowledgeAddResult; export declare function knowledgeAdd(argv: string[]): Promise; //# sourceMappingURL=knowledge-add.d.ts.map