wogiflow 2.6.4 → 2.7.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (29) hide show
  1. package/.claude/settings.json +0 -1
  2. package/lib/workspace-changelog.js +182 -0
  3. package/lib/workspace-channel-server.js +75 -2
  4. package/lib/workspace-contracts.js +151 -1
  5. package/lib/workspace-events.js +383 -0
  6. package/lib/workspace-gates.js +740 -0
  7. package/lib/workspace-integration-tests.js +299 -0
  8. package/lib/workspace-intelligence.js +486 -1
  9. package/lib/workspace-locks.js +371 -0
  10. package/lib/workspace-messages.js +203 -3
  11. package/lib/workspace-routing.js +144 -0
  12. package/package.json +1 -1
  13. package/scripts/flow-done-gates.js +70 -0
  14. package/.claude/rules/_internal/README.md +0 -64
  15. package/.claude/rules/_internal/document-structure.md +0 -77
  16. package/.claude/rules/_internal/dual-repo-management.md +0 -174
  17. package/.claude/rules/_internal/feature-refactoring-cleanup.md +0 -87
  18. package/.claude/rules/_internal/github-releases.md +0 -71
  19. package/.claude/rules/_internal/model-management.md +0 -35
  20. package/.claude/rules/_internal/self-maintenance.md +0 -87
  21. package/.claude/rules/architecture/component-reuse.md +0 -38
  22. package/.claude/rules/code-style/naming-conventions.md +0 -107
  23. package/.claude/rules/operations/git-workflows.md +0 -92
  24. package/.claude/rules/operations/scratch-directory.md +0 -54
  25. package/.claude/rules/security/security-patterns.md +0 -176
  26. package/.claude/skills/figma-analyzer/knowledge/learnings.md +0 -11
  27. package/.workflow/specs/architecture.md.template +0 -24
  28. package/.workflow/specs/stack.md.template +0 -33
  29. package/.workflow/specs/testing.md.template +0 -36
@@ -1,24 +0,0 @@
1
- # Architecture
2
-
3
- ## Pattern
4
-
5
- <!-- Detected during onboarding -->
6
- <!-- Examples: MVC, Clean Architecture, DDD, Microservices, Monolith -->
7
-
8
- ## Structure
9
-
10
- <!-- Project structure overview -->
11
- <!-- Key directories and their purposes -->
12
-
13
- ## Key Decisions
14
-
15
- <!-- Architecture decisions made for this project -->
16
- <!-- Trade-offs and rationale -->
17
-
18
- ## Dependencies
19
-
20
- <!-- Major dependencies and their purposes -->
21
-
22
- ---
23
-
24
- *This file is auto-populated during `flow onboard`. Update manually as architecture evolves.*
@@ -1,33 +0,0 @@
1
- # Tech Stack
2
-
3
- ## Framework
4
-
5
- <!-- Primary framework (e.g., Next.js, NestJS, FastAPI) -->
6
-
7
- ## Language
8
-
9
- <!-- Primary language (e.g., TypeScript, Python, Go) -->
10
-
11
- ## Database
12
-
13
- <!-- Database system if applicable (e.g., PostgreSQL, MongoDB) -->
14
-
15
- ## Package Manager
16
-
17
- <!-- npm, yarn, pnpm, pip, etc. -->
18
-
19
- ## Build Tools
20
-
21
- <!-- Build and bundling tools (e.g., Vite, Webpack, esbuild) -->
22
-
23
- ## Testing
24
-
25
- <!-- Test frameworks (e.g., Jest, Vitest, pytest) -->
26
-
27
- ## Other Tools
28
-
29
- <!-- Linters, formatters, CI/CD tools -->
30
-
31
- ---
32
-
33
- *This file is auto-populated during `flow onboard`. Update manually as stack evolves.*
@@ -1,36 +0,0 @@
1
- # Testing
2
-
3
- ## Test Framework
4
-
5
- <!-- Primary test framework (e.g., Jest, Vitest, pytest) -->
6
-
7
- ## Test Commands
8
-
9
- ```bash
10
- # Run all tests
11
- npm test
12
-
13
- # Run tests in watch mode
14
- npm run test:watch
15
-
16
- # Run specific test file
17
- npm test -- path/to/test.ts
18
- ```
19
-
20
- ## Test Structure
21
-
22
- <!-- Where tests are located -->
23
- <!-- Naming conventions -->
24
-
25
- ## Coverage
26
-
27
- <!-- Coverage requirements if any -->
28
- <!-- Coverage commands -->
29
-
30
- ## E2E Testing
31
-
32
- <!-- E2E framework if used (e.g., Playwright, Cypress) -->
33
-
34
- ---
35
-
36
- *This file is auto-populated during `flow onboard`. Update manually as testing strategy evolves.*