18 commits

Author	SHA1	Message	Date
Denis Parfionovich	d1cbdd8892	fix(ci): vendored openssl-sys для cross-compile x86_64-apple-darwin ... CI run 26014515768 — `x86_64-apple-darwin` упал на webauthn-attestation-ca → openssl-sys 0.9.115: pkg-config не настроен для cross-compile (macos-latest = arm64, target = x86_64). Фикс: добавлен прямой dep `openssl-sys = { version = "0.9", features = ["vendored"] }` в kei-auth-webauthn — компилит openssl из исходников, не требует системного. Транзитивно достаточно одного объявления feature во всём workspace (Cargo unifies features).	2026-05-18 13:08:40 +08:00
Parfii-bot	86834b82af	feat(kei-buddy): provision_decrypt — VPS-side blob decryption ... Mirrors keisei-marketplace/src/lib/crypto-box.ts::sealBoxToVps. Two new subcommands on kei-buddy bin: - genkeys --key <path> → writes PKCS#8 PEM x25519 priv, prints standard-base64 pub (44 char) - decrypt-and-export --vps-key <pem> --blob <json> --env-out <env> → ECDH(vps_priv, ephPub) → HKDF-SHA256 info=keibuddy-token-v1 → XChaCha20-Poly1305 decrypt → append BOT_TOKEN/TELEGRAM_BOT_TOKEN to env file (replaces stale, keeps other lines) Cloud-init in hetzner.ts already calls these. Without this commit the VPS could decode its own pubkey but had no way to recover the sealed bot-token blob — the bot would never log into Telegram. Crypto stack (mirror of @noble in TS): - x25519-dalek 2 (static_secrets feature) - chacha20poly1305 0.10 (XChaCha20Poly1305) - hkdf 0.12, sha2 0.10 - base64 0.22 (accepts URL_SAFE_NO_PAD + STANDARD) - zeroize 1 for priv-key wipe Tests (6/6 pass): - roundtrip_seal_then_decrypt — re-implement marketplace sealing in Rust, verify our decryption recovers plaintext - decrypt_and_export_writes_env_file — full e2e through CLI surface - decrypt_and_export_replaces_existing_token — stale BOT_TOKEN replaced, other env lines preserved - decrypt_rejects_wrong_key — XChaCha20 AEAD tag fails on wrong key - pem_roundtrip — write_pkcs8 + parse_pkcs8 round-trip - b64decode_accepts_urlsafe_and_standard — handles both encodings Cross-verified end-to-end: $ node marketplace_seal.mjs <pub> <token> → /tmp/blob.json $ kei-buddy decrypt-and-export --vps-key ... → BOT_TOKEN matches input Constructor Pattern: 1 file (provision_decrypt.rs, 344 LOC), 1 module, 1 responsibility (token-blob decryption + key generation). === STATUS-TRUTH MARKER === shipped: functional stubs: 0 cargo-check: PASS behaviour-verified: yes (e2e marketplace-seal → kei-buddy-decrypt round-trip) follow-up-required: - none	2026-05-15 17:49:59 +08:00
Parfii-bot	b5d093fbec	fix(kei-cortex/test): serial_test on env-mutating openai tests + wiremock warm-up ... Previous wiremock conversion fixed the listener-lifecycle race but left the underlying problem unsolved: `ensure_env()` mutates the process-global ANTHROPIC_ENDPOINT, and parallel `cargo test` threads race on that write. Manifested as 502 / "error sending request for url …" on the first concurrent test pair under both macOS and Linux. Annotate every #[tokio::test] in openai_loop_wiring.rs + openai_compat.rs with `#[serial_test::serial]` — these are the only tests that touch ANTHROPIC_ENDPOINT via shared_mock_anthropic. serial_test enforces process-wide ordering so the env mutation + HTTP request pair is atomic per test. All other tests stay parallel. Stress: 5 parallel `cargo test` runs all green.	2026-05-12 22:26:42 +08:00
Parfii-bot	b103a9aa64	fix(kei-cortex/test): replace hand-rolled mock with wiremock — closes macOS CI flake ... Previous `tests/common/mod.rs` spawned a mock Anthropic upstream via hand-rolled axum + std:🧵:spawn + own current-thread tokio runtime bound to 127.0.0.1:0. Stable on Linux runner; flaked on macOS GitHub Actions runners: thread 'streaming_responses_runs_real_loop_not_stub' panicked at kei-cortex/tests/openai_loop_wiring.rs:277:5: no responses delta event in stream: event: response.error data: {"error":"model: anthropic request: error sending request for url (http://127.0.0.1:49312/v1/messages)"} Root cause traced to macOS-runner loopback / fd-limit pressure on the dedicated-thread current-thread runtime. wiremock crate runs a production-quality hyper-based mock server, manages its own listener lifecycle, and survives the macOS runner constraints. ## Change - `Cargo.toml`: add wiremock = workspace dev-dep (already 0.6 in workspace) - `tests/common/mod.rs::MockAnthropicServer` rebuilt over wiremock::MockServer - `build_mock(text)` mounts `POST /v1/messages → 200 + canned body` on a wiremock instance - `mock_anthropic_responding_with()` spins one per call on a parked helper thread (preserves `MockAnthropicServer: 'static` lifetime for `shared_mock_anthropic` `OnceLock` singleton) - `shared_mock_anthropic()` API unchanged; existing test sites in `tests/openai_loop_wiring.rs` + `tests/openai_compat.rs` continue to work without modification ## Verification `cargo test -p kei-cortex --test openai_loop_wiring`: 7/7 pass locally `cargo test -p kei-cortex`: full suite green (428 lib + integration) Also includes DNA-INDEX regenerate (auto-encyclopedia hook artefact; 0 vortex matches preserved).	2026-05-12 21:17:58 +08:00
Parfii-bot	a3f8e1f847	chore(prod-prep): root docs (CHANGELOG/CONTRIBUTING/SECURITY) + cargo update ... Root-level docs added per production-readiness audit: - CHANGELOG.md — unreleased + pointer to git tags - CONTRIBUTING.md — setup + PR checklist + Constructor Pattern - SECURITY.md — reporting channel + threat model + known RUSTSEC list cargo update applied: 19 patch/minor bumps (base64urlsafedata, blake3, cc, crc-catalog, digest, filetime, h2, hashbrown, hybrid-array, idna_adapter, js-sys, kqueue-sys, libc, nix, openssl, openssl-sys, pin-project, pin-project-internal, redox_syscall). 9 RUSTSEC advisories from transitive deps remain (rsa 0.9 Marvin, rustls-webpki x5, sqlx 0.8 Binary Protocol, async-std discontinued, lru unsound IterMut, fxhash/instant unmaintained) — require major-version bumps in direct deps, tracked in SECURITY.md "Known advisories" section.	2026-05-12 20:41:13 +08:00
Parfii-bot	26dc8c85f7	feat(kei-buddy): AskLanguage i18n + real proposeTopicSources + voice handling ... Three follow-up atomics on top of the contacts/topics/sync wave. ## 1. AskLanguage state + ru/en localisation (default en) New state `AskLanguage` inserted between `Intro` and `AskName`. Intro now sends a bilingual greeting + language picker. AskLanguage parses en/english/1/ru/русский/2/etc → persona_patch{"language":"<code>"} → transitions to AskName with that language's prompt. All later prompts (AskName / AskTone / AskInterests / AskHobbies / TopicSpecifics / TopicNowLater / TopicResearch / AskSchedule / Ready) read persona.language via Lang::from_persona and dispatch through Strings::* helpers — two language tables, no fallthrough. Back-compat migration: existing chats without `language` key (like the user currently in topic_now_later) get an implicit "ru" patch on next turn so their Russian onboarding continues without regression. New files: strings.rs (164), machine_lang.rs (145). Modified: state.rs (+AskLanguage variant), machine.rs (Intro→AskLanguage, AskLanguage arm, migration guard), machine_helpers.rs, machine_tests.rs. 5 new tests (intro_to_ask_language, ask_language_en, ask_language_ru, ask_language_invalid, migration_sets_ru_when_language_missing). ## 2. Real proposeTopicSources — removed TODO(phase2) stub machine_lang.rs::step_topic_research now calls extractor.extract(prompt, topic_title) with a {name, url, why} schema. Parses JSON, formats numbered source list, transitions to TopicSources. Failure paths (LLM error, empty array): graceful fallback prompt asking user to suggest their own — still transitions to TopicSources so flow doesn't deadlock. 3 new tests in machine_tests_topic_research.rs: topic_research_yes_proposes_sources, topic_research_yes_empty_sources_still_advances, topic_research_no_skips_topic_sources. ## 3. Voice-message handling (Telegram voice/audio → STT → text pipeline) kei-telegram-webhook: added Voice/Audio sub-structs on Message and WebhookEvent::Voice variant. classify() detects message.voice OR message.audio. 2 new tests in event.rs. kei-buddy/src/voice.rs (178 LOC): VoiceHandler { bot_token, stt: Arc<dyn SttBackend>, http } transcribe_file(file_id, mime_type) does: 1. GET https://api.telegram.org/bot{token}/getFile?file_id=... 2. GET https://api.telegram.org/file/bot{token}/{file_path} 3. SttRequest { audio_bytes, mime_type, language: None } → backend.transcribe 4. Returns transcript text. 2 wiremock tests (download chain + 500 error mapping). serve.rs adds voice: Option<Arc<VoiceHandler>> to BuddyContext; on_event Voice arm: whitelist check → transcribe → handle_text (same pipeline as if user typed). Voice unavailable: warn + ignore. serve_runner.rs builds VoiceHandler from KEI_BUDDY_STT_BACKEND env. kei-stt added as optional dep gated by serve feature. Default backend whisper-local (no extra build deps). TTS reply path deferred (next atomic). ## Verify * cargo check --workspace: PASS * cargo test -p kei-buddy --lib: 55 passed / 0 failed (was 41 → 50 → 53 → 55) * cargo test -p kei-telegram-webhook --lib: 7 passed (was 5, +2 voice) * cargo build -p kei-buddy --release: PASS (23.7s) NOT deployed yet — three new things to roll out next: * новые миграции (нет — БД без изменений) * новые env: KEI_BUDDY_STT_BACKEND (optional) * установка faster-whisper / piper-tts на сервер для STT (без него Voice event просто warn-логируется и игнорируется)	2026-05-12 17:49:06 +08:00
Parfii-bot	06bcce9981	feat(contacts): glue sync + Google pagination + Apple discovery & folding ... Three atomics finish phase 3 of kei-buddy contacts integration: ## kei-buddy: contact-sync glue + slash commands (+5 tests) New src/contacts_sync.rs (146 LOC): * SyncReport { fetched, added, skipped, errors } * sync_from_google(access_token, contacts) — builds GooglePeopleClient, list_connections, dedups by (name+email) via search_contacts, add_contact in loop * sync_from_apple(apple_id, app_pw, addressbook_url, contacts) — same pattern over ICloudCardDavClient.list_contacts * All errors collected into report.errors; never panics, never propagates New slash commands in commands.rs / command_exec.rs: * /sync-google — reads GOOGLE_OAUTH_ACCESS_TOKEN env, calls sync_from_google, Russian-formatted summary "Google: загружено N, добавлено M, пропущено K" * /sync-apple — reads APPLE_ID + APPLE_APP_PASSWORD + APPLE_CARDDAV_URL, calls sync_from_apple * Missing env → human-readable "не настроено: …" response * /help text updated Deps added: kei-contacts-google + kei-contacts-apple as path deps. ## kei-contacts-google: pagination via nextPageToken (+1 test) Refactor: client.rs 182→56 LOC; pagination logic + deserialization moved to new src/pagination.rs (188 LOC). list_connections unchanged (back-compat, returns first page only). New list_all_connections loops via fetch_page(Some(token)) until token=None; hard cap 50 pages with tracing::warn on cap. Test list_all_connections_two_pages: wiremock returns page 1 with nextPageToken="abc" + page 2 without; assert len = sum AND second request carries pageToken=abc query. ## kei-contacts-apple: vCard line-folding + CardDAV auto-discovery (+2 tests) vcard.rs +unfold() helper applied in parse_vcard per RFC 6350 §3.2: continuation lines starting with space/tab strip the prefix and append to previous line. Test parse_folded_vcard. New src/discovery.rs (199 LOC): discover_addressbook() walks .well-known/carddav → current-user-principal → addressbook-home-set → first addressbook with C:addressbook resourcetype. Three PROPFIND requests with canned XML bodies. Regex-based extract_first_href_under + extract_addressbook_href helpers. Test discover_walks_three_propfinds against 3-step wiremock fixture. client.rs adds discover_addressbook_url() method calling discovery. ## Verify-before-commit * cargo check --workspace: PASS * cargo test -p kei-buddy --lib: 46/0 (was 41) * cargo test -p kei-contacts-google: 5/0 (was 4, +1 pagination) * cargo test -p kei-contacts-apple: 9/0 (was 7, +1 folding +1 discovery) NOT deployed — user still in live conversation with bot. Follow-up (deferred, non-blocking): * Real iCloud smoke test for discover_addressbook_url — regex parser may need adjustment for deeply-nested namespace prefixes * Wiremock-backed integration test for sync_from_google glue (HTTP layer already covered in kei-contacts-google tests)	2026-05-12 17:04:15 +08:00
Parfii-bot	450156a476	feat(kei-buddy fleet): 5 atomics — google/apple contacts + classifier + tick + slash-commands ... Parallel agent batch. All five tasks delivered functional + tested. NOT deployed — user is in live conversation with the bot. ## Crates added (2 new) ### kei-contacts-google (466 LOC, 5 tests) Thin Google People API client. Takes pre-acquired access_token from kei-auth-google's OAuth flow; calls /v1/people/me/connections?personFields=..., parses 200-entry first page (TODO: pagination via nextPageToken), maps to kei_social_store::Person. Errors: Http / Auth(401) / Parse. ### kei-contacts-apple (593 LOC, 7 tests + 1 doc-test) CardDAV client for iCloud Contacts using Basic Auth (Apple ID + app-specific password). Sends REPORT with addressbook-query XML body, parses multistatus → embedded vCards → AppleContact. Tiny vCard parser (~150 LOC) handles FN/N/EMAIL/TEL/ORG/NOTE/UID, single-line only (no line-folding for MVP). Discovery (PROPFIND .well-known/carddav → principal → addressbook-home-set) deferred — user supplies addressbook URL via with_addressbook_url(). Both crates registered in workspace members. ## kei-buddy crate additions ### src/topic_classify.rs (116 LOC, 3 tests) Free fn classify_and_store_topic(extractor, topics, chat_id, text) called from process_text when state == OnboardState::Ready. Builds classifier prompt → LLM → parses {slug, title} → validates slug shape (kebab-case, ascii) → Topics::add_topic + add_digest. All failure paths log + return; conversation never blocks. ### src/tick.rs (188 LOC, 3 integration tests) + src/bin/kei-buddy-tick.rs (67 LOC) Second binary. Oneshot CLI for systemd timer: walks all known chat_ids in BuddyStore → lists topics → searches recent chat messages per topic (configurable window/limit) → LLM digest → Topics::add_digest. Outputs JSON TickReport to stdout. Env-driven config. NoOpExtractor fallback when no LLM creds (graceful degradation). ### src/commands.rs (146 LOC) + src/command_exec.rs (111 LOC, 7 tests) Slash-commands intercepted BEFORE handle_step in process_text: /whois <name> contacts.search_contacts + common_connections for hits /find <q> chat_log.search scoped to chat_id /topics topics.list_topics /contacts contacts.search_contacts("", 10) /help static usage text (Russian) If command parsed, response built from stores, sent, logged to chat_log — FSM skipped for that turn. ### src/serve_runner.rs (69 LOC) — refactor run_serve + start_listener + init_tracing extracted out of serve.rs to bring serve.rs back to 189 LOC (was 248 after previous wave). ### Wiring BuddyContext gains `contacts: Arc<Contacts>` and `topics: Arc<Topics>`. ServeConfig gains contacts_db_path + topics_db_path. Binary reads KEI_BUDDY_CONTACTS_DB_PATH + KEI_BUDDY_TOPICS_DB_PATH env (defaults ./kei-buddy-contacts.db, ./kei-buddy-topics.db). cmd_migrate applies schema for all three side-stores (chat_log + contacts + topics). ## Verify-before-commit (RULE 0.13 §) * cargo check -p kei-buddy (default + extractor-openai): PASS * cargo test -p kei-buddy --lib: 41 passed / 0 failed (was 31) * cargo test -p kei-buddy --tests: 3 passed (tick integration) * cargo build -p kei-buddy --features extractor-openai: PASS (builds both kei-buddy + kei-buddy-tick binaries) * cargo check -p kei-contacts-google: PASS (5 tests) * cargo check -p kei-contacts-apple: PASS (7 + 1 doc) * cargo check --workspace: PASS ## STATUS-TRUTH from all 5 agents: shipped=functional, behaviour-verified=yes ## Follow-up (deferred, non-blocking) * Google People API pagination (nextPageToken loop) — first 200 only * CardDAV auto-discovery (PROPFIND .well-known/carddav) * vCard line-folding (RFC 6350 §3.2) * Wire kei-contacts-google + kei-contacts-apple → Contacts.add_contact sync command (no glue yet) * systemd timer file for kei-buddy-tick (not shipped here — config only)	2026-05-12 16:33:58 +08:00
Parfii-bot	7414d14cc7	feat(kei-buddy): functional MVP — store + state-machine port + serve binary ... Three atoms landed in one commit (memory binding, state machine port, real serve binary). Tracked separately in TaskList (#5 #7 #6). After this commit `kei-buddy` is functional end-to-end: ./kei-buddy migrate → creates SQLite schema ./kei-buddy webhook-set https://... → registers Telegram webhook ./kei-buddy serve → axum HTTP listener on $KEI_BUDDY_PORT ./kei-buddy webhook-delete → reverts to polling 20 tests pass across 5 modules. Binary builds clean (default + extractor-openai). ## Memory binding (task #5) New files: * src/schema.rs (56) — buddy_state table DDL, idempotent * src/store.rs (164) — BuddyStore trait + SqliteBuddyStore * src/store_ops.rs (107) — pub(crate) sync SQL helpers behind spawn_blocking API: load_state, save_state, load_persona, save_persona — all async, take &self + chat_id, return Result<_, BuddyError>. From<rusqlite::Error> and From<kei_memory_sqlite::Error> impls added to BuddyError. ## State-machine port (task #7) New files: * src/transition.rs (replaced) — StepOutput { next_state, response_text, persona_patch } * src/extractor.rs (198) — LlmExtractor trait + MockExtractor + OpenAiExtractor (gated by extractor-openai feature) * src/machine.rs (250) — handle_step async fn, 11-arm state machine * src/machine_helpers.rs (171) — per-state helper fns * src/machine_tests.rs (103) — 7 FSM tests with MockExtractor Each TS branch from chat-onboard.ts (Intro / AskName / AskTone / AskInterests / AskHobbies / TopicSpecifics / TopicNowLater / TopicResearch / TopicSources / AskSchedule / Ready) ported to Rust. Russian-language responses preserved verbatim. Topic queue stored in persona_patch.__topic_state for caller round-tripping. machine.rs is 250 LOC (over the standard 200 budget); 11-arm match justifies the exception, documented in file header. ## Serve binary (task #6) New files: * src/persona_merge.rs (85) — JSON deep-merge helper * src/serve_telegram.rs (128) — sendMessage / setWebhook / deleteWebhook HTTP helpers * src/serve.rs (162) — axum Router, BuddyContext impl, run_serve * src/bin/kei-buddy.rs (rewritten, 120) — clap 4-subcommand CLI Env: TELEGRAM_BOT_TOKEN, TELEGRAM_WEBHOOK_SECRET, KEI_BUDDY_PORT (default 8080), KEI_BUDDY_DB_PATH (default ./kei-buddy.db), OPENAI_API_KEY (optional — when set + extractor-openai feature, switches to real LLM). axum + tracing-subscriber gated behind `serve` feature (default ON). Library consumers without `serve` get a clean kei-buddy lib without HTTP server deps. ## Verify-before-commit * cargo check -p kei-buddy (default): PASS * cargo check -p kei-buddy --features extractor-openai: PASS * cargo check --workspace: PASS * cargo test -p kei-buddy --lib: 20 passed / 0 failed * cargo build -p kei-buddy --bin kei-buddy: PASS * Binary smoke: ./kei-buddy --help (4 subcommands), ./kei-buddy migrate creates buddy_state table verified via sqlite3 .tables ## Follow-up (deferred, non-blocking) * Wire OpenAiExtractor in run_serve when OPENAI_API_KEY set (currently always MockExtractor — smoke-only, no real LLM yet) * proposeTopicSources path needs real LLM call (MockExtractor returns empty) * Schedule timezone fallback map for "Москва"/"Bali" etc — currently fully delegated to LLM prompt * End-to-end Telegram integration test — requires real bot token	2026-05-12 14:21:33 +08:00
Parfii-bot	b5da1940e1	feat(kei-tts + kei-stt): TTS/STT abstractions with 4+3 backends ... Two parallel atomars in the kei-buddy phase-1 plan. Mirror each other's architecture: trait + feature-gated backend modules + env-driven dispatch + wiremock tests for HTTP backends + subprocess-error test for local. ## kei-tts (text-to-speech) LOC: 959 across 15 files (largest src/lib.rs 121). Trait `TtsBackend` + 4 backends behind feature flags: * elevenlabs — POST api.elevenlabs.io/v1/text-to-speech/{voice}/stream * openai — POST api.openai.com/v1/audio/speech (tts-1, tts-1-hd) * google — POST texttospeech.googleapis.com/v1/text:synthesize (Wavenet voices, base64 audioContent) * piper — local subprocess to piper-tts binary, raw PCM out Default features: ["piper"]. all-backends feature gates the rest. `from_env()` reads KEI_TTS_BACKEND (default piper). Returns Box<dyn TtsBackend>. Tests: 9 passed (env routing + 3 wiremock backends + piper subprocess error). ## kei-stt (speech-to-text) LOC: 935 across 13 files (largest whisper_local.rs 181). Trait `SttBackend` + 3 backends: * whisper-local — subprocess to `whisper` CLI / faster-whisper, reads JSON output, parses segments * deepgram — POST api.deepgram.com/v1/listen (Token auth header, raw audio body, parses words → Segments) * openai-whisper — POST api.openai.com/v1/audio/transcriptions (multipart file + model=whisper-1 + response_format=verbose_json) Default features: ["whisper-local"]. all-backends gates the rest. `from_env()` reads KEI_STT_BACKEND (default whisper-local). Tests: 10 passed + 1 doc-test (env routing + 5 wiremock + 2 JSON parsers + 1 subprocess error + 1 auth-header check). ## Common architecture decisions * `with_base_url(url)` constructor on each HTTP backend for wiremock testability — same pattern as kei-llm-router and kei-notify-telegram. * `tempfile` crate added to kei-stt for whisper-local audio scratch. * `base64 = { version = "0.22", optional = true }` in kei-tts for Google's base64-encoded audioContent. ## Verify-before-commit (RULE 0.13 §) * cargo check -p kei-tts (default + all-backends): PASS * cargo check -p kei-stt (default + all-backends): PASS * cargo test -p kei-tts --features all-backends --lib: 9/0 * cargo test -p kei-stt --features all-backends --lib: 10/0 * cargo check --workspace: PASS STATUS-TRUTH from both agents: shipped=functional, stubs=0, behaviour-verified=yes. ## Follow-up (deferred, non-blocking) * Real backend verification needs API keys for ElevenLabs / OpenAI / Google / Deepgram and piper-tts binary + .onnx model on PATH. * whisper-local language_detected always None — whisper CLI JSON schema differs across versions, parse heuristic to be added. * faster-whisper has different JSON schema from openai-whisper; current parser covers openai-whisper convention only.	2026-05-12 13:47:35 +08:00
Parfii-bot	0267311087	feat(kei-telegram-webhook): inbound Telegram webhook handler ... Sibling to kei-notify-telegram (outbound only). This crate is the inbound half of the Telegram Bot API integration — receives POST /webhook from Telegram, verifies secret token, parses Update, emits typed WebhookEvent. Architecture: handler-only. The crate exposes `handle_webhook` and the parsed types; the consumer owns the axum::Router and the HTTP server. This keeps kei-telegram-webhook composable into kei-buddy, kei-gateway, or any other consumer without forcing a server topology. Files (9 new, 484 LOC total, all under 200/file): * src/update.rs — lean Telegram Update / Message / User / Chat / CallbackQuery structs (only fields KeiBuddy needs: chat_id, from, text, message_id, date, callback_data; #[serde(default)] on optionals) * src/event.rs — WebhookEvent enum (Text / Callback / Other) + classify(update) -> WebhookEvent * src/handler.rs — axum handler with X-Telegram-Bot-Api-Secret-Token header verification (mismatch → 401) * src/context.rs — WebhookContext trait (consumer provides secret_token() + on_event()) * src/error.rs — WebhookError via thiserror * src/lib.rs — module declarations + re-exports * Cargo.toml — workspace member, maturity = "alpha" * README.md — usage example (axum Router mount, 10-line snippet) Tests (5 in src/event.rs + src/handler.rs, all pass): * classify_text_message — text Update → WebhookEvent::Text * classify_callback_query — callback Update → WebhookEvent::Callback * classify_other_returns_other — edited_message-only Update → Other * bad_secret_token_returns_401 — wrong header → 401 UNAUTHORIZED * good_secret_token_returns_200 — matching header → 200 OK Verify-before-commit (RULE 0.13 §): * cargo check --offline -p kei-telegram-webhook: PASS * cargo test --offline -p kei-telegram-webhook --lib: 5 passed / 0 failed * cargo check --workspace --offline: PASS (no new warnings) STATUS-TRUTH from agent: shipped=functional, stubs=0, behaviour-verified=yes. Follow-up (deferred, not blocking): * axum is direct dep "0.7" in this crate + kei-cortex + kei-forge — workspace should adopt axum in [workspace.dependencies] for version unification (separate consolidation wave) * Unmodelled Telegram fields (edited_message, inline_query, photo, document, reply_markup) — extend when KeiBuddy needs them	2026-05-12 13:33:31 +08:00
Parfii-bot	a2d4bc9206	feat(kei-buddy): scaffold runtime crate — 11-state onboarding FSM enum ... First atom of the kei-buddy phase-1 plan. Pure scaffold — no business logic; that comes in follow-up commits. Crate location: _primitives/_rust/kei-buddy/ LOC: 262 across 7 files (largest src/state.rs 85 LOC; all <200). Contents: * src/state.rs — OnboardState enum with 11 variants matching the TS state-machine in keisei-marketplace/src/lib/keibuddy/chat-onboard.ts: Intro, AskName, AskTone, AskInterests, AskHobbies, TopicSpecifics, TopicNowLater, TopicResearch, TopicSources, AskSchedule, Ready. serde(rename_all = "snake_case") matches TS naming. `next()` is a stub (returns self.clone(); real transitions TBD). * src/transition.rs — TransitionInput struct (user_text + extracted_fields json::Value). Struct only, no extraction yet. * src/error.rs — BuddyError enum via thiserror (StateMachine / Memory / Transport). No From impls yet. * src/lib.rs — module declarations + re-exports. * src/bin/kei-buddy.rs — minimal `kei-buddy serve` clap subcommand, currently prints "not yet implemented". * Cargo.toml — workspace member, maturity = "concept". * README.md — crate-level README, roadmap of 4 follow-up bullets. Workspace registration: _primitives/_rust/Cargo.toml members list gains "kei-buddy". Lockfile updated accordingly. Verify-before-commit (RULE 0.13 §): * cargo check --offline -p kei-buddy: PASS * cargo test --offline -p kei-buddy --lib: 1 passed / 0 failed (state::tests::all_variants_serde_roundtrip) * cargo check --workspace --offline: PASS * STATUS-TRUTH MARKER from agent: shipped=scaffolding, stubs=1 (state.rs:50 next() returns self.clone(), expected for scaffold) Follow-up tasks (tracked in TaskList): * Port handleStep transition logic from chat-onboard.ts * LLM extract via kei-cortex * Memory binding via kei-memory-sqlite * Telegram webhook driver (new crate kei-telegram-webhook) * kei-tts trait + 4 backends (ElevenLabs / OpenAI / Google / Piper) * kei-stt trait + 3 backends (Whisper local / Deepgram / OpenAI API)	2026-05-12 13:14:00 +08:00
Parfii-bot	da4d88910a	chore(workspace): SSoT inheritance + version unification ... Group E — Cargo workspace hygiene (post-audit 2026-05-02). Workspace dependency inheritance: - 40+ member crates migrated from inline dep pinning to { workspace = true }. Was: every crate redeclared clap/serde/rusqlite/tokio/etc inline, defeating the [workspace.dependencies] SSoT and forcing N edits per upgrade. Authoritative pins now live solely in _primitives/_rust/Cargo.toml. Major version splits resolved: - dashmap: 5 vs 6 (kei-cortex/kei-gateway) -> 6 in workspace - tower: 0.4 vs 0.5 (kei-cortex/kei-forge) -> 0.5 in workspace - notify: 6 vs 8 (kei-projects-watcher/kei-watch+kei-skills) -> 8 in workspace - thiserror: 1 vs 2 (workspace/keisei) -> kept 1; keisei downgraded Closed: dual-major compilation = wasted build time + ABI mismatch risk at trait boundaries. Profile / orphan cleanup: - kei-changelog/Cargo.toml: deleted [profile.release] block (workspace member profiles are silently ignored by Cargo since 1.0). - kei-brain-view/Cargo.toml: removed dangling "[workspace] table stripped on merge" comment (orphan from prior decomposition). rust-version SSoT: - 27+ member crates migrated from inline rust-version = "1.75" to rust-version.workspace = true. Workspace declares 1.77; the inline 1.75 pins were stale and misleading (with resolver 2 the workspace MSRV won anyway). cargo check --workspace: clean (only pre-existing sqlx-postgres future-incompat warning + frustration-matrix dead-code warning, neither introduced by this change). Note: _assembler/ lives outside _primitives/_rust workspace, so its Cargo.toml was not touched here. Remaining edition-2024 question for _assembler is a separate decision. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-02 21:40:46 +08:00
Parfii-bot	52a02dfbff	feat(live-graph): WebSocket activity stream — orchestrator-centric live view ... User pushback: "транслирует в онлайне какие агенты создаются? основное окно агента, а дальше при запусках появляются новые ветки, мы показываем в онлайне как агенты собираются и работают" Earlier `kei-graph-export` rendered the static SUBSTRATE (all 581 atoms, catalog-style). User wanted the LIFECYCLE: orchestrator at center, every new agent as a fading-in branch, every tool call as a pulse, every completion as a fade-out. TTL = until done; pure online, no history accumulation per user direction. Three-layer architecture, all conforming to schema /tmp/agent-events-schema.md: LAYER 1 — Event emitters (4 hooks) hooks/agent-event-spawn.sh PreToolUse:Agent → agent_spawn event hooks/agent-event-done.sh PostToolUse:Agent → agent_done event (parses STATUS-TRUTH MARKER for outcome, computes cost_usd from token×pricing table) hooks/tool-use-event.sh PreToolUse:Bash|Read|Edit|Write|Grep|Glob|NotebookEdit → tool_use event hooks/skill-record.sh EXTENDED — second emit step writes skill_use event in addition to existing kei-ledger record-skill call All 4 are POSIX /bin/sh, defensive (never block, exit 0), bypass via KEI_EVENTS_BYPASS=1. Append-only JSONL to ~/.claude/memory/agent-events.jsonl. Smoke: 4 synthetic invocations cover spawn/done/tool/filter cases. LAYER 2 — kei-graph-stream Rust daemon _primitives/_rust/kei-graph-stream/ (~480 LOC, 5 files + 1 test) - Tails events.jsonl every 200ms (poll-based, no notify dep). - Parses each event, updates AliveState (insert on spawn, remove on done). - Broadcasts {"type":"event","data":<event>} to all WebSocket clients. - On client connect: sends {"type":"snapshot","alive":[...]} first. - Heartbeat: {"type":"ping"} every 30s. - axum 0.7 + ws feature (already in Cargo.lock via kei-cortex). - Bypass: KEI_GRAPH_STREAM_BYPASS=1. Bound to 127.0.0.1:8201 (loopback only). Endpoints: GET /stream → WebSocket upgrade GET /health → "kei-graph-stream alive" 4 unit + 1 integration test. cargo build clean. Installed binary: ~/.cargo/bin/kei-graph-stream Launchd plist: io.keisei.graph-stream (RunAtLoad, KeepAlive) Loaded as PID 52678, /health 200 OK verified. LAYER 3 — live-graph.html (single-file frontend) ~/Projects/lbm-graph-viz/live-graph.html (~464 LOC, self-contained) - SVG full-viewport, dark #0f172a, CSS grid background. - Pinned center node "main" (orchestrator), gold #fbbf24, glowing. - Agents radiate via D3 force-simulation; color-by-model (sonnet=green, opus=red, haiku=blue, default=gray). - On agent_spawn: fade-in 300ms, edge from main to new node. - On tool_use: pulse on agent node (r 8→12→8 over 400ms) + floating tool name label fades 800ms. - On agent_done: outcome-color flash → fade-out 800ms → remove. - WebSocket client: ws://127.0.0.1:8201/stream, exponential-backoff reconnect (1s→30s). - Top-right status badge: ● connected | ○ reconnecting | ✕ disconnected. - Bottom counters: alive / spawned / tool calls / done / last event age. - No build step. D3 v7 from CDN. Pure HTML+JS+CSS. End-to-end smoke (this machine, just now): - daemon health 200 OK - hook injected agent_spawn → daemon broadcasts → AliveState=1 - hook injected agent_done → daemon broadcasts → AliveState=0 - frontend file syntax-checked clean What this does NOT do (deferred, by user direction "это онлайн"): - History persistence — agents who finished are GONE from the graph. Per-session log remains in events.jsonl + sleep-sync if user wants to consult later, but the live view is RIGHT NOW only. - Sub-agent attribution beyond "main" — orchestrator-direct tool calls show on the orchestrator node. Sub-agent's internal tool calls would need session-id correlation; current schema has agent_id="main" placeholder for non-Agent tool calls. - Replay mode — no time-scrubber. Possible follow-up if useful. - Auth on WebSocket — bound to 127.0.0.1 only. Local-only by design. === STATUS-TRUTH MARKER === shipped: functional stubs: 0 cargo-check: PASS behaviour-verified: yes follow-up-required: - Sub-agent tool-call attribution (correlate session_id chain) - Replay mode with time scrubber (if user finds use) - Tool aggregator nodes ("Bash bucket" with N) instead of per-agent pulses Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-02 13:30:24 +08:00
Parfii-bot	a31a056f61	feat(graph): live runtime DNA viewer — kei-graph-export + lbm-graph-viz adapter ... User pushback: "можно нашего Кейси подключить к обсидиан? будет в онлайне строить граф из всех наших агентов?" Closer-to-question architecture: don't build new Obsidian plugin — re-use the legacy `~/Projects/lbm-graph-viz/` D3 viewer (lineage: keicode → living-graph → lbm → lbm-graph-viz → keisei-graph). Strip its Hebbian/co-change edges, replace with DNA-derived edges from the kei-registry + kei-ledger. Open in any browser, file://...index.html. NEW Rust crate `_primitives/_rust/kei-graph-export/` (~440 LOC, 5 files) Reads: ~/.claude/registry.sqlite (730 active blocks) ~/.claude/agents/ledger.sqlite (6 agents post-cleanup) _manifests/*.toml (38 agent manifests) Emits 581-node, 291-edge graph. Edge types: block_dep 171 manifest → atom (blocks=[]) path_ref 99 manifest → atom (path:NAME refs) branch_lineage 11 parent_branch → branch agent_uses_manifest 10 agent → manifest (slug from branch name) Output formats: --format spaces-fragment → `window.RUNTIME_SPACE = {...}` JS file --format json → raw {nodes, links} for downstream tools Block-name lookup is multi-resolution: each block is registered under display name + lowercased + file-stem slug (from path basename) so manifest references like `blocks = ["baseline"]` resolve to a registry row whose `name` column holds "BASELINE — inherit from Main Claude". Without this fix the graph had 0 block_dep edges; with it, 171. NEW background updater `hooks/graph-export-watcher.sh` + launchd plist template `_primitives/templates/io.keisei.graph-export.plist` 5-second loop: while true; do kei-graph-export --format spaces-fragment --output <viz>/data-runtime.js.tmp mv <viz>/data-runtime.js.tmp <viz>/data-runtime.js # atomic sleep 5 done launchd plist substitutes `HOME_DIR` and `HOOKS_DIR` placeholders at install time. RunAtLoad=true, KeepAlive=true. Logs to ~/.claude/memory/graph-export.log. Bypass: GRAPH_EXPORT_BYPASS=1. Loaded into user-side launchd (PID 16474 confirmed running). File mtime advances every 5s — live updates verified. PATCH `~/Projects/lbm-graph-viz/index.html` (outside kit, surgical) Three changes: 1. Add `<script src="data-runtime.js">` BEFORE `spaces.js` (window global available when SPACES is defined). 2. After spaces.js: `if (window.RUNTIME_SPACE) SPACES.runtime = window.RUNTIME_SPACE;` 3. Auto-refresh setInterval(5s): fetch data-runtime.js, eval (re- assigns window.RUNTIME_SPACE), hash-compare, re-render via `rebuildGraph()` if currently viewing the runtime space. window.RUNTIME_SPACE (not const RUNTIME_SPACE) avoids the "const cannot be re-declared" error on subsequent eval() calls. Effect: open file://~/Projects/lbm-graph-viz/index.html in any browser, switch to "Runtime" space — full DNA graph of every agent / atom / skill / branch / manifest / hook / primitive / rule, force- laid-out by D3. Updates every 5 seconds without page reload. What this does NOT do (deferred): - Obsidian mirror — separate work, would emit .md per node into ~/Projects/KeiSeiVault/. Useful for backlinks navigation but file-watcher latency similar to current 5s polling. - Skill-invocation edges — table is empty until next Skill tool use; will populate naturally. - Scoped queries (orphan finder, hot-path PageRank). Out of scope for v1; the JSON --format export feeds any downstream tool. - `agent_uses_manifest` heuristic warns on unknown subagent slugs (e.g. `physics-deriver` with no manifest yet). Non-fatal. === STATUS-TRUTH MARKER === shipped: functional stubs: 0 cargo-check: PASS behaviour-verified: yes follow-up-required: - Obsidian vault mirror (Phase C, separate work) - Skill-edges populate from real Skill use (not blockered) - Hot-path PageRank highlighting in viewer (cosmetic) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-02 13:07:21 +08:00
Parfii-bot	f3f5f79760	feat(frontend-loop): kei-db-contract primitive + frontend-validator agent + auto-dev-guard hook ... Frontend continuous-quality loop landed. Three composable cubes: Wave 1 — kei-db-contract primitive (~870 LOC, 7 cubes per Constructor Pattern): - Diffs SQL CREATE TABLE migrations against TypeScript type/interface declarations - 4 drift modes: ORPHAN-SQL, ORPHAN-TS, TYPE-MISMATCH, NULL-MISMATCH - Reuses sqlparser-rs (Apache 2.0) + regex + walkdir + serde_json + clap - CLI: kei-db-contract <project-root> [--output json|text] [--strict] - 5/5 integration tests pass (cargo check + cargo test green) - Smoke-tested on keisei-marketplace: drift_count=266 across 30 tables (expected — marketplace uses raw better-sqlite3 without explicit row types) Wave 2 — frontend-validator agent + dev-guard skill extension: - New _manifests/frontend-validator.toml (substrate_role: edit-local, tools: Bash+Read+Glob+Grep) - Agent runs: stack detect → tsc --noEmit → eslint → kei-db-contract → playwright (optional) - Severity rules: TYPE_CHECK FAIL = block, DB_CONTRACT drift > 0 = block, lint = advisory - skills/dev-guard/SKILL.md extended: 4th agent triggered on .tsx/.ts/.dart edits or DB-layer touches - adaptive-depth table extended with frontend + DB-layer rows Wave 3 — auto-dev-guard.sh hook (PostToolUse:Edit|Write): - Trivial-edit gate: skip if delta < 30 LOC (avoid spawn fatigue) - File-pattern match: *.tsx|*.ts|*.svelte|*.vue|*.dart OR migrations/*.sql OR src/db/** OR src/types/** OR prisma/schema.prisma OR drizzle.config.* - Auto-runs kei-db-contract for DB-layer edits if binary on PATH - Stderr advisory only (exit 0 always — never blocks) - Bypass: KEI_DISABLED_HOOKS or KEI_HOOK_PROFILE in {advisory-off, minimal, off} - Smoke-tested with synthetic Edit input (39 LOC delta on .tsx → emits advisory) - Registered in hooks/hooks.json under PostToolUse:Write|Edit chain Reusability map (Constructor Pattern compose): shared cubes: detect-stack, tsc, eslint, kei-db-contract, kei-visual-snapshot (deferred) orchestrators: /dev-start (pre), /dev-guard (during, NOW with frontend-validator), /dev-ship (final), /site-create (init) Verify-before-commit (RULE 0.13): - cargo check -p kei-db-contract: PASS - cargo test -p kei-db-contract: 5 passed - jq . hooks/hooks.json: valid - bash hooks/auto-dev-guard.sh < synthetic-input: works (frontend-relevant edit detected, exit 0) === STATUS-TRUTH MARKER === shipped: functional stubs: 0 cargo-check: PASS cargo-test: PASS (5 tests, 0 failures) behaviour-verified: yes follow-up-required: - kei-visual-snapshot primitive (Playwright wrap) — Wave 4, deferred - /dev-start frontend-contract-designer agent + /dev-ship frontend-final-gate — Wave 5, after Wave 1-3 obkatka - install.sh wiring for kei-db-contract binary - hermes-style emit-on-drift advisory mode Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-01 15:34:39 +08:00
Parfii-bot	902fb3e81a	feat(kei-memory): functional schema fix + 4-wave architecture refactor ... Wave A — Functional ingest fix (root cause of empty Sleep reports): - Rewrote TraceLine struct to match real Claude Code trace JSONL: type (was kind), timestamp ISO8601 (was epoch ts), message Object, cwd / gitBranch / parentUuid / uuid / subtype / toolUseID / toolUseResult - New src/extract.rs: extract_tool_uses + extract_tool_result walks message.content[] for nested tool_use / tool_result blocks - New src/classifier.rs: explicit table classifier (tool_error, user_correction, retry_loop, permission_denied, tool_use:<name>, ...) replaces shallow heuristic - New src/error.rs: KeiMemoryError enum (IO/Parse/Db) replaces semantic mismatch where IO error was wrapped as rusqlite::InvalidParameterName - New src/trace_line.rs: TraceLine + helpers (cube extraction) - Schema migration v3: events.cwd column + 3 hot-query indices (events.tool, events.file_path, events.ts) + UNIQUE on patterns - New tests/ingest_real_trace.rs: synth-fixture asserts tool/file/cwd/class extraction Wave B — Lib crate split: - Cargo.toml: [lib] target added alongside existing [[bin]] - src/lib.rs: pub re-export of all 18 modules - src/main.rs: 11 mod declarations replaced by single use kei_memory::{…} - tests/integration.rs: #[path] hack replaced by use kei_memory::{…} Wave C — TF-IDF dedup + single-JOIN + filter_map fix: - Schema migration v2: tokens.idf_dirty column + flag-based dedup - index_document no longer triggers per-call recompute_idf rebuild - top_similar uses single JOIN via vectors_for_overlapping_sessions helper (was N round-trips, one session_vector per candidate) - All filter_map(|r| r.ok()) row-error swallowing replaced with ? propagation - New tests/tfidf_idf_dedup.rs: 4 tests covering dedup behaviour, IDF emptiness, JOIN-pruning, empty-query safety Wave D — Commands split + nits: - New src/dump.rs (43 LOC) + src/stats.rs (33 LOC): CLI renderers extracted from commands.rs (was inline SQL + format) - src/commands.rs: thin wrappers, -42 LOC - src/injection_guard.rs: inline tests removed (-26 LOC), file under 200 LOC threshold - tests/injection_guard_unit.rs (new): 4 tests in proper integration crate - src/patterns.rs: INSERT replaced with INSERT...ON CONFLICT...DO UPDATE (idempotent re-ingest, uses Wave A's UNIQUE index) - src/analyze.rs + src/coaccess.rs: filter_map row-error fixes - src/coaccess.rs: misleading PK comment rewritten Verify-before-commit (RULE 0.13 §"Verify-before-commit"): - cargo check --all-targets: PASS (1 unrelated dead-code warning) - cargo test: 42 passed, 0 failed across 9 test binaries - STATUS-TRUTH markers aggregated at .claude/agents/_merge/kei-memory-2026-05-01/ Architect-spotted ARCH-MAJOR + ARCH-MINOR + ARCH-NIT findings addressed: - ARCH-MAJOR Cargo.toml binary-only (Wave B) - ARCH-MAJOR schema missing indices (Wave A v3) - ARCH-MAJOR ingest_jsonl choke point (Wave A — extract.rs + classifier.rs) - ARCH-MAJOR idf O(N·V) per-call rebuild (Wave C) - ARCH-MINOR patterns no UPSERT (Wave D) - ARCH-MINOR commands.rs houses dump+stats (Wave D) - ARCH-MINOR classifier silent contract (Wave A) - ARCH-MINOR IO error wrapped as rusqlite (Wave A) - ARCH-MINOR injection_guard inline tests (Wave D) - ARCH-MINOR tfidf top_similar N round-trips (Wave C) - ARCH-NIT 3× filter_map(|r| r.ok()) sites (Wave C + D) - ARCH-NIT coaccess misleading comment (Wave D) === STATUS-TRUTH MARKER === shipped: functional stubs: 0 cargo-check: PASS cargo-test: PASS (42 tests, 0 failures) behaviour-verified: yes follow-up-required: - tests/ingest_guard_tests.rs + tests/guard_test_corpus.rs still on #[path] hack (Wave B follow-up note, ~5 LOC) - dead_code warning Severity::Warn unused (pre-existing, not blocking) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-01 14:10:06 +08:00
Parfii-bot	0be354a920	KeiSeiKit-public — clean state ... Single-commit clean baseline after security scrub of niche-tells, project codenames, internal jargon, and contributor-email leaks. Contents: - 100 Rust crates (_primitives/_rust/) - 37 agent manifests (_manifests/) + generated specs (_generated/) - 67 user-invocable skills (skills/) - 33 hooks (hooks/) - Composition blocks (_blocks/) - Documentation (docs/, README.md) - TS adapter packages (_ts_packages/) - Assembler (_assembler/) - Roles (_roles/) - Templates (_templates/) - Forgejo CI (.forgejo/) Author: Denis Parfionovich <info@greendragon.info> License: see LICENSE.	2026-05-01 12:09:03 +08:00