Add column width settings

.github/workflows/release.yml

@@ -0,0 +1,37 @@
+name: Release Obsidian plugin
+
+on:
+  push:
+    tags:
+      - "*"
+
+permissions:
+  contents: write
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v3
+
+      - name: Use Node.js
+        uses: actions/setup-node@v3
+        with:
+          node-version: "18.x"
+
+      - name: Build plugin
+        run: |
+          npm install
+          npm run build
+
+      - name: Create release
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          tag="${GITHUB_REF#refs/tags/}"
+
+          gh release create "$tag" \
+            --title="$tag" \
+            --draft \
+            main.js manifest.json styles.css

.gitignore

@@ -1,22 +1,31 @@
-# vscode
-.vscode 
-
-# Intellij
-*.iml
-.idea
-
-# npm
-node_modules
-
-# Don't include the compiled main.js file in the repo.
-# They should be uploaded to GitHub releases instead.
-main.js
-
-# Exclude sourcemaps
-*.map
-
-# obsidian
-data.json
-
-# Exclude macOS Finder (System Explorer) View States
-.DS_Store
+# vscode
+.vscode 
+
+# Intellij
+*.iml
+.idea
+
+# npm
+node_modules
+
+# Don't include the compiled main.js file in the repo.
+# They should be uploaded to GitHub releases instead.
+main.js
+
+# Exclude sourcemaps
+*.map
+
+# obsidian
+data.json
+
+# Exclude macOS Finder (System Explorer) View States
+.DS_Store
+
+# tmp directory
+tmp/
+
+# temporary planning artifacts
+tmp_specs/
+
+# beads
+.beads/

AGENTS.md

@@ -0,0 +1,14 @@
+# AI Agent Guidelines
+
+## 📚 Onboarding
+At the start of each session, read:
+1. `README.md` - High-level project overview
+2. `README.architecture.md` - Project structure and architecture
+3. `README.process.md` - Commit standards and release workflows
+4. `README.development.md` - Build commands and testing
+5. `README.planning.md` - Spec creation and planning standards
+
+## ✅ Quality Gates
+When writing code, you must not finish until all of these succeed:
+1. `npm run build` (Runs TypeCheck + Build)
+2. `npm test` (Runs Vitest)

CLAUDE.md

@@ -0,0 +1 @@
+See AGENTS.md for instructions.

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Chris Kerr
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

MAINTAINABILITY.md

@@ -0,0 +1,133 @@
+# Maintainability Improvement Opportunities
+
+This document outlines code maintainability improvements identified during codebase analysis. These changes should be considered for future development iterations to enhance code quality, reduce technical debt, and improve developer experience.
+
+## Code Organization & Architecture
+
+### 1. Extract Configuration Management
+- **Issue**: Configuration logic is scattered across multiple files (`settings_store.ts`, `text_view.ts`, `store.ts`)
+- **Improvement**: Create a centralized configuration service/class with validation
+- **Impact**: Easier to maintain settings, clearer separation of concerns
+
+### 2. Reduce Coupling Between UI and Business Logic
+- **Issue**: 
+  - `KanbanView` class has too many responsibilities (view logic, settings, task management)
+  - `Task` constructor has 7 parameters, some optional
+- **Improvement**: Consider dependency injection or builder pattern for Task creation
+- **Impact**: Better testability, clearer responsibilities
+
+### 3. Improve File Structure
+- **Issue**: 
+  - Tasks store contains complex initialization logic that could be extracted
+  - Mixed concerns in single files (validation, constants, and business logic in `task.ts`)
+- **Improvement**: Separate concerns into focused modules
+- **Impact**: Easier navigation, better code organization
+
+## Error Handling & Robustness
+
+### 4. Add Comprehensive Error Handling
+- **Issue**: File operations in `store.ts` lack error handling (vault.read operations)
+- **Improvement**: Add try-catch blocks and graceful degradation for parsing failures
+- **Impact**: Better user experience, fewer crashes
+
+### 5. Improve Async Operations
+- **Issue**: Multiple unhandled promises in `store.ts` (lines 76-78, 99-101)
+- **Improvement**: Proper promise handling and error boundaries for file system operations
+- **Impact**: Prevent silent failures, better debugging
+
+## Code Quality & Maintainability
+
+### 6. Reduce Code Duplication
+- **Issue**: 
+  - Settings retrieval pattern repeated 3 times in `store.ts` (lines 56-59, 85-88, 109-112)
+  - Similar validation logic in `task.ts` could be consolidated
+- **Improvement**: Extract common patterns into reusable functions
+- **Impact**: DRY principle, easier maintenance
+
+### 7. Improve Type Safety
+- **Issue**: 
+  - Brand types like `TaskString` and `DoneStatusMarkers` could have runtime validation
+  - Magic strings like "archived" should be constants
+- **Improvement**: Add runtime type guards and extract constants
+- **Impact**: Fewer runtime errors, better IntelliSense
+
+### 8. Extract Complex Logic
+- **Issue**: 
+  - Task constructor is 60+ lines with complex parsing logic
+  - Tag processing logic could be its own service
+- **Improvement**: Break down large functions, create specialized services
+- **Impact**: Better readability, easier testing
+
+## Testing & Documentation
+
+### 9. Expand Test Coverage
+- **Issue**: Only 3 test files for 15 TypeScript files (~20% coverage by file count)
+- **Missing**: Tests for `store.ts`, `actions.ts`, settings functionality, integration tests
+- **Improvement**: Add comprehensive unit and integration tests
+- **Impact**: Catch regressions, safer refactoring
+
+### 10. Add Documentation
+- **Issue**: 
+  - Complex regex patterns lack explanation
+  - No JSDoc for public APIs
+  - Missing README sections on architecture/contributing
+- **Improvement**: Add comprehensive documentation
+- **Impact**: Easier onboarding, better maintainability
+
+## Performance & Scalability
+
+### 11. Optimize File Processing
+- **Issue**: 
+  - No debouncing for rapid file changes beyond task updates
+  - Large files could cause performance issues without streaming
+- **Improvement**: Add proper debouncing and streaming for large files
+- **Impact**: Better performance with large vaults
+
+### 12. Memory Management
+- **Issue**: 
+  - Maps in `store.ts` grow indefinitely without cleanup
+  - Event listeners not properly cleaned up on plugin disable
+- **Improvement**: Implement proper cleanup strategies
+- **Impact**: Prevent memory leaks
+
+## Modern Development Practices
+
+### 13. Add Linting Rules
+- **Issue**: ESLint config is basic, missing rules for complexity, naming conventions
+- **Improvement**: 
+  - Add complexity rules, naming conventions
+  - Add Prettier for formatting
+  - Import/export organization rules
+- **Impact**: Consistent code style, catch potential issues
+
+### 14. Improve Build Process
+- **Issue**: 
+  - No pre-commit hooks
+  - Missing bundle analysis
+  - No automated testing in CI
+- **Improvement**: Add comprehensive development tooling
+- **Impact**: Catch issues early, better development workflow
+
+## Priority Recommendations
+
+### High Priority
+1. **Error Handling** (#4, #5) - Critical for stability
+2. **Code Duplication** (#6) - Easy wins with immediate impact
+3. **Test Coverage** (#9) - Essential for safe refactoring
+
+### Medium Priority
+4. **Configuration Management** (#1) - Foundation for other improvements
+5. **Type Safety** (#7) - Improves developer experience
+6. **Documentation** (#10) - Helps with team collaboration
+
+### Low Priority
+7. **File Structure** (#3, #8) - Can be done incrementally
+8. **Performance** (#11, #12) - Address when scaling issues arise
+9. **Development Tooling** (#13, #14) - Nice to have improvements
+
+## Implementation Notes
+
+- These improvements should be tackled incrementally
+- Consider creating feature branches for each major improvement area
+- Some changes may require coordination with pending work from other contributors
+- Test coverage should be expanded before major refactoring efforts

README.architecture.md

@@ -0,0 +1,63 @@
+# Architecture Guide
+
+## Project Structure
+- `src/entry.ts` - Plugin entry point
+- `src/ui/` - Svelte UI components and views
+- `src/ui/tasks/` - Task model, store, and actions
+- `src/parsing/` - Parsing utilities (tags, kebab case)
+- `src/ui/settings/` - Settings store and configuration
+- `specs/` - Design documents (tracked in git)
+- `tmp_specs/` - Temporary planning artifacts (gitignored)
+
+## System Architecture
+
+This plugin follows a modular architecture with clear separation between parsing, UI, and business logic layers.
+
+### Core Components
+
+**Plugin Entry** (`src/entry.ts`)
+- Main plugin class extending Obsidian's Plugin
+- Handles view registration and file menu integration
+- Manages plugin lifecycle and workspace events
+
+**View Layer** (`src/ui/`)
+- `text_view.ts`: Main view controller extending TextFileView
+- `main.svelte`: Primary Svelte component for the kanban interface
+- Component-based UI with reactive stores for state management
+
+**Task Management** (`src/ui/tasks/`)
+- `task.ts`: Core Task model with parsing and serialization
+- `store.ts`: Reactive task store with file system integration
+- `actions.ts`: Task manipulation operations (move, archive, delete)
+
+**Parsing Layer** (`src/parsing/`)
+- `kebab/`: String normalization utilities for consistent naming
+- `tags/`: Tag extraction and processing from task content
+
+**Configuration** (`src/ui/settings/`)
+- Settings store with reactive updates
+- Column management and color configuration
+- Scope and filtering preferences
+
+### Data Flow
+
+```
+Obsidian Files → File System Events → Task Parsing → Reactive Stores → Svelte UI
+                     ↓                                    ↑
+                 Task Actions ← User Interactions ← UI Components
+```
+
+**File Monitoring**: The plugin watches for file changes using Obsidian's vault events and automatically updates the task store when markdown files are modified.
+
+**Task Parsing**: Raw markdown content is parsed using regex patterns to identify task strings, extract metadata (tags, status, indentation), and create Task objects.
+
+**State Management**: Svelte stores provide reactive state management, automatically updating the UI when tasks or settings change.
+
+**Bidirectional Sync**: Changes made in the kanban UI are serialized back to the original markdown files, maintaining consistency between the kanban view and file content.
+
+### Key Design Patterns
+
+- **Observer Pattern**: File system events trigger task store updates
+- **Brand Types**: Type-safe string validation for markers and identifiers
+- **Reactive Stores**: Svelte-based state management for UI consistency
+- **Command Pattern**: Task actions encapsulate operations for undo/redo support

README.development.md

@@ -0,0 +1,41 @@
+# Development Guide
+
+## Tech Stack
+- **Language**: TypeScript (strict mode)
+- **UI Framework**: Svelte 4
+- **Build Tool**: ESBuild
+- **Testing**: Vitest
+- **Plugin Framework**: Obsidian API
+- **Package Manager**: npm
+
+## Build & Development Commands
+
+**Development**
+```bash
+npm run dev
+```
+Starts ESBuild in watch mode for live development. Built files go to root directory.
+
+**Build (Production)**
+```bash
+npm run build
+```
+Runs TypeScript type checking (`tsc -noEmit -skipLibCheck`) then builds optimized bundle with ESBuild. Always run this before releasing to catch type errors.
+
+**Test**
+```bash
+npm test
+```
+Runs the Vitest test suite. Tests are located in `src/` alongside source files.
+
+**Version Bump**
+```bash
+npm run version
+```
+Automated script that updates version in manifest.json and versions.json, then stages the files for commit.
+
+## Testing
+Run tests before every commit. Only commit if tests pass. Never disable tests
+to get them to pass. Only modifiy tests to get them to pass if you are SURE
+the failure is expected due to the PR. Otherwise, fix the non-test code or
+check with the human operator.