44 lines
3.4 KiB
Markdown
44 lines
3.4 KiB
Markdown
<!-- generated 2026-02-28 04:16 -->
|
|
|
|
Current Context
|
|
The current focus is on stabilizing the Signet dashboard (Astro/React stack) after resolving a critical Svelte 5 reactivity bug, while maintaining the ongoing implementation of the Skills API module and integration of Pipeline configurations.
|
|
|
|
Active Projects
|
|
|
|
1. Signet Dashboard Bug Fixes
|
|
Location: `dashboard/` (specifically `SettingsTab.svelte`)
|
|
Status: Completed & Verified.
|
|
Details: Resolved a `effect_update_depth_exceeded` error that prevented collapsible sections in the Settings tab from being clickable. The issue was a reactivity cycle where the `$effect` tracked a reactive `configFiles` prop while mutating `$state`.
|
|
Next Steps: Ensure the fix is stable in production and monitor for similar reactivity issues in other Svelte components.
|
|
|
|
2. Skills Module Implementation
|
|
Location: `packages/daemon/src/routes/skills.ts`
|
|
Status: Designed/Architected.
|
|
Details: Developing RESTful HTTP API endpoints for skills management (GET, POST, DELETE). The module is designed with zero database dependencies.
|
|
Next Steps: Implement the route handlers and test daemon change verification steps.
|
|
|
|
3. Pipeline Configuration Integration
|
|
Location: `isaac-research-chain` (destination repo)
|
|
Status: Pending.
|
|
Details: Integrating the PipelineV2Config, which currently uses a flat structure, into the target repository.
|
|
Next Steps: Execute the merge process for the PipelineV2Config.
|
|
|
|
Recent Work
|
|
|
|
Svelte 5 Reactivity Fix: Identified and patched the reactivity bug in `SettingsTab.svelte`. The fix involves wrapping the `st.init(configFiles)` call in `untrack()` to prevent the `$effect` from creating a dependency loop that triggered infinite re-initialization of the store. The dashboard and daemon have been restarted and verified to be functioning correctly with Playwright.
|
|
Daemon Management: Performed daemon restarts and testing to validate the Settings tab fix. Ensured `bun.lockb` and environment variables are correctly configured.
|
|
Agent Configuration: Clarified the path for agent profile storage (`~/.agents/`) to ensure correct file system interactions.
|
|
|
|
Technical Notes
|
|
|
|
Stack: The application frontend uses Astro for the static site shell and React components for dynamic UI elements. The core daemon logic is written in TypeScript.
|
|
Deployment Target: The static site builds are intended for deployment at `https://www.signetai.sh`.
|
|
Agent Config Path: All agent profile configurations must be stored in `~/.agents/` and sourced from `AGENTS.md`, not `~/.signet/`.
|
|
UI Development Constraints: Strict rule—UI work (Svelte, React, Tailwind) must not be delegated to subagents. Must be handled directly by the assistant with direct reference passing.
|
|
|
|
Rules & Warnings
|
|
|
|
UI Work Prohibition: Never delegate UI debugging or coding tasks (Svelte/React components, styling) to subagents. The assistant must execute these tasks manually.
|
|
Daemon Verification: Before deploying daemon changes, ensure full verification is performed to prevent runtime errors.
|
|
Path Correctness: Always use `~/.agents/` for agent configuration files.
|
|
- Svelte 5 Awareness: Be vigilant about Svelte 5 reactivity features. Issues often arise when `$state` is initialized inside closures or when `$effect` creates circular dependencies with reactive props. Use `untrack()` when necessary to break those loops. |