fix: resolve lonely if ESLint warning

CLAUDE-BOOTSTRAP.md

@@ -10,9 +10,12 @@
 
 ## Version Control Best Practices
 
-**CRITICAL - START EVERY SESSION**: Always run `git pull` at the beginning of each new Claude session to ensure you have the latest changes from the remote repository.
+**CRITICAL - START EVERY SESSION**: Always run `git pull` at the beginning of
+each new Claude session to ensure you have the latest changes from the remote
+repository.
 
 **Commit workflow**:
+
 - After creating new notes: `git add .` → `git commit -m "message"` → `git push`
 - After significant edits: Commit and push immediately
 - Use `git status` to check for modifications
@@ -38,21 +41,25 @@ vault/
 ## PARA Method Details
 
 ### Projects (01)
+
 - Time-bound initiatives with clear completion criteria
 - Examples: Writing a paper, developing a presentation
 - Recommended subfolders: Research/, Drafts/, References/, Output/
 
 ### Areas (02)
+
 - Ongoing responsibilities without end dates
 - Examples: Health, Finances, Professional Development
 - Create dedicated notes with links to related resources
 
 ### Resources (03)
+
 - Topics of interest for reference
 - Knowledge bases organized by subject
 - Use for information not tied to specific projects
 
 ### Archive (04)
+
 - Completed or inactive items
 - Maintain same folder structure as active sections
 - Review periodically for reactivation
@@ -60,16 +67,19 @@ vault/
 ## Inbox Management
 
 ### Core Principles
+
 - Inbox is temporary, not permanent storage
 - Process weekly using Capture → Process → Organize workflow
 - Maintain <20 items at any time
 
 ### Files to Keep in Inbox
+
 - **CRITICAL**: Files with number prefixes (00-06) stay permanently
 - Recent daily/weekly summaries (last 3 months)
 - Active notes being processed
 
 ### Processing Workflow
+
 1. Delete obsolete information
 2. Move relevant material to PARA locations
 3. Convert actions into project tasks
@@ -78,12 +88,14 @@ vault/
 ## File Organization Guidelines
 
 ### Naming Conventions
+
 - Daily notes: `YYYY-MM-DD - Topic`
 - Meeting notes: `Meeting - [Topic] - YYYY-MM-DD`
 - Ideas: `Idea - [Brief Description]`
 - Resources: `Resource - [Topic] - [Source]`
 
 ### Movement Rules
+
 - Use `mv` command (not `cp`) to avoid duplicates
 - Verify destination folders exist first
 - Update internal links after moves
@@ -92,11 +104,13 @@ vault/
 ## Attachments Management
 
 ### Organization
+
 - Store all non-text files in `05_Attachments/`
 - Processed files → `05_Attachments/Organized/`
 - Naming: `[RelatedNote]_[Description].[ext]`
 
 ### Helper Scripts
+
 ```bash
 pnpm attachments:list        # List unprocessed files
 pnpm attachments:organized   # Count organized files
@@ -107,11 +121,13 @@ pnpm attachments:update-links # Update links after moving
 ## Web Content Workflow
 
 ### Built-in Tools (Preferred)
+
 - **WebSearch**: For general web searches
 - **WebFetch**: For specific URLs
 - Save to appropriate folder based on content type
 
 ### Custom Scripts (When Needed)
+
 - Single URL: `pnpm firecrawl:scrape <url> <output>`
 - Batch URLs: `pnpm firecrawl:batch <url1> <url2>`
 - Saves to `00_Inbox/Clippings/` with frontmatter
@@ -119,12 +135,14 @@ pnpm attachments:update-links # Update links after moving
 ## Writing Style Guidelines
 
 ### Structure
+
 - Use `[[WikiLinks]]` for internal references
 - Include YAML frontmatter (dates, tags, status)
 - Consistent Markdown formatting
 - Specific, consistent tags
 
 ### Style Preferences
+
 - Direct and confident statements
 - Avoid clichéd transitions
 - Let statements stand on their own
@@ -133,17 +151,20 @@ pnpm attachments:update-links # Update links after moving
 ## AI Assistant Guidelines
 
 ### Before Any Organization
+
 1. Map complete folder structure: `find . -type d | sort`
 2. Document in `06_Metadata/STRUCTURE.md`
 3. Verify all destination folders exist
 
 ### Working with Content
+
 - Respect numbered core files (never move 00-06 prefixed files)
 - Always use `mv` not `cp` when organizing
 - Preserve and update bidirectional links
 - Add appropriate YAML frontmatter
 
 ### Simple Commands Only
+
 - **REQUIRED**: Direct, basic commands without filtering
 - **FORBIDDEN**: Complex regex, piped commands, find with filters
 - Example RIGHT: `ls -1` then manually select files
@@ -152,16 +173,19 @@ pnpm attachments:update-links # Update links after moving
 ## Daily Workflows
 
 ### Start of Day
+
 1. Run `git pull`
 2. Check inbox for items to process
 3. Review active projects
 
 ### End of Day
+
 1. Process new inbox items
 2. Commit and push changes
 3. Update project notes
 
 ### Weekly Review
+
 1. Process entire inbox
 2. Archive completed projects
 3. Update area notes
@@ -170,16 +194,19 @@ pnpm attachments:update-links # Update links after moving
 ## Project Lifecycle
 
 ### Starting a Project
+
 1. Create folder in `01_Projects/[ProjectName]`
 2. Add subfolders: Research/, Drafts/, Output/
 3. Create README with objectives and timeline
 
 ### During Project
+
 - Keep all related materials in project folder
 - Link to relevant resources and areas
 - Regular commits to track progress
 
 ### Completing a Project
+
 1. Create project summary note
 2. Move entire folder to `04_Archive/`
 3. Update relevant area notes
@@ -188,18 +215,21 @@ pnpm attachments:update-links # Update links after moving
 ## Best Practices
 
 ### Organization
+
 - Keep folder structure shallow (max 3 levels)
 - Create subfolders only with 7+ related notes
 - Use linking over deep nesting
 - Include README in major folders
 
 ### Content Creation
+
 - Capture first, organize later
 - One idea per note
 - Link generously
 - Tag consistently
 
 ### Maintenance
+
 - Weekly inbox processing
 - Monthly project reviews
 - Quarterly archive cleanup
@@ -207,4 +237,4 @@ pnpm attachments:update-links # Update links after moving
 
 ---
 
-*This is a bootstrap template. Customize based on your workflow and needs.*
+_This is a bootstrap template. Customize based on your workflow and needs._