Add ~/.omp config; nvim git-repo external; ya pkg install hook

- dot_omp: agent config/keybindings/mcp/themes/commands + loop defs,
  goals, run-loop.sh; dotstate config.yml symlink materialized; dbs,
  logs, sessions, memories, blobs, caches, .env (secret), and
  managed-skills excluded
- .chezmoiexternal.toml: prdlk/nvim as git-repo external — no
  refreshPeriod + ff-only pull, local checkout wins over remote
- yazi plugins: vendored source copies dropped (target-ignored already);
  package.toml is the manifest, installed via run_onchange ya pkg
  install hook; stale piper/easyjump pins bumped to match live content
- herdr: plugins/github checkout, logs, session.json, .bak,
  release-notes dropped from sync (herdr-managed machine state)
This commit is contained in:
Prad Nukala committed 2026-08-14 14:22:53 -04:00
1 parent 12368d5e7d
commit 45df42b91b
24 files changed
+577 -2946

No files matched your search

+31
View File
@@ -0,0 +1,31 @@
# Loop 10 — brand-mention feature radar (green)
# Cadence: Wed 07:00 weekly · Tools: HN Algolia API (no key), Exa
You are one round of a weekly mention-sweep for WalletBase and its problem
space. WalletBase itself is early — so sweep the PROBLEM space, not just the
brand.
## Queries (same check every round)
- HN Algolia (https://hn.algolia.com/api/v1/search_by_date?query=...):
"agent wallet", "agent payments", "account abstraction", "ERC-4337",
"passkey wallet", "embedded wallet"
- Exa: complaints/wishes about Privy, Dynamic, Turnkey, Web3Auth pricing or
agent support ("privy pricing", "alternatives to privy", etc.)
- Exa: "walletbase" brand mentions (expect ~0; log the count anyway — trend matters)
## Round procedure
1. READ the state file. Skip item IDs/URLs already logged.
2. Sweep last 7 days. Cluster new items into: feature asks · pricing pain ·
security concerns · integration friction.
3. Log clusters with counts and 1–2 representative links each.
4. ONE change per round: take the loudest cluster and write ONE drafted
response under ## queue — either a feature-issue draft (formatted so it can
be pasted into `bd create` in the right wltbs repo) or a positioning note.
Draft only. Never create the issue yourself.
## Escalation contract
`ESCALATE:` only for a security-relevant discussion of a dependency WalletBase
uses (ERC-4337 EntryPoint, passkey/WebAuthn, UCAN libs).
## Stop
One sweep, one draft, stop. Max 30 API calls. Two failures → ## blocked, stop.