faf-cli 7.8.0 → 7.10.0

package/dist/interrogate/build-files.d.ts

@@ -0,0 +1,10 @@
+/**
+ * Makefile / justfile / Taskfile interrogation — the real project commands.
+ *
+ * `detectCommands` in scanner.ts only reads root package.json scripts + language
+ * defaults. Many repos (esp. polyglot ones) drive test/build/lint through a
+ * Makefile — `make test`, `make check-all`. Read the target names and map the
+ * obvious ones. Facts from files, not README prose.
+ */
+import type { ExtractedContext } from './types.js';
+export declare function interrogateBuildFiles(dir: string): ExtractedContext;

package/dist/interrogate/compose.d.ts

@@ -0,0 +1,11 @@
+/**
+ * docker-compose interrogation — the services a repo runs ARE its stack.
+ *
+ * A polyglot / platform repo declares Postgres, Redis, ClickHouse, MinIO, Kafka…
+ * in compose and nowhere the root-only detectors look. We read the `image:` lines
+ * (naive regex — same style as cargo.ts's TOML reader) and map well-known infra
+ * images onto stack slots. Facts, not prose — so these win over README guesses.
+ */
+import type { ExtractedContext } from './types.js';
+/** Read every compose file and map service images onto stack slots. */
+export declare function interrogateCompose(dir: string): ExtractedContext;

package/dist/interrogate/env.d.ts

@@ -0,0 +1,8 @@
+/**
+ * .env.example interrogation — where secrets live.
+ *
+ * A repo that ships `.env.example` (or `.env.sample`) is telling you: secrets go
+ * in `.env`, this file is the template. Fills `security.secrets` + `.example`.
+ */
+import type { ExtractedContext } from './types.js';
+export declare function interrogateEnv(dir: string): ExtractedContext;

package/dist/interrogate/index.d.ts

@@ -1,16 +1,23 @@
 /**
  * Repo interrogation orchestrator — runs all extractors and merges results.
  *
- * Order of precedence: extractors that run first WIN (their non-empty values
- * are kept; later extractors fill only empties). README is highest-precedence
- * because its prose is most likely to be hand-curated; manifest fields
- * (Cargo.toml description, package.json description) are fallbacks.
+ * Two classes of extractor:
+ *   - PROSE (README, Cargo.toml description) → `project.goal` + `human_context`.
+ *     README wins on overlap because its prose is most likely hand-curated.
+ *   - FILE-FACTS (docker-compose services, Makefile targets, .env.example) →
+ *     `stack.*` + `commands.*` + `security.*`. These are ground truth pulled
+ *     straight from config — they win over README guesses and over the
+ *     presence-only detectors in scanner.ts (wired in assemble.ts).
  *
- * The orchestrator never overwrites with empty — only fills empties.
+ * The orchestrator never overwrites with a non-empty value — earlier extractors
+ * win; later ones fill empties only.
  */
 import type { ExtractedContext } from './types.js';
 export type { ExtractedContext } from './types.js';
 export { interrogateReadme } from './readme.js';
 export { interrogateCargo } from './cargo.js';
+export { interrogateCompose } from './compose.js';
+export { interrogateBuildFiles } from './build-files.js';
+export { interrogateEnv } from './env.js';
 /** Run all repo interrogators and return merged context. */
 export declare function interrogateRepo(dir: string): ExtractedContext;

package/dist/interrogate/types.d.ts

@@ -35,6 +35,23 @@ export interface ExtractedContext {
         /** Approach — "## Architecture" / "## How it works" */
         how?: string;
     };
+    /** Stack facts pulled from real config files (docker-compose services, …).
+     *  Higher-precedence than README prose or presence-only guesses for these. */
+    stack?: {
+        database?: string;
+        cache?: string;
+        search?: string;
+        storage?: string;
+        hosting?: string;
+        runtime?: string;
+    };
+    /** Real project commands from Makefile / justfile / Taskfile targets. */
+    commands?: Record<string, string>;
+    /** Secrets handling — from .env.example / .env.sample presence. */
+    security?: {
+        secrets?: string;
+        example?: string;
+    };
 }
 /** Confidence threshold rules for extracted text — empty if violated */
 export declare const EXTRACTION_LIMITS: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "faf-cli",
-  "version": "7.8.0",
+  "version": "7.10.0",
   "description": "Persistent AI context + memory — .faf and .fafm, IANA-registered. Anthropic-merged.",
   "type": "module",
   "icon": "https://faf.one/orange-smiley.svg",

package/project.faf

@@ -1,8 +1,8 @@
 faf_version: "3.0"
 project:
   name: faf-cli
-  version: "7.8.0"
-  goal: "CLI for IANA-registered `.faf` + `.fafm` — context DNA and portable agent memory. TypeScript, Bun-native since v6. package faf-cli v7.8.0 The Projector Edition."
+  version: "7.10.0"
+  goal: "CLI for IANA-registered `.faf` + `.fafm` — context DNA and portable agent memory. TypeScript, Bun-native since v6. package faf-cli v7.10.0 The Full-Facts Edition."
   main_language: TypeScript
   type: cli  # found: package.json bin
 # Commands + key_files feed `faf export --agents` (hand values win over detection).
@@ -58,7 +58,7 @@ human_context:
   what: Persistent AI Context Standard — project DNA for AI. IANA-registered. Anthropic-merged.
   why: Eliminates 91% context re-discovery tax — define once, AI remembers forever
   where: npm registry, Homebrew, GitHub
-  when: Production since September 2025; Bun-native since v6; current package 7.8.0
+  when: Production since September 2025; Bun-native since v6; current package 7.10.0
   how: bunx faf-cli auto, then project.faf versions with your code — faf show renders it human-visible
 monorepo:
   packages_count: slotignored