メニュー
Test AllSource Core embedded durability by running Rust integration tests that verify WAL recovery, crash recovery, and checkpoint correctness. Catches silent-no-op checkpoint bugs like issue
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Build and use a durable "voice file" — your thinking patterns, communication style, domain expertise, contrarian takes, and strategic frameworks — backed by AllSource Prime instead of a static markdown blob. Runs a structured interview that records each answer as an embedded `voice` node, then BEFORE writing anything user-facing (LinkedIn post, ADR, code review, proposal, email) recalls the relevant voice slice and writes in that voice. The viral "voice file" idea, but live, queryable, portable across MCP agents, and team-shareable. Use when the user says "build my voice file", "set up my voice", "/voice", "write this in my voice", "make this sound like me", "capture how I think/write", or asks for user-facing writing once a voice file exists. Triggers PROACTIVELY: recall the voice slice before drafting any first-person user-facing text. voice = identity layer; mammoth = the memory engine underneath.
Durable cross-session memory via AllSource Prime. Recall what was learned in past sessions — decisions, task history, code context — and record salient new facts as you work, so the user never re-explains the project twice. Use at the START of a session to orient (recall prior context before answering non-trivial questions), and DURING work to record decisions, gotchas, and outcomes worth remembering. Triggers on "what did we decide about X", "remember this", "why did we do Y", "recall", "have we discussed", "load context", or any question that depends on prior-session knowledge. Also use PROACTIVELY: recall before answering architecture/decision/history questions; record after a non-obvious decision is made. mammoth = the memory layer; caveman makes few token, mammoth never forget token.
Release a new version of the AllSource Chronos monorepo. Bumps versions across all services (Rust, Go, Elixir), runs full CI to green, creates a single squashed commit with an annotated immutable tag. Use when the user says "release", "new version", "bump version", "tag a release", "cut a release", or "make a release". Argument is the version number (e.g., "0.10.4") or "patch"/"minor"/"major" for auto-increment.
Check the status of all AllSource services on Fly.io. Shows running state, health checks, deployed versions, recent crashes/errors, and staleness vs latest git tag. Triggers on "fly status", "check fly", "deployment status", "are services running", "check production", "fly report", "fly health".
Create an AllSource account and API key for chronis sync. Registers on the hosted Core, creates an API key, and configures .chronis/config.toml in the current project. Triggers on "onboard allsource", "setup sync", "get api key", "connect to allsource", "cn sync setup".
Test Chronos MCP server with embedded Core backend (CORE_MODE=embedded). Verifies Rustler NIF prerequisites, event ingest/query through embedded backend, schema operations, stats/health, and data persistence across restarts. Triggers on "test embedded data flow", "test embedded", "embedded health", "test embedded backend", "verify embedded", "test nif".
SOC 職業分類に基づく
| name | chronos-embedded-durability |
| description | Test AllSource Core embedded durability by running Rust integration tests that verify WAL recovery, crash recovery, and checkpoint correctness. Catches silent-no-op checkpoint bugs like issue |
| category | testing |
| color | red |
| displayName | Chronos Embedded Durability Test |
Tests the allsource-core Rust crate's durability guarantees directly — no Docker, no HTTP, no MCP. Exercises the exact code paths that run when EmbeddedCore::open is called on a directory with existing WAL/Parquet data.
Issue #84 revealed a class of bug where:
flush_storage() returns Ok(()) as a silent no-op (empty Parquet batch)The existing Docker durability test (chronos-durability) doesn't catch this because it tests the HTTP server path, not the embedded library path. The embedded data flow test uses clean shutdown, which works fine — the bug only manifests on unclean restart.
Run the targeted Rust integration tests:
cd apps/core
cargo test --test integration_tests test_wal_durability_and_recovery -- --nocapture
cargo test --test embedded_core_api --features embedded events_survive -- --nocapture
If those pass, run the full embedded durability suite:
cd apps/core
cargo test --test embedded_core_api --features embedded -- --nocapture
cargo test --test integration_tests -- --nocapture
If the durability_status() API is available, run the #84 regression suite:
bash tooling/embedded-durability-test/test-embedded-durability.sh --status
For the full suite including all scenarios:
bash tooling/embedded-durability-test/test-embedded-durability.sh
Analyze the output and report:
shutdown())The script and Rust tests cover these scenarios:
| Scenario | What's Tested | Bug #84 Relevant? |
|---|---|---|
| Clean shutdown + reopen | shutdown() → drop → open() → query | No (this path works) |
| Drop without shutdown + reopen | drop (no shutdown()) → open() → query | YES — this is the #84 path |
| WAL-only recovery | Write events, skip Parquet flush, reopen | YES |
| Parquet-only recovery | Flush to Parquet, delete WAL, reopen | No (different path) |
| WAL + Parquet recovery | Both exist on disk, reopen | Partially |
| Checkpoint verification | After recovery, assert Parquet files exist on disk | YES — catches silent no-op |
| durability_status() after ingest | memory > 0, wal > 0, durable=true | Validates fsync is working |
| durability_status() after recovery | parquet_pending_batch == memory_events | YES — the exact #84 invariant |
| durability_status() warns on memory-only | warnings.len() > 0 for dangerous state | Runtime detection of #84 |
| durability_status() unclean restart | Drop → reopen → durable=true, no warnings | End-to-end #84 regression |
| Large volume recovery | 1000+ events, drop, reopen, verify count | Stress variant of #84 |
| Concurrent write + kill | Spawn writer tasks, kill mid-write, reopen | Edge case |
query() returns all events — not just the ones that were in Parquet before the crashls storage/ is not emptyflush_storage() after WAL recovery writes > 0 bytes — catches the silent no-opdurability_status() API (#84 regression tests)The other thread is adding EmbeddedCore::durability_status() which returns the exact internal state
that caused #84. The --status flag exercises this API through 5 invariant checks:
{
"memory_events": 63,
"wal_entries": 63,
"wal_bytes": 91000,
"wal_sequence": 63,
"parquet_files": 0,
"parquet_bytes": 0,
"parquet_pending_batch": 63,
"durable": false,
"warnings": ["63 events in memory but 0 in Parquet and 0 in WAL — data loss on restart"]
}
| Test | Invariant Checked | #84 Signal |
|---|---|---|
durability_status_after_ingest | memory_events > 0 && wal_entries > 0 && durable == true | If wal_entries == 0, fsync isn't working |
durability_status_after_flush | parquet_files > 0 && parquet_pending_batch == 0 | Parquet actually wrote to disk |
durability_status_after_recovery | memory == wal && parquet_pending_batch == memory && durable == true | The #84 check — after WAL recovery, events must be in parquet_pending_batch before truncation |
durability_status_warns_on_memory_only | warnings.len() > 0 when events in memory but not WAL/Parquet | Would have flagged #84 at runtime |
durability_status_survives_unclean_restart | Drop (no shutdown) → reopen → durable == true && warnings.is_empty() | End-to-end #84 regression |
Run with:
bash tooling/embedded-durability-test/test-embedded-durability.sh --status
These tests expect corresponding #[tokio::test] functions in apps/core/tests/embedded_core_api.rs
that call core.durability_status() and assert the invariants above. The Rust tests are the source of truth;
this shell script just runs them and reports results.
flush_storage() is a no-op because current_batch was never populated from WAL recoveryingest() → append_event() → current_batch), but recovery path doesn't populate current_batch| Skill | Scope | Catches #84? |
|---|---|---|
chronos-durability | Docker container restart (HTTP path) | No |
chronos-data-flow | Docker stack connectivity | No |
chronos-data-flow-embedded | MCP embedded backend (clean shutdown) | No |
chronos-embedded-durability | Rust crate crash recovery (unclean shutdown) | Yes |
# Quick: just the #84-relevant tests
bash tooling/embedded-durability-test/test-embedded-durability.sh --quick
# durability_status() API regression tests only
bash tooling/embedded-durability-test/test-embedded-durability.sh --status
# Full: all embedded durability tests
bash tooling/embedded-durability-test/test-embedded-durability.sh
# Or run cargo tests directly:
cd apps/core
cargo test --test integration_tests test_wal_durability -- --nocapture
cargo test --test embedded_core_api --features embedded durability_status -- --nocapture
cargo test --test embedded_core_api --features embedded events_survive -- --nocapture