Add comprehensive development roadmap via GitHub Issues

Created 10 detailed GitHub issues covering:
- Project activation and management UI (#1-2)
- Worker node coordination and visualization (#3-4)
- Automated GitHub repository scanning (#5)
- Intelligent model-to-issue matching (#6)
- Multi-model task execution system (#7)
- N8N workflow integration (#8)
- Hive-Bzzz P2P bridge (#9)
- Peer assistance protocol (#10)

Each issue includes detailed specifications, acceptance criteria,
technical implementation notes, and dependency mapping.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

frontend/node_modules/storybook/README.md

@@ -0,0 +1,51 @@
+# Storybook Core
+
+The `@storybook/core` package is the core of Storybook. It is responsible for the following:
+
+- the main UI of storybook
+- the UI used by addons
+- the API used by addons
+- the API used by the CLI
+- the API used by the server
+- prebundled code used by the browser
+- static assets used by the browser
+- utilities for CSF, MDX & Docs
+
+## Private package
+
+This package is not intended to be used by anyone but storybook internally.
+
+Even though this is where all of the code is located, it is NOT to be the entry point when using functionality within!
+
+Consumers of the code should import like so:
+
+```ts
+import { addons } from 'storybook/manager-api';
+```
+
+Importing from `@storybook/core` is explicitly NOT supported; it WILL break in a future version of storybook, very likely in a non-major version bump.
+
+# For maintainers
+
+## When to use `@storybook/core`
+
+In the following packages you should import from `@storybook/core` (and ONLY from `@storybook/core`):
+
+- `@storybook/core`
+- `@storybook/codemod`
+
+To prevent cyclical dependencies, these packages cannot depend on the `storybook` package.
+
+## When to use `storybook/internal`
+
+In every other package you should import from `storybook/internal` (and ONLY from `storybook/internal`).
+
+The heuristic is simple:
+
+> If you see a peerDependency on `storybook` in the `package.json` of the package you are working on, you should import from `storybook/internal`.
+
+## The 1 exception: the `storybook` package itself
+
+The sole exception is the `storybook` package itself.
+
+Obviously, the `storybook` package cannot depend on itself, so it must import from `@storybook/core`.