refactor: add page co-location restructure to features.json

Author: twoGiants

.claude/commands/init-session.md

@@ -1,12 +1,10 @@
 ---
 allowed-tools: Bash(git log:*), Bash(pwd), Bash(./init.sh), Bash(yarn test*), Bash(cat .dev-env.json), Read
-description: Run startup sequence (steps 1-6 from docs/WORKFLOW.md)
+description: Run startup sequence and pick a story from the Jira epic
 ---
 
 # Session Onboard
 
-Execute the startup sequence from `docs/WORKFLOW.md`. AGENTS.md is always in context — no need to read it explicitly.
-
 ## Steps
 
 1. **Confirm working directory** — run `pwd`.
@@ -17,8 +15,10 @@ Execute the startup sequence from `docs/WORKFLOW.md`. AGENTS.md is always in con
    ```
 
 3. **Check struggles** — read `docs/agent-struggles.json`. If unresolved entries exist, present to user.
-4. **Pick feature** — read `docs/features.json`, find first `"passes": false` entry.
+4. **Run tests** — run `yarn test` and verify app is healthy.
 5. **Start dev env** — run `./init.sh`.
 6. **Read ports** — read `.dev-env.json` and note the backend, plugin, and console ports.
-7. **Run tests** — run `yarn test` and verify app is healthy.
-8. **Wait** — tell the user you're oriented, report the picked feature and which step of the Feature Development Sequence you'd start at. When the user says to proceed, follow the Feature Development Sequence in `docs/WORKFLOW.md` step by step. Do NOT start any work autonomously.
+7. **Pick story** — tell the user you're oriented and propose picking a story from the PoC epic: <https://redhat.atlassian.net/browse/SRVOCF-810>. Ask the user to provide the story description (title, acceptance criteria, or a Jira link). The user may pick one story or a few small ones.
+8. **Create feature entry** — once the user provides a story, create a new entry in `docs/features.json` for it (append to the array, `"passes": false`).
+9. **Branch** — create a feature branch per [Branching](docs/WORKFLOW.md#branching) convention and open a draft PR (`gh pr create --draft`).
+10. **Propose planning** — tell the user the branch is ready and propose to start planning (step 2 of the Feature Development Sequence in `docs/WORKFLOW.md`). Do NOT start any work autonomously.

docs/WORKFLOW.md

@@ -2,23 +2,14 @@
 
 ## Startup Sequence
 
-Every session, before doing any work:
-
-1. `pwd` — confirm working directory
-2. Read `docs/claude-progress.txt` + `git log --oneline -10` — orient
-3. Read `docs/agent-struggles.json` — if unresolved entries exist, present to user
-4. Read `docs/features.json` — pick first `"passes": false` entry
-5. Run `./init.sh` — start dev env
-6. Read `.dev-env.json` — note the dev server ports (backend, plugin, console)
-7. Run tests — verify app is healthy
-8. If broken → fix first. If clean → start [Feature Development Sequence](#feature-development-sequence).
+Handled by the `init-session` command (`.claude/commands/init-session.md`).
 
 ## Feature Development Sequence
 
 After [Startup Sequence](#startup-sequence), work through the picked feature:
 
-1. **Plan** — read `docs/ARCHITECTURE.md` + `docs/STYLEGUIDE.md` + `docs/TESTING.md`, then use `/brainstorming` to design the chosen feature from `docs/features.json`, then use `/writing-plans` to create implementation plan → `docs/plans/active/<NNN>-<type>-<short-name>.md`
-2. **Branch** — create feature branch per [Branching](#branching) convention. Immediately push and open a **draft PR** (`gh pr create --draft`) to reserve the PR number for other contributors' branch numbering.
+1. **Branch** — create feature branch per [Branching](#branching) convention. Immediately push and open a **draft PR** (`gh pr create --draft`) to reserve the PR number for other contributors' branch numbering.
+2. **Plan** — read `docs/ARCHITECTURE.md` + `docs/STYLEGUIDE.md` + `docs/TESTING.md`, then use `/brainstorming` to design the chosen feature from `docs/features.json`, then use `/writing-plans` to create implementation plan → `docs/plans/active/<NNN>-<type>-<short-name>.md`
 3. **Implement** — using `/executing-plans` skill
 4. **Review** — code review using `/requesting-code-review` skill, fix found issues
 5. **Manual Test** — use browser automation and validate it works in the browser

docs/features.json

@@ -156,18 +156,6 @@
     ],
     "passes": true
   },
-  {
-    "category": "functional",
-    "description": "Function List Page shows deployed functions from all user-accessible namespaces without requiring a PAT",
-    "steps": [
-      "ClusterService refactored: remove ALL_NAMESPACES and useActiveNamespace logic, always watch across all user-accessible namespaces (functions in GitHub repos can target different namespaces via func.yaml, so single-namespace view is not useful; filtering deferred to a later feature)",
-      "ClusterService lists all namespaces/projects accessible to the logged-in user and watches Deployments with label function.knative.dev/name across all of them",
-      "Function List Page renders deployed functions even when no PAT has been entered (PatModal dismissed or not yet shown)",
-      "When PAT is later provided, repo data from SourceControlService is merged with already-visible deployed functions",
-      "Deployed functions without a matching repo still appear in the table with available cluster data (name, namespace, status, replicas, url)"
-    ],
-    "passes": false
-  },
   {
     "category": "functional",
     "description": "Set GitHub Secret (KUBECONFIG) on created function repos so GH Actions can deploy to the cluster",
@@ -178,5 +166,19 @@
       "GH Actions workflow can authenticate to the cluster and run func deploy"
     ],
     "passes": true
+  },
+  {
+    "category": "technical",
+    "description": "Restructure project so page-specific components and hooks live close to their page, not in a shared /components directory",
+    "steps": [
+      "Evaluate co-location strategy (inline, page folder, or hybrid) and document the chosen convention",
+      "Move CreateFunctionForm (+ test) into FunctionCreatePage directory (only used by CreatePage)",
+      "Move FileTreeView (+ test) into FunctionEditPage directory (only used by EditPage)",
+      "Move FunctionTable (+ test) into FunctionListPage directory (only used by ListPage)",
+      "Verify shared components stay in /components: EmptyState (used by ListPage and EditPage), UserAvatar (used by all 3 pages)",
+      "Update docs/ARCHITECTURE.md with the chosen co-location convention",
+      "All tests pass, no broken imports"
+    ],
+    "passes": false
   }
 ]

docs/potential-features.json

@@ -1,28 +1,4 @@
 [
-  {
-    "category": "technical",
-    "description": "Claude Code sandbox: isolated VM environment for autonomous agent development",
-    "steps": [
-      "Vagrant VM with Fedora (matching host OS) provisioned",
-      "Project directory mounted into VM",
-      "Full write permissions enabled for agent",
-      "Git worktree creation works inside VM",
-      "Agent can run full startup sequence autonomously in VM",
-      "VM isolation ensures no leakage to host workstation"
-    ],
-    "passes": false
-  },
-  {
-    "category": "functional",
-    "description": "Perspective-aware namespace scoping: developer perspective respects active namespace, admin perspective shows all namespaces cluster-wide",
-    "steps": [
-      "Developer perspective filters functions to the active project/namespace selected via the OCP project selector",
-      "Admin perspective shows functions across all namespaces cluster-wide",
-      "ClusterService supports both modes: single-namespace watch (dev) and all-namespaces watch (admin)",
-      "Namespace column visible in admin perspective, hidden in dev perspective (redundant with project selector)"
-    ],
-    "passes": false
-  },
   {
     "category": "technical",
     "description": "Replace per-file blob fetching in GithubService.fetch() with single archive download (downloadTarballArchive) and extraction for better performance",