5 Commits

Author	SHA1	Message	Date
Your Name	9ef42c5fd1	fix: pos ai — honor legacy AI_API_KEY as fallback (provider key stays primary) ... Architect decision C on the API-key contract mismatch: docs claimed AI_API_KEY was the required primary key, but resolve_key() only read provider-specific keys (7ae2e77 removed shared-key priority to fix cross-provider leakage; docs never updated). - bin/pos-ai resolve_key(): provider key wins, legacy AI_API_KEY honored read-only when the provider's own key is empty, llamacpp unchanged; cmd_providers() configured check mirrors the same set - require_key() error messages byte-stable (test-locked) - AI_API_KEY NOT re-added to the # POS_CONFIG:/# PROVIDER_CONFIG: registry - Docs reworded: POS.md rows 91/96/98 + precedence sentence, howto/ai.md first-run hints, HOWTO.md row, AGENT_Context prose (2 spots), config/ai.env legacy comment - New regression tests/t-ai-key-resolution.sh: 24 checks / 10 cases (provider-key-only, AI_API_KEY-only, both -> provider wins, env-wins, llamacpp no-key, missing-key message, providers configured status) Verified: suite 19 files / 440 checks / 0 fail / 0 skip; make gen byte-idempotent; make check OK; make lint 0 FAIL, 0 WARN; bash -n clean; git diff --check clean; Reviewer APPROVE_WITH_NOTES (mutation disproof: inverted precedence -> C3/C6 fail)	2026-09-07 13:32:42 -04:00
he	5e312b3207	feat: pos ai server — llama.cpp local inference server ... Service manager (start/stop/status/models/logs) with systemd user service generation, GPU auto-detection, model selection from pos ai hf downloads. Provider adapter integrates with pos ai ask as --provider llamacpp. Config extends existing ai scope with LLAMACPP_* keys. 87 test cases / 0 failed. make gen/check/lint 0 FAIL / 0 WARN.	2026-09-04 12:40:50 -04:00
Your Name	7ae2e77a44	fix: ai — per-provider API keys (remove shared AI_API_KEY) ... Each provider now has its own key: AI_GEMINI_API_KEY and OPENROUTER_API_KEY. No more shared AI_API_KEY that caused cross-provider key leakage (gemini getting openrouter key → 400 error). resolve_key() sets AI_API_KEY internally from the active provider's key for adapter use. Config UI shows both keys.	2026-08-26 02:36:48 -04:00
Your Name	4f79ce123f	refactor: ai — merge gemini/openrouter into unified plugin architecture ... - bin/pos-ai: single provider-agnostic tool (ask/chat/sessions/capture/models/providers) - lib/ai-providers/gemini.sh: Gemini adapter (59 ln) - lib/ai-providers/openrouter.sh: OpenRouter adapter (59 ln) - bin/pos-ai-gemini/openrouter: thin forwarders for backward compat - Provider adapter interface: provider_name/default_model/generate/models_list - Unified session format (OpenAI messages), auto-migrate old gemini contents - Config: AI_PROVIDER/AI_API_KEY/AI_MODEL/AI_SYSTEM_PROMPT in ai.env - Config fallback: AI_API_KEY → provider-specific env var → error - Default system prompt configurable via AI_SYSTEM_PROMPT - New subcommand: pos ai providers (lists providers + config status) - Shell hook (pos-ai-hook.sh) for auto-capture	2026-08-25 09:57:10 -04:00
Your Name	23eede637a	feat: pos ai gemini — CLI + Telegram AI chat (ask, chat, models) ... - bin/pos-ai-gemini: one-shot ask (stdout-only, pipe-friendly), interactive multi-turn chat REPL (q/Ctrl+C, /reset), models list; --model override, default gemini-2.5-flash; key via x-goog-api-key header, never printed. - Config scope 'ai' (AI_GEMINI_API_KEY secret, AI_GEMINI_MODEL) in ~/.config/linux_post_install/ai.env via 'pos config ai'; config/ai.env template installed no-clobber by postinstall. - Telegram listener: non-command text starting with 'ai ' (case-insensitive) is answered by Gemini via 'pos ai gemini ask'; owner-chat only, errors reply with the pos config ai hint. Future intents slot in as case arms. - ai-gemini added to INTERACTIVE_CMDS (chat reads stdin). - Docs: POS.md ai section + listener bridge, howto/ai.md, HOWTO/README index rows, bin/pos usage example; make gen refreshed context/completions.	2026-08-09 14:40:15 +00:00