Live smoke test โ 2026-04-08
Summary
A live smoke-test pass was run against https://kb.icvida.com after the simplification wave landed. The goal was to test the simplified core workflow rather than every advanced helper.
Core workflow tested
- health
- vault listing
- home UI load
- search on recently stored knowledge
- create raw capture
- read capture
- append to capture
- capture history
- create durable project doc
- read durable doc
- search durable doc
- recent activity
- tags listing
- delete durable doc
- verify delete behavior
Result
Overall result: PASS
Functional summary: - 17 successful core checks - 1 expected 404 after deleting the temporary durable test doc
The 404 was the correct post-delete behavior, not a product failure.
Timing observations
Live end-to-end request times were roughly: - reads/searches: ~316โ420 ms - writes: ~379โ418 ms - delete: ~383 ms
Interpretation: - not instant - but clearly usable for a remote HTTPS wiki shared between humans and agents
Search observations
Worked well
- exact and near-exact knowledge retrieval worked well for recent stored docs
- examples:
pi teams,cheap executor,quick switcher - exact run-id search found the newly created live smoke capture immediately
Current limitation
Search still behaves like an exact-term system more than a fuzzy one.
That means it is best used with: - precise terms - vault filters - type filters - tag filters when relevant
UI observation
The home page now reflects the simplified framing:
- Shared markdown wiki
- Default workflow
This confirms that the simplification wave is visible in the live app, not only in the repo.
Activity and history observation
Recent activity correctly showed: - capture create - capture update - durable doc create - durable doc delete
History on the smoke capture correctly showed: - initial capture commit - append/update commit
Temporary artifacts created during test
Kept for evidence:
- inbox/2026/04/08/knowledge-hub-smoke-test-20260408-031805-eaadb0.md
Created then cleaned up:
- projects/smoke-tests/smoke-20260408-031805-eaadb0.md
Conclusion
The simplified default workflow is viable right now: 1. search 2. capture 3. read 4. append/update 5. history 6. optional durable docs
This supports the earlier conclusion that Knowledge Hub does not need a rewrite. It is ready to be used for real work while future improvements remain incremental.