Forker Fractal upstream et structurer le workspace Cargo #1
Labels
No labels
module:M0-setup
module:M1-stt
module:M1-stt
module:M2-ai
module:M2-ai
module:M3-rich
module:M3-rich
module:M4-bridge
module:M4-bridge
module:M5-bonus
module:M5-bonus
module:setup
priority:high
priority:high
priority:low
priority:low
priority:medium
priority:medium
type:chore
type:chore
type:feature
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
charles/my-fractal#1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Contexte
Point de départ du projet : créer le fork de Fractal et mettre en place la structure multi-crates du workspace.
Critères d'acceptation
Cargo.tomlworkspace avec les crates membres :fractal-core,fractal-gtk,fractal-ext,fractal-stt,fractal-ai,fractal-rich,fractal-bridgecrates/,data/,docs/,po/)cargo check --workspace) sans erreur.cargo/config.toml+rust-toolchain.toml)Notes techniques
fractal-core,fractal-gtkfeature/m1-stt,feature/m2-ai-agent, etc.AgentDetector: identifier les bots et agents IA Matrix #11RichMessageParser: détecter et extraire les blocsdata-fx-*du HTML #29BridgeType::detect(): identifier les puppet users par patterns user ID #47