Create a Focused Workshop Experience

Work directly in:

/home/kernel-kain/Documents/Github/unfinished-business

Execution rules:

1. Work only on the main branch.
2. Begin with:
   • git status
   • git switch main
   • git pull --ff-only origin main
3. Preserve all unrelated changes, untracked files, and existing stashes. Do not apply, delete, or commit .backboard/, .unfinished-business/, .env files, credentials, or the existing stash unless this phase explicitly requires it.
4. Read the relevant source, tests, AGENTS.md files, and documentation before editing.
5. Implement only the phase described below. Do not begin the next phase.
6. Maintain backward compatibility with existing saved projects through explicit migrations.
7. Do not expose provider secrets, prompts containing secrets, or private model output in logs, telemetry, screenshots, or error messages.
8. Add or update tests for every behavior changed.
9. After implementation, update the relevant project documentation, including:
   • README.md when user-facing behavior changes
   • docs/ARCHITECTURE.md
   • docs/DECISIONS.md
   • docs/IMPLEMENTATION_PLAN.md
   • docs/EVIDENCE.md
   • docs/RELEASE_NOTES.md
   • any phase-specific setup or integration documentation
10. Mark the phase complete in the implementation plan only after its acceptance criteria pass.
11. Run all relevant verification. At minimum:

• npm run typecheck
• npm test
• npm run build Run visual, security, budget, contract, migration, or integration tests when affected.

1. Review the final git diff for accidental files, secrets, debugging output, and unrelated changes.
2. Commit with the commit message specified by this phase.
3. Push the commit to origin/main. Never force-push.
4. If the push is rejected because origin/main advanced, fetch and rebase safely, resolve only scoped conflicts, rerun verification, and push normally.
5. Finish with:

• implementation summary
• changed files
• documentation updated
• tests and results
• known limitations
• commit hash
• push result

Do not stop for ordinary implementation decisions. Stop only if there is a destructive conflict, missing required credential, irreconcilable remote conflict, or a decision that would materially change the product’s intended behavior.

Implement Phase 5: simplify the workshop and reorganize OpenCode controls.

Objectives:

• Present one primary task at a time.
• Hide technical machinery until it is relevant.
• Replace confusing session notes and run inspector terminology.

Implementation requirements:

1. Refactor the workshop into:
   • focused main task area;
   • collapsible project-outline drawer;
   • contextual activity/results drawer;
   • compact model and connection header.
2. Preserve all existing functionality during the layout change.
3. Rename Run Inspector to Activity & results.
4. Organize it into:
   • Progress
   • Changes
   • Checks
5. Hide the activity drawer when there has been no relevant operation.
6. Put native IDs, capability mappings, raw evidence, and provider payloads under Technical details.
7. Replace Session notes with Project memory:
   • decisions;
   • user answers;
   • assumptions;
   • constraints;
   • unresolved questions.
8. Keep raw transcripts in advanced diagnostics rather than the primary workspace.
9. Split OpenCode controls into:
   • Model & connection
   • Contextual permission request
   • Advanced diagnostics
10. Keep sessions, agents, commands, skills, MCP, LSP, formatters, low-level revert, and export controls out of the normal user flow.
11. Avoid loading expensive advanced diagnostics before the user opens them.
12. Ensure there is one clear primary action per stage.
13. Improve mobile/tablet behavior, keyboard navigation, focus management, loading announcements, and reduced-motion behavior.
14. Update intentional visual snapshots.

Acceptance criteria:

• The main task is understandable without opening advanced controls.
• Empty technical panels no longer occupy permanent screen space.
• Permission requests remain impossible to miss.
• Project memory is useful and editable.
• All primary workflows work with keyboard and screen reader navigation.

Commit message:

refactor(ui): create a focused workshop experience