2 Commits

Author	SHA1	Message	Date
marfrit	31e5de5ad5	docs/PHASE9: analyze + baseline + plan (single bundled commit) ... Bundled the three doc steps since the surface is small (4-commit impl, no major redesigns from formulate). Analyze findings (12, A1-A12): A1-A2 — main.lua surface clean; no new FFI needed A3 — Q-P2 RESOLVED via baseline: sha256sum (GNU coreutils) A4 — Q-P1: trust prompt AFTER user-config status line A5 — Q-P3: don't log walk-up by default; :config show on demand A6 — Q-P5: :cfg show top-level by default; `full` for deep A7 — Q-P6: project may set secrets.vault (covered by trust prompt) A8 — Q-P4 DEFERRED: rl.readline early-startup smoke at impl time A9 — walk-up perf <1ms even pessimistic A10 — trust-file race: JSONL append-only handles concurrent writes A11 — sandboxed dofile out of scope (trust prompt IS the gate) A12 — bootstrap order is correct: user→project→secrets_session Baseline: B1 — sha256sum + openssl agree byte-for-byte on noether; sha256sum chosen (universal + simpler parse). §10 Open Qs table now shows resolutions inline (5/6 done; Q-P4 deferred to implement-time smoke). §13 Implementation Plan added — 4 commits: 1. history.lua: trust file helpers (read/add/is_trusted + _sha256_file) 2. main.lua: walk-up + load_config_with_overlay + trust prompt 3. repl.lua: :config show meta + startup status line 4. config.lua header note + status -> Implement Per-commit risk index covers sha256sum-missing case, JSONL partial write, A8 rl.readline early-startup, symlink-loop walk-up, :config show token leakage via conservative masking heuristic. Open at plan-time (resolve at impl): - A8 rl.readline behavior; fall back to io.read if broken - $AISH_TRUST_FILE env override for CI isolation Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-16 23:38:10 +00:00
marfrit	4f5c3aeba9	docs/PHASE9: formulate — project-local config overlay (.aish.lua) ... Phase 9 formulate manifest + PHASE0 §11 amendment (adds Phase 9 row) + PHASE0 §10 amendment (config resolution order now references Phase 9's overlay step). Substrate-touch lands same commit per CLAUDE.md §3. Four pillars: 1. .aish.lua walk-up from cwd; stops at $HOME or filesystem root. First found file becomes the project layer. Absence = no-op. 2. Shallow merge over user config: project top-level keys REPLACE user keys. Predictable; deep merge surprises with array/table semantics. Users compose full blocks explicitly. 3. Trust prompt + sha256-pinned persistence in ~/.aish/trusted- projects (JSONL, mode 0600). First encounter prompts; subsequent startups load only if recorded sha matches. Content change -> re-prompt. Matches direnv-allow security posture. 4. :config show meta — lists each source path with the top-level keys it contributed + sanitized effective config dump (token-bearing fields masked). Key design decisions documented: - Trust mechanism is explicit (not default-trust-all-cwds) — .aish.lua runs arbitrary Lua via dofile; hostile cloned-repo case is a real concern. - $HOME boundary on walk-up — don't search /tmp or /. Repos outside $HOME get no project layer. - Reload on cd: NO. Config resolved at startup only. - sha256 via shelled `sha256sum` (POSIX-portable; avoid vendoring a Lua impl). §9 risk table covers: hostile repo (trust prompt), corrupted trust file (best-effort skip), updated repo (sha mismatch re-prompts), dofile errors (pcall-protected), walk-up safety ($HOME boundary). 6 open questions for analyze: Q-P1 — trust prompt before/after startup status Q-P2 — sha256sum vs openssl dgst (baseline) Q-P3 — log walk-up path? Q-P4 — rl.readline safe at startup? Q-P5 — :config show full vs top-level Q-P6 — project-set secrets.vault security Scope confirmed via AskUserQuestion: project-local overlay (chosen over cost preflight enforcement and cross-session cost persistence, both deferred as Phase 10 candidates per §11). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-16 23:36:35 +00:00