Add experimental folder and initial spec commands

[anj-s]

Conductor_Exp: SDLC Spec Isolation Migration

The integration of agent-spec-sdlc isolation capabilities into the conductor extension. To adhere to a strict protocol demanding zero destructive changes to the existing conductor logic, an entirely isolated dual-stack has been scaffolded under the /conductor_exp namespace.

Core Features Delivered

1. Fully Isolated Extension Namespace (/conductor_exp)
   • Added a lightweight route binding in gemini-extension.json.
   • Duplicated setup, newTrack, and implement inside commands/conductor_exp/ and heavily patched their prompts with isolation guardrails, preventing them from interacting with or mutating the root conductor ecosystem destructively.
2. Strict Git Worktree Execution (policies/conductor_exp.toml)
   • A custom policy limits AI tool mutations during /conductor_exp sessions, strongly biasing the agent to act only inside .gemini/worktrees/<trackId>.
3. Standalone Backend Tooling (conductor_exp_backend/)
   • Ported manageSpec.ts, orchestration.ts, and cli.ts into a siloed package to avoid root package.json pollution.
   • Stripped unnecessary MCP layers and compiled flawlessly to parse conductor/tracks/ hierarchies.

Architectural Changes

• /conductor_exp:setup: Injects an interactive toggle for Worktree Isolation directly into workflow.md.
• /conductor_exp:newTrack: Mandates YAML frontmatter parsing for Parent IDs (id, type, parentId) to compute DAG impact scopes.
• /conductor_exp:implement: Forces the agent to initialize a git worktree under .gemini/ and pins run_shell_command usage to this path.
• /conductor_exp:analyze: A newly created wrapper to execute the node conductor_exp_backend/dist/cli.js analyze|graph CLI scripts. Outputs structural mapping of tracks so you know what depends on what before proceeding with an implementation.
• conductor_exp_backend/src/*: Rewrote the directory looping logic from agent-spec-sdlc to match Conductor's nested tree pattern (conductor/tracks/<trackId>/spec.md).