shraga 0.1.109 → 0.1.111

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (18) hide show
  1. package/defaults/skills/mcp-server.md +2 -0
  2. package/defaults/skills/self-aware.md +1 -1
  3. package/dist/client/assets/{index-CFvAge7k.js → index-BNAh4GUs.js} +95 -92
  4. package/dist/client/assets/index-DIMte_k6.css +10 -0
  5. package/dist/client/index.html +2 -2
  6. package/package.json +2 -2
  7. package/src/client/components/ConversationHeader.tsx +38 -3
  8. package/src/client/components/ConversationPane.tsx +8 -2
  9. package/src/client/lib/ws.ts +1 -1
  10. package/src/mcp-stdio-bridge.ts +25 -9
  11. package/src/server/claude-account.ts +9 -0
  12. package/src/server/claude-usage.ts +34 -2
  13. package/src/server/claude.ts +2 -1
  14. package/src/server/data-sync.ts +7 -10
  15. package/src/server/engine/claude-code.ts +26 -5
  16. package/src/server/integrity-audit.ts +117 -46
  17. package/src/server/sessions.ts +17 -5
  18. package/dist/client/assets/index-CibL2gLy.css +0 -10
package/defaults/skills/mcp-server.md CHANGED
@@ -41,6 +41,8 @@ Add to `~/Library/Application Support/Claude/claude_desktop_config.json` (uses s
41
41
  }
42
42
  ```
43
43
 
44
+ Optional bridge env: `MCP_BRIDGE_TIMEOUT_MS` (protocol calls, default 60s) and `MCP_BRIDGE_TOOL_TIMEOUT_MS` (`tools/call`, default 30min). Past the bound the bridge answers with a JSON-RPC error instead of hanging.
45
+
44
46
  ## Available MCP Tools
45
47
 
46
48
  | Tool | Description |
package/defaults/skills/self-aware.md CHANGED
@@ -142,7 +142,7 @@ Your behavioral config (skills, MCPs, schedules, contacts, workspace, agent-conf
142
142
  - **Pull on demand**: `POST /api/data-sync/webhook` triggers a pull (GitHub webhook fires on every push)
143
143
  - **Change history**: `data/git-log.json` (gitignored, reconstructed) contains recent commit log — read it to understand what changed and when. Also available via `GET /api/data-sync/log`
144
144
  - **Recovery**: If data seems stale or missing, trigger a pull by restarting the service or calling the webhook
145
- - **Integrity audit**: `bun run src/server/integrity-audit.ts [git-ref]` compares current data/ against a baseline commit. Detects missing files, truncated content, degraded JSON (fewer entries in schedules/contacts/skills-defaults/api-keys), and invalid JSON. Runs automatically after every data-sync init — check logs for `[data-sync] ⚠️ DATA INTEGRITY`. Use manually when investigating suspected data loss.
145
+ - **Integrity audit**: `bun run src/server/integrity-audit.ts [git-ref] [data-dir]` checks the files that changed between a baseline commit and HEAD (unchanged files are not re-examined — widen the ref to cover older commits). Detects missing files, truncated content, degraded JSON (fewer entries in schedules/contacts/skills-defaults/api-keys), and invalid JSON (.json over 16MB is skipped with a warning). Runs automatically after every data-sync init — check logs for `[data-sync] ⚠️ DATA INTEGRITY`. Use manually when investigating suspected data loss.
146
146
 
147
147
  ### Scheduler gating
148
148
  Schedules sync across all envs but only **execute** where `DATA_SYNC_SCHEDULER_ACTIVE=true` (prod). Inactive envs load and serve schedules with their real `enabled` flags — they just never fire them (no timers armed). Manual "run now" still works anywhere. Event triggers respect the same gate (`fireEvent` no-ops unless active) so a webhook can't double-fire across blue-green.