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

2.3 KiB

Raw Permalink Blame History

Phase 3 — Run setup script, hand off deploy key

Run the imperative helper and hand the public-key material to the user.

3a — Invoke `kei-sleep-setup.sh`

Run the primitive non-interactively with REPO_URL pre-supplied:

KEI_MEMORY_REPO_URL="<REPO_URL>" \
  ~/.claude/agents/_primitives/kei-sleep-setup.sh

Capture stdout + stderr. The script:

Generates ~/.ssh/keisei-memory-sync if missing.
Prints the .pub contents and fingerprint.
Scaffolds ~/.claude/memory/sync-repo/ and writes config + env refs.
Tests SSH auth against the host (advisory).

If the script exits non-zero, surface its stderr directly to chat and abort the wizard. Do NOT retry silently.

3b — Render deploy-key block to chat

The script already printed the key + fingerprint to its stdout. Echo that block back to the user verbatim, prefaced with:

Add this key as a DEPLOY KEY with WRITE access to <REPO_URL>.
GitHub:    Settings → Deploy keys → Add deploy key ("Allow write access")
GitLab:    Settings → Repository → Deploy keys → Enable with write access
Bitbucket: Repository settings → Access keys → Add key (write)
Self-host: check your provider's "deploy key" or "access key" feature

NEVER show the private key. The .pub file is safe to display.

3c — Confirm click

Emit ONE AskUserQuestion:

{
  "questions": [
    {
      "question": "Have you added the deploy key to the repo with WRITE access?",
      "header": "Deploy key",
      "multiSelect": false,
      "options": [
        {"label": "Yes, it's added",      "description": "Proceed to a test push"},
        {"label": "Show me the key again", "description": "Re-print the public key + fingerprint"},
        {"label": "Abort",                "description": "Cancel — re-run /sleep-setup later"}
      ]
    }
  ]
}

Handle each option:

Yes → set KEY_ADDED = true, proceed to Phase 4.
Show again → re-print the block from 3b, re-emit this click.
Abort → print "aborted — re-run /sleep-setup later"; exit.

Verify-criterion

~/.ssh/keisei-memory-sync(.pub) exist.
~/.claude/memory/sync-repo/.git/ exists.
~/.claude/secrets/.env contains all three KEI_MEMORY_* refs.
KEY_ADDED == true.
Exactly ONE AskUserQuestion (plus loops on "Show me again").

2.3 KiB Raw Permalink Blame History