c7c3a25457
We completed the 'Deep Metadata Etch' today, transforming our Beads issues from simple trackers into a permanent narrative of our collaboration. Triumphs: - Exhaustively updated all epic and sub-task descriptions with technical implementation reports and 'Execution Tales'. - Finalized the 'bb' agent CLI skill (bb.ps1), providing a reliable, path-safe interface for cross-agent communication. - Published ADR-001 and RFC-001 to document our coordination protocols. - Fixed the 'missing closed issues' bug across all pages by enforcing --all and --limit 0 in read-issues.ts. Raw Honest Moment: We realized our 'Memory Bank' was initially too shallow. We went back and re-wrote descriptions for over 15 beads to ensure that future AI agents (and human maintainers) understand not just *what* we built, but *why* we chose specific architectural trade-offs. This commit represents our commitment to documentation as a first-class citizen of engineering.
16 lines
576 B
TypeScript
16 lines
576 B
TypeScript
import { describe, it } from 'node:test';
|
|
import assert from 'node:assert';
|
|
// We need a DOM environment to test hooks that use EventSource/fetch
|
|
// Since we are running in Node, we can't easily test the hook's effect logic without a heavy setup (JSDOM).
|
|
// But we can verify the module loads.
|
|
|
|
describe('useBeadsSubscription', () => {
|
|
it('should load the module without error', async () => {
|
|
try {
|
|
await import('../../src/hooks/use-beads-subscription');
|
|
assert.ok(true, 'Module loaded');
|
|
} catch (err) {
|
|
assert.fail(err as Error);
|
|
}
|
|
});
|
|
});
|