Merged
Conversation
…dd priority field - TaskStatus: backlog→planning, review→ai-review, add human-review - Add optional TaskPriority type and priority field to Task interface - Update all references in yaml-store and MCP tools Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…chema enums, handler descriptions, and request_review target status Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…lues Adds migrate-statuses.ts script that converts existing YAML project files from old status values (backlog → planning, review → ai-review) with --dry-run support and atomic file writes. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
… and create cn() utility Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
… light/dark theme Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
… toggle + accent presets) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…olumn layout Expand TaskStatus from 4 values (backlog, in-progress, review, done) to 5 values (planning, in-progress, ai-review, human-review, done). Add TaskPriority type and optional priority field to Task interface. Update column configuration to match. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…d, add status badge, priority label, description preview, relative timestamp Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…askCard.tsx Migrate both components from inline styles to Tailwind utility classes. DroppableColumn now uses flex-1 for 5-column equal-width layout with Aperant-style headers. Added missing status CSS variables (planning, ai-review, human-review) to globals.css for both light and dark themes. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…oned nav Migrated Sidebar from inline styles to Tailwind utility classes with cn() helper. Restructured into clear sections: logo header, project list with active accent border, inline project creation form, theme toggle (Sun/Moon icons), and prominent New Task button. Collapsed state shows icon-only view. Uses lucide-react icons throughout. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…nd Tailwind migration Migrate [project]/page.tsx from inline styles to Tailwind utility classes. Update default form status from 'backlog' to 'planning'. Import cn() utility. All 5 columns render correctly via COLUMNS array. DnD context unchanged. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
… Tailwind, 5 statuses, priority selector Migrated both components from inline styles to Tailwind utility classes using cn() helper. TaskDetailPanel now shows interactive status/priority selectors with all 5 statuses. TaskForm adds status and priority selectors for new task creation. Updated api.ts types to include priority in create/update signatures. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…eView, ViewToggle, CommentThread, Tooltip Migrate all four components from inline styles to Tailwind classes using cn() helper. - SwimlaneView: Tailwind classes, fix 'backlog' → 'planning' column reference, hover via CSS - ViewToggle: Conditional Tailwind classes for active/inactive toggle states - CommentThread: Tailwind styling, CSS focus: pseudo-class replaces onFocus/onBlur handlers - Tooltip: Position-based conditional Tailwind classes replace positionStyles object Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
… and CSS Align desktop app with board app's status model: replace backlog/review with planning/ai-review/human-review. Add TaskPriority type and CSS variables. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…x redesign in desktop app Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…x redesign in desktop app Add interactive status and priority selectors to TaskDetailPanel (matching board app's clickable pill buttons for changing task status/priority). Add status and priority selector fields to TaskForm for setting these on task creation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…aneView, ViewToggle, CommentThread, BoardKanbanPage Align desktop board components with web board parity: - SwimlaneView: fix add button to use 'planning' column (matching web board) - CommentThread: add ✦/● author prefixes, use ellipsis chars, reorder focus handlers - BoardKanbanPage: fix default status from 'backlog' to 'planning' - ViewToggle: already matched, no changes needed Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…cross all three services All three services pass TypeScript compilation: - packages/board-server: tsc --noEmit OK - apps/board: tsc --noEmit --skipLibCheck OK - apps/desktop: tsc --noEmit --skipLibCheck OK Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…mn board All automated checks pass: TypeScript compilation for board-server, board, and desktop. Code-level verification confirms 5-column config, theme toggle, and status defaults across all services. Manual browser testing needed for DnD, WebSocket sync, and theme persistence. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
siracusa5
changed the title
…react Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
siracusa5
added a commit
that referenced
this pull request
Mar 30, 2026
Tests expected old statuses ("backlog", "review") but the Kanban
redesign (PR #65) changed defaults to "planning" and split "review"
into "ai-review" / "human-review".
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
siracusa5
added a commit
that referenced
this pull request
Mar 30, 2026
* feat(marketplace): plugin ratings and reviews system
- Add Supabase migration for ratings/reviews tables with RLS policies
- Add auth utilities, OAuth callback route, sign-in/sign-out API routes
- Add SignInButton component
- Add review submission and flag API endpoints
- Add StarRating, ReviewForm, ReviewList, and FlagButton components
- Surface average rating on plugin cards and detail page stats bar
- Add reviews section to plugin detail page
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: update pnpm-lock.yaml after rebase
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: update board-server tests for 5-column status model
Tests expected old statuses ("backlog", "review") but the Kanban
redesign (PR #65) changed defaults to "planning" and split "review"
into "ai-review" / "human-review".
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This includes expanding from 4 columns to 5 (Planning, In Progress, AI Review, Human Review, Done), enriching task cards with progress bars, status badges, priority labels, and timestamps, adopting the Aperant dark theme with warm-tinted color tokens, and migrating from inline React styles to a Tailwind CSS utility-class approach. The desktop board (
apps/desktop) shares nearly identical components and must be kept in sync, and the board-server'sTaskStatustype must be updated to accommodate the new column structure. A data migration script is needed for existing YAML project files.