16 commits

Author	SHA1	Message	Date
denis	305787fae3	fix(install): make fresh install complete + ship tamagotchi (#1)	2026-05-20 18:50:09 +00:00
Denis Parfionovich	fc0758d2bb	chore: версия 0.38.0 единая + warning-fixes + mold для release-job ... 1. Версии npm-пакетов приведены к 0.38.0 (был зоопарк 0.14.0/0.14.6): _ts_packages/{,packages/{gmail,grok,mcp-server,recall,telegram,youtube}-adapter} 2. Rust warnings (cargo check workspace): - kei-cortex: deprecated validate_path → validate_path_lexical, удалён orphan-wrapper в read.rs, struct Input → pub(crate) - frustration-matrix: #[allow(dead_code)] на confusion_* поля EvalReport + train_from_dir (будущий CLI) 3. CI release.yml job 'release' падал на Build kei-changelog: clang invalid linker '-fuse-ld=mold' — в .cargo/config.toml жёстко прописан mold для linux. Добавлен Install mold шаг (как уже сделано в build-release matrix).	2026-05-18 13:41:37 +08:00
Denis Parfionovich	5f6b4f2620	fix(ci): regenerate bun.lock — sync с package.json для CI release ... CI v0.38.0 mcp-server билды все 5 упали на `bun install --frozen-lockfile` с «lockfile had changes, but lockfile is frozen». В lockfile отставали: - @keisei/mcp-server 0.14.0 → 0.14.6 - ajv 8.18.0 → 8.20.0 - express-rate-limit 8.3.2 → 8.4.1 - hono 4.12.14 → 4.12.16 Пересоздан `rm bun.lock && bun install` под bun 1.3.14 (тот же что в CI).	2026-05-18 13:01:36 +08:00
Parfii-bot	35136a9840	feat(npm-publish): keigit as primary registry, npmjs reserved for future ... - _ts_packages/tsconfig.base.json: sourceMap=false, declarationMap=false (source maps leaked absolute dev paths in published tarballs). - All 6 @keisei/* packages: publishConfig.registry = keigit.com. mcp-server bumped 0.14.5 -> 0.14.6 (republished without maps). - .github/workflows/release.yml split into two jobs: npm-publish-keigit: primary. Activates on KEIGIT_NPM_TOKEN + KEIGIT_NPM_USER secrets. Publishes via direct curl PUT (Forgejo requires Basic auth; npm CLI sends Bearer). npm-publish-npmjs: reserved for future. Activates on NPM_TOKEN secret. Currently no token -> job skipped gracefully. End-to-end verified: clean dir + scope @keisei -> keigit + npm install pulls 145 deps, no leaked paths, no .map files in any of 6 packages.	2026-05-17 00:18:44 +08:00
Parfii-bot	0c3584d9ee	diag(release): v0.14.5 — keigit auth diagnostic step before publish ... v0.14.4 failed with same 401 despite local-probe showing path-scoped + Basic-auth fallback work. Adding a diagnostic step BEFORE publish: - npm whoami against keigit - curl Bearer probe (read endpoint /api/v1/user) - curl PUT probe (publish endpoint with empty body) - npm config dump (registry resolution) Will reveal: - Whether token actually authenticates from runner network - Whether npm correctly resolves @keisei:registry to keigit URL - Whether something in CI environment is rewriting/blocking the auth header Bump 0.14.4 → 0.14.5 to trigger fresh release run. [FROM-JOURNAL: this session — local probe confirms .npmrc form works, CI rejects with 401, narrowing to runner-environment issue] Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-04 01:03:39 +08:00
Parfii-bot	8a885a7d76	fix(release+slices): v0.14.4 publish auth fallback + 4 fix-implementer slices ... After v0.14.3 npm-publish failed again with 401 Unauthorized despite path-scoped _authToken. Direct curl probe to keigit confirmed BOTH Bearer and Basic auth schemes work — so the issue is npm 10 not sending the auth header in CI. Likely cause: deprecated `always-auth=true` interfered with token resolution. == Publish auth fix == - Drop `always-auth=true` (deprecated in npm 10+; warns in logs) - Keep path-scoped `_authToken` (npm 10 canonical) - Add legacy Basic-auth fallback rows (username/_password/email) — Forgejo accepts both schemes per direct probe; if one resolution path fails, npm tries the other - chmod 600 on $HOME/.npmrc and project .npmrc (defense-in-depth) - Bump 0.14.3 → 0.14.4 == Slice A — TS server hardening (Sonnet code-implementer-typescript) == File: _ts_packages/packages/mcp-server/src/server.ts (+3/-1) File: _ts_packages/packages/mcp-server/src/index.ts (+14/-4) - safeEqual constant-time path on length mismatch (timing oracle close) - HTTP server defaults to 127.0.0.1 bind; --bind <addr> opt-in for 0.0.0.0 - Body cap 1 MiB with 413 response (DoS prevention) - VERIFIED: tsc -b --noEmit exit 0 == Slice B — Outcome-only profile hardening (Sonnet code-implementer) == Files: install.sh, install/lib-args.sh, install/lib-profile-outcome-only.sh - Confirm-screen gate before destructive install (skips on --dry-run / --yes) - _outcome_install_ledger return value tracked → summary reflects reality (was: false-success "ledger: ..." when init failed) - --dry-run silent-ignored on non-outcome profiles → now warns - VERIFIED: end-to-end smoke against fake $HOME with `<<< "y"` — all 5 files installed, schema v9 + 2 triggers, summary correct == Slice D — jq-merge dedup tuple (Sonnet code-implementer) == File: install/lib-hooks.sh - Replaced `unique_by(.command)` with reduce-into-object keyed on norm-ed command (tilde-vs-absolute path collision fix) - Snippet-wins precedence on collision - 3 manual scenario traces pass: tilde+tilde, absolute+tilde, idempotency == Slice E — Doc honesty pass (Sonnet code-implementer, selective-merged) == Files: README.md, docs/{INSTALL,ARCHITECTURE,PROFILE-OUTCOME-ONLY}.md Note: Slice E worktree was based on an older main commit; merged selectively to preserve current-main values (565 DNAs, not worktree's 518) - README:62 plugin marketplace URL: KeiSei84/KeiSeiKit → KeiSei84/KeiSeiKit-1.0 (consistent with line 66 git clone URL + Cargo.toml repository field) - README:9-15: per-claim [REAL: <command>] markers on all 8 numerics - README:124-132 + PROFILE-OUTCOME-ONLY.md:43-55 + ARCHITECTURE.md:288-302: rephrase 100-row router claim — now describes Wilson lower-bound (δ=0.10, q*=0.70) continuous metric with file:line pointer to select.rs - INSTALL.md: ESTIMATE-HTC marker covering all install-time / disk-size numerics in profile table (RULE 0.18 compliance) - PROFILE-OUTCOME-ONLY.md privacy section: discloses agent-toolstats.jsonl sidecar (was undocumented per W3 finding) - PROFILE-OUTCOME-ONLY.md uninstall: added 6th rm -f for .bak-* cleanup (closes orphan-accumulation per W3+W4 audits) [FROM-JOURNAL: tasks.jsonl this session — 12 audit agents waves 5+6 + 4 parallel fix-implementer worktrees ran ~25 min wall-time] Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-04 00:16:48 +08:00
Parfii-bot	ca99f78f66	fix(release): path-scoped npmrc + hard-fail publish (v0.14.3 retry) ... v0.14.2 publish run reported "success" but @keisei/mcp-server NEVER landed on keigit because: 1. Host-scoped `.npmrc` token (`//keigit.com/:_authToken=...`) was silently ignored by npm 10 — every publish errored with ENEEDAUTH. 2. The publish loop's `|| echo ":⚠️:"` swallowed the failure so the job exited 0 (W1+W3 finding F3). Two fixes in one commit: A) Path-scoped npmrc per Forgejo docs: `//keigit.com/api/packages/keisei/npm/:_authToken=${KEIGIT_TOKEN}` + `always-auth=true` for scoped registry. Also tee'd to $HOME/.npmrc so the publish loop's `cd packages/<pkg>` cwd doesn't lose the auth line. [VERIFIED: curl PUT with Bearer to /api/packages/keisei/npm/ returns 400 "package is invalid" (auth ACCEPTED, payload bad) — auth format is correct] B) Hard-fail publish loop for packages with publishConfig: - Iterate all packages - For each: read .publishConfig presence - If publish errors AND has publishConfig → record gated_failed=1 - If publish errors AND no publishConfig → notice "skipped" (adapter without registry pin reached npm.org default, expected fail) - End of loop: exit 1 if any gated_failed - Adapters without publishConfig (gmail/grok/recall/telegram/youtube) correctly skip; only @keisei/mcp-server is gated, and a real failure now blocks the job. Bump 0.14.2 → 0.14.3 (0.14.2 tag exists with previous failed publish). Verification done locally: - PAT owner Parfionovich is member of org keisei [REAL: api/v1/user + api/v1/users/Parfionovich/orgs] - Bearer auth to keigit npm registry works [REAL: curl probe → 400 "package invalid", not 401 "unauthorized"] - Cargo workspace clean [REAL: cargo check exit 0] After tag v0.14.3: - npm-publish job creates .npmrc with path-scoped auth - Publishes @keisei/mcp-server@0.14.3 to https://keigit.com/api/packages/keisei/npm/ - Adapters skip cleanly (no publishConfig, no NPM_TOKEN) - Job exits 0 only if mcp-server actually landed Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-03 23:48:07 +08:00
Parfii-bot	cbed9e2275	fix(release): decouple npm-publish + drop x86_64-darwin (v0.14.2 retry) ... v0.14.1 tag triggered Release workflow but npm-publish was SKIPPED because Rust matrix entry x86_64-apple-darwin failed and release job needs:[build-release, build-mcp-binary]; npm-publish needs:release. Single Rust target failure → entire publish chain blocks. This was the W3 Opus CI/build finding deferred from audit-batch-2. Two fixes: 1. **Drop x86_64-apple-darwin from build-release matrix.** GitHub's `macos-latest` runner is now Apple Silicon (M1+); cross-compile to x86_64 needs an OpenSSL sysroot that the arm64 image doesn't ship. `openssl-sys 0.9.114` build fails with "Could not find openssl via pkg-config: pkg-config has not been configured to support cross-compilation". Apple Silicon mandatory for new Macs since 2020; x86 Mac is legacy. If a future user needs x86 darwin, re-add with `experimental: true` and `openssl-sys` features=["vendored"]. 2. **Decouple `npm-publish` from `release`.** The npm package builds its own `dist/` from `_ts_packages/` — it does NOT consume Rust release tarballs. Previously `needs: release` meant a single Rust matrix failure blocked the npm publish even though the two are architecturally independent. Now `needs: []` (parallel with build-release matrix). KEIGIT_TOKEN-presence guard still gracefully skips when secret is absent. Bump version 0.14.1 → 0.14.2 (v0.14.1 tag already exists from prior run). After re-tag v0.14.2: - build-release matrix: 3 targets (was 4) — should all succeed - build-mcp-binary: 5 platforms (unchanged) — already passed in 0.14.1 run - release job: produces GitHub Release with 3 Rust tarballs + 5 MCP binaries - npm-publish job: runs in PARALLEL, publishes @keisei/mcp-server@0.14.2 to keigit regardless of Rust matrix status [FROM-JOURNAL: tasks.jsonl this session — v0.14.1 release run 25280711426 ran 14m wall, 8/9 jobs success, x86_64-darwin failed at openssl-sys build, release+npm-publish skipped via needs-chain] Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-03 22:30:50 +08:00
Parfii-bot	da819a0d92	chore(mcp-server): bump 0.14.0 → 0.14.1 for first keigit publish ... Pre-tag bump. publishConfig.registry already pinned to https://keigit.com/api/packages/keisei/npm/. KEIGIT_TOKEN secret configured on github KeiSei84/KeiSeiKit-1.0 repo. keigit org `keisei` (id=5) created and verified live. Verification: - `npm run build --workspace=@keisei/mcp-server` exits 0 [REAL: ran in this session] - dist/index.js produced (4125 bytes) - Token works: `GET /api/v1/user` with PAT → 200 - Registry empty: `GET /api/packages/keisei/npm/` → 404 (expected) After tag v0.14.1 pushes, the release workflow's npm-publish job runs `npm publish --access public` which routes via publishConfig to keigit. Expected: package lands at https://keigit.com/keisei/-/packages/npm/@keisei%2Fmcp-server Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-03 21:33:41 +08:00
Parfii-bot	784dfbae6f	fix(audit-batch-2): regressions from prev batch + 2nd-wave audit findings ... 12-agent audit (waves 3+4 Opus+Sonnet) on commit 3759fb0 found that 2 of my prior fixes had regressions, plus the prev batch missed 8 stale-text sites and 2 latent bugs. This batch closes them all. == Regressions in audit-batch (3759fb0) — now fixed == 1. PRAGMA user_version=9 placement — could silently downgrade schema on cross-version install (existing v10 DB → re-run reset to 9 → migrations replay → ALTER TABLE duplicate-column errors) - install/sql/outcome-only-schema.sql: PRAGMA moved OUTSIDE the transaction (after COMMIT) for portability across SQLite versions - install/lib-profile-outcome-only.sh::_outcome_install_ledger: added downgrade guard — reads existing user_version BEFORE running ANY init path; if >9, skips entirely (preserves newer schema) - VERIFIED: simulated v10 DB → re-run prints "skipping init to preserve newer schema"; user_version stays at 10 (was downgraded to 9 in the prior batch) [REAL: ran in this session] 2. backup_file mv→cp workaround left orphan backups + bypassed rollback contract (BACKUP_PAIRS not registered) - install/lib-profile-outcome-only.sh: now manually appends to BACKUP_PAIRS so rollback trap restores on later failure; removes the .bak on success path - Comment updated to explain the workaround vs backup_file mv 3. CLAUDE.md skip-guard "STATUS-TRUTH MARKER" was too broad — false-positive on existing kit users (RULE 0.16 doc text matches) - lib-profile-outcome-only.sh: changed grep to literal HTML comment marker `<!-- outcome-only profile (KeiSeiKit) -->` (specific marker written by the installer itself) == Tier 1 missed in prev batch — now fixed == 4. _ts_packages/package-lock.json referenced packages/cortex-ui which does NOT exist on disk → npm ci would fail with ELSPROBLEMS in CI - Regenerated via fresh `rm package-lock.json && npm install` - npm ci now exits 0 cleanly [REAL: ran in this session] - Lockfile shrunk 2403→0 lines on the cortex-ui section (full regen) 5. v3 triggers (branch length cap ≤256) were MISSING from outcome-only-schema.sql — sqlite3 fallback path skipped a schema feature that the Rust kei-ledger flow enforces, creating cross-flow drift - Added trg_agents_branch_len_ins + trg_agents_branch_len_upd mirroring migrations_list.rs:30-44 - Header comment in outcome-only-schema.sql rewritten to match current behavior (was stale) - VERIFIED: end-to-end install creates 2 triggers [REAL: sqlite3 .schema | grep trg_agents_branch_len returns 2] 6. README.md:232 said "102 crates" while README.md:9 said "105 crates" — internal contradiction in same doc - README:232 → "105 workspace crates" 7. ARCHITECTURE.md:165 "53 Rust crates + 13 shell primitives" stale - Updated to "105 Rust workspace crates (47 declared in MANIFEST.toml `full` profile) + 14 shell primitives" 8. ARCHITECTURE.md:157 "45 /commands" stale - Updated to 68 9. plugin.json + marketplace.json description strings still had pre-fix counts (23 primitives / 39 skills / 9 hooks / 12 agents) - Both rewritten to match README:9 SSoT (38 agents / 68 skills / 38 hooks / 105 workspace crates / 47 installable + 14 shell) 10. PROFILE-OUTCOME-ONLY.md:28-29 "What does NOT get installed" still cited 102/67/37/82 - Updated to 105/68/38/85 11. encyclopedia/substrate-overview.md §6/§11/§12 still said "80-char DNA"; §13 said "495 DNA indices"; §6 said "11 install profiles (.../Cursor/Continue/etc)" - All 4 sites fixed to current language (≥33-char variable, 565 DNAs, 12 install profiles) 12. docs/DNA-INDEX.md:1352 said wire format is "(80 chars)" - Updated to "(≥33 chars; role + caps slugs are variable — see docs/DNA-FORMAT.md)" == Tier 2 honesty fixes == 13. Wagner et al. 2004 citation in SLEEP-LAYER.md:26 lacked [VERIFIED] marker (W3 doc consistency caught it) - Added [VERIFIED: doi:10.1038/nature02223] + clarification that the original study did not isolate a specific sleep stage; SWS attribution comes from secondary literature (Diekelmann/Born) 14. PHILOSOPHY.md:125 attributed "overnight consolidation of un-finished intentions" to Wagner 2004 — that paper is about insight gain on the Number Reduction Task, not Zeigarnik-effect cued memory - Rewritten to accurately describe Wagner 2004's actual finding + [VERIFIED: doi:10.1038/nature02223] Verification: - `npm ci` in _ts_packages/ exits 0 [REAL: ran in this session] - `cargo check --workspace` exits 0 in _primitives/_rust [REAL: ran in this session] - Outcome-only end-to-end fresh install produces user_version=9 + 2 triggers (correct schema shape) - Outcome-only re-run against v10 DB preserves user_version=10 (downgrade guard works) - CLAUDE.md skip-guard now triggers ONLY on literal marker, not on RULE 0.16 phrase NOT addressed in this batch (deferred to a future round): - github KeiSei84/{KeiSeiKit, KeiSeiKit-1.0} 404 (user-side action: publish repo or update refs) - keigit user `keisei` does not exist (user-side: create org or rename scope) - KEIGIT_TOKEN secret not configured (user-side action) - Forgejo registration disabled (admin-side) - safeEqual timing leak in TS server (LOW per W3 reassessment) - HTTP bind 0.0.0.0 default (MEDIUM) - Unbounded request body (MEDIUM) - Outcome-only confirm-screen bypass (RULE 0.1 spirit) - Ledger fallthrough false summary - Node 20 deprecation (deadline 2026-06-02, 30 days) - Hook count triple-discrepancy (38 README / 53 DNA-INDEX / 35 maturity-row) - 100-row router claim still in README:117 + PROFILE-OUTCOME-ONLY.md - INSTALL.md numerics without [REAL:] markers - Stale .bak files accumulation policy (cosmetic) - README per-claim [REAL: ] markers for 6 of 7 numerics Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-03 20:30:51 +08:00
Parfii-bot	94a7d682c4	feat(mcp-server): production publish path via keigit.com (Forgejo npm) ... Wire @keisei/mcp-server publish to the author-operated keigit.com Forgejo npm registry. Verified live: keigit.com → 45.77.41.204 (Vultr, public DNS), Caddy → Forgejo 9.0.3, TLS valid, /api/v1/version=200. Why keigit, not GitHub Packages or npm.org: - keigit IS the canonical npm registry for the @keisei scope (operator runs it; no separate vendor account needed) - npm scope @keisei stays @keisei (no rename to match a github org) - Public DNS resolves from any client; auth via per-user PAT - One auth surface for both the git remote and the npm registry Files changed (7): - _ts_packages/packages/mcp-server/package.json · removed `private: true` (was blocking ALL publish, including ours) · added publishConfig.registry = https://keigit.com/api/packages/keisei/npm/ so accidental `npm publish` cannot route to npm.org · added repository field (provenance link to KeiSeiKit-1.0) · added license: Apache-2.0 - README.md (2 hunks): maturity row + install section say "published to keigit.com", show ~/.npmrc setup - PLUGIN.md (3 hunks): same updates referencing keigit - .claude-plugin/mcp-template.json: _comment updated - docs/encyclopedia/substrate-overview.md (1 hunk): MCP row says "alpha" not "stable" + clarifies registry+scope - .github/workflows/release.yml: npm-publish job rewired: · KEIGIT_TOKEN secret instead of NPM_TOKEN as gate · Two-row .npmrc temp-write: @keisei → keigit.com (always when KEIGIT_TOKEN set), npm.org auth as optional fallback · .npmrc cleanup via `if: always()` step - .gitignore: _ts_packages/.npmrc + .npmrc excluded (RULE 0.8) Verification: - node -e 'require("./.../package.json")' parses clean, publishConfig pinned to keigit, private:false [REAL: ran in session] - `npm run build --workspace=@keisei/mcp-server` → tsc -b exit 0, dist/index.js produced [REAL: built in session] - Server starts: `node dist/index.js` lives >1s, doesn't throw, reports expected `[adapters] not installed` for un-built siblings - keigit.com reachable from this machine: HTTP 200 root + Forgejo 9.0.3 version endpoint [REAL: curl ran in session] Required user-side setup before first publish: 1. Create user/org `keisei` on keigit.com (web UI; currently /keisei → 404) 2. Generate a keigit PAT with write:package scope 3. Add as github repo secret KEIGIT_TOKEN 4. Push tag v0.14.1+ → release workflow's npm-publish job picks it up History note: - Earlier in this session a github-packages-scope-rename variant (commit a6f1c72) was pushed; reverted by 542a0a8 because keigit is the right registry. Current commit lands the keigit wiring on top of the revert. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-03 18:11:24 +08:00
Parfii-bot	542a0a816e	Revert "feat(mcp-server): production-ready publish path via GitHub Packages" ... This reverts commit a6f1c72472.	2026-05-03 18:04:00 +08:00
Parfii-bot	a6f1c72472	feat(mcp-server): production-ready publish path via GitHub Packages ... Renamed @keisei/mcp-server → @keisei84/mcp-server (scope must match github org KeiSei84 for GitHub Packages publish). Replaced private:true with publishConfig pinned to npm.pkg.github.com so an accidental `npm publish` cannot leak to npm.org. CI npm-publish job rewired to GitHub Packages auth (GITHUB_TOKEN with packages:write permission). Why GitHub Packages, not npm.org: - Authentication piggybacks on existing github org / PAT — no separate account or NPM_TOKEN required for the core kit - Scope @keisei84 maps 1:1 to org KeiSei84 (npm rule for github) - Doesn't require public DNS for our private Forgejo (Tailscale-only 100.91.246.53 cannot be the publish target — IP-leak in public ref) - Published artefacts live under github.com/orgs/KeiSei84/packages, same access surface as the source repo Why not @keisei (un-scoped or different scope): - npm scope @keisei IS reachable on npm.org but we don't own it there (would require email-verified npm account claim + ongoing maintenance) - @keisei84 requires zero new accounts; works the moment KeiSei84 org has packages enabled (github default) Files changed (11): - _ts_packages/packages/mcp-server/package.json — rename + publishConfig + repository field (required by GitHub Packages); removed private:true - _ts_packages/package-lock.json — regenerated via `npm install` (workspace recognises @keisei84/mcp-server symlink) - README.md (2 hunks) — maturity row says "alpha" not "alpha (unpublished)"; install section documents `~/.npmrc` setup for `@keisei84:registry=https://npm.pkg.github.com/` - PLUGIN.md (3 hunks) — same `~/.npmrc` setup; .mcp.json references @keisei84/mcp-server; "not yet on npm" replaced with "lives on GitHub Packages, not npm.org" - .claude-plugin/mcp-template.json — args use @keisei84 scope - _ts_packages/README.md (4 hunks) — package layout + npx examples - docs/INSTALL.md, install/lib-rust.sh — comment refs - docs/encyclopedia/substrate-overview.md (2 hunks) — package table + publishing notes (was "published to keigit.com npm" — wrong; keigit is a separate community-publish path for user-contributed packages, not the destination for core @keisei84 packages) - .github/workflows/release.yml — npm-publish job rebuilt: · permissions: packages:write · Two-scope .npmrc temp-write: @keisei84 → npm.pkg.github.com (always), @keisei → npm.org (only if NPM_TOKEN secret set, else skipped per pkg) · NODE_AUTH_TOKEN sourced from GITHUB_TOKEN · .npmrc cleaned up via `if: always()` step - .gitignore — _ts_packages/.npmrc + .npmrc excluded (RULE 0.8: auth tokens never in git; CI temp-creates per-job) Verification: - `npm install` clean against new scope: node_modules/@keisei84/mcp-server symlinks to packages/mcp-server, other adapters untouched in node_modules/@keisei/* [REAL: install ran 2026-05-03 in this session] - `npm run build --workspace=@keisei84/mcp-server` produces dist/index.js [REAL: tsc -b exit 0] - Server starts cleanly: `node dist/index.js` runs >1s, emits expected "[adapters] not installed" warnings for un-built sibling adapters, doesn't throw - 17 references to old @keisei/mcp-server scope migrated; 0 left [REAL: grep -rn "@keisei/mcp-server" returns 0 lines] Bad-commit-hygiene note: - Two earlier local commits (cb8dc2a + revert 474fe1c) attempted a keigit.com-pinned variant; soft-reset past them so this commit lands on top of public 2bb2f10. Bad commits never reached remote. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-03 17:50:59 +08:00
Parfii-bot	d2068cded7	docs: reviewer-response — honesty pass + portable format specs ... External reviewer raised 7 overclaim/scope concerns. Agents verified each against source; this commit applies all fixes that landed in docs. Honesty pass: - README:25-29 — Cortex daemon track listed as alpha (was beta); MCP server marked "alpha (unpublished) — install via local dist build"; Phase B noted "auto-codification not yet wired (manual via /escalate-recurrence)"; keigit framed as author-operated mirror (KeiSei84 / private Forgejo), not neutral community service - README:95-97 — Cortex CLI/daemon track downgraded beta→alpha with rationale (browser-app + VSCode-extension are concept-level) - docs/ARCHITECTURE.md — added "Model router — current state (2026-05-03)" subsection: per-call fixed estimate routing, NO 100-row Bayesian threshold in current source (select.rs:74-124); reviewer suggestion deferred - docs/SLEEP-LAYER.md — added Phase B scope clarification: morning report is read-only markdown, no auto-codification path - docs/PUBLISHING.md — aligned framing with README:43 ("author-operated mirror" not "community registry"); added vendor-neutrality note that substrate works against any npm-compatible registry - mcp-server/package.json — added "private": true and description note to prevent accidental publish before maturity gate Portable format specs (reviewer asked for memory-repo agnosticism): - docs/MEMORY-FORMAT.md (196 LOC) — JSONL schemas for traces / decisions / agent-events with jq/awk/pandas recipes, grounded in actual writers - docs/DNA-FORMAT.md (159 LOC) — DNA wire format ("type::caps::sha8") with shell+python parsers - docs/LEDGER-SCHEMA.md (199 LOC) — full SQLite DDL (agents + skill_invocations + indexes + triggers) with sample queries Auto-regen artifact: - docs/DNA-INDEX.md — kei-registry regenerated count 564→565 Verification: - All claims traced to file:line in source by agent a52b29ae - All new docs ≤200 LOC per Constructor Pattern - Reality verification verdicts: README/MCP/Phase-B/Cortex VERIFIED; Bayesian-router PARTIAL (overclaim removed); keigit PARTIAL (framing fixed in this commit); memory-format VERIFIED-FALSE (spec added) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-03 16:59:25 +08:00
Parfii-bot	7cc544fd85	chore: author email + Cargo metadata SSoT (parfionovich@keilab.io) ... Two related changes: 1. Author email update across the kit - All `info@greendragon.info` references replaced with `parfionovich@keilab.io` - Touched: NOTICE, README.md, _ts_packages/package.json (and 5 adapter packages), plus 90+ Cargo.toml files - Apache-2.0 attribution unchanged (Denis Parfionovich, 2026) 2. Cargo workspace.package SSoT for author/license/repository/homepage - Added to [workspace.package]: authors = ["Denis Parfionovich <parfionovich@keilab.io>"] license = "Apache-2.0" repository = "https://github.com/KeiSei84/KeiSeiKit-1.0" homepage = "https://github.com/KeiSei84/KeiSeiKit-1.0" - All ~89 member crates migrated from inline declarations to: authors.workspace = true license.workspace = true (repository/homepage where applicable) - Closes audit gap: kei-graph-stream, kei-cortex, kei-shared previously had no license field at the crate level, blocking `cargo publish` on those. Now they inherit Apache-2.0 from workspace. - kei-scheduler/Cargo.toml: removed stray duplicate `authors` line introduced by an earlier migration sweep. cargo check --workspace: clean. No code changes; metadata-only migration. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-03 13:55:28 +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