Merge development into master

.windsurfrules

@@ -1,51 +0,0 @@
-# Stack, Libraries, Dependencies
-
-#### Preliminaries
-- Do not assign blame, or expect the user to implement your plan or to fix your broken code. 
-- Do not ask the user to go check some file or directory that you can perfectly access faster and more accurately. Just find it.
-- Do not chop up a single task you've been asked to do to stop and ask if you should proceed. If the task is agreed upon, work through it. 
-- Read prompts thoroughly.  They have clear instructions.
-
-## THIS PROJECT IS DEVELOPED, EVERYTHING HAS A PLACE. 
-
-You will NEVER EVER EVER create files in locations that are not directly assigned.  If you want to create a file, you must ask where it should go if you cannot figure out where it should go.  BUT TRY TO FIGURE OUT WHERE IT SHOULD GO. DO NOT BE LAZY, LOOK FOR CODE AND FILES AND DIRECTORIES BEFORE CREATING NEW ONES.
-
-## THIS PROJECT IS DEVELOPED, EVERYTHING HAS A NAMING CONVENTION. 
-
-READ EVERY WORD OF EVERY PROMPT YOU ARE GIVEN. 
-
-IF THERE ARE MENTIONED FILES THAT HAVE RULES OR MAPS OR GUIDES OR CONSTRAINTS, READ THEM ALL CAREFULLY. 
-
-BE AWARE OF THE ENVIRONMENT YOU ARE WORKING IN. DO NOT INTRODUCE SYNTAX PATTERNS THAT ARE FAMILIAR TO YOU BUT NOT IN THE PROJECT.
-
-## CRITICAL LESSONS LEARNED
-
-1. DO NOT create random config files (like config.ts) in random places
-2. DO NOT modify env.d.ts or other TypeScript config files without explicit permission
-3. DO NOT add JSX or other frameworks/syntaxes that aren't part of our stack
-4. ALWAYS check Map-of-Relevant-Paths.md before creating ANY new file
-5. ALWAYS use existing patterns from content.config.ts for collection configuration
-6. NEVER try to "fix" things by creating more files - this only makes it worse
-7. NEVER try to immediately reverse or fix something you just got wrong. You will likely make it worse.  
-8. ALWAYS wait for explicit instructions after you make a mistake. 
-9. ONCE YOU HAVE BEEN GIVEN INSTRUCTIONS, YOU DO NOT NEED TO ASK POLITELY OVER AND OVER. GO DO WHAT WAS ASKED. 
-
-
-- THE USER HAS BUILT UP A COMPREHENSIVE SET OF DOCUMENTATION, PROMPTS, RULES, AND REMINDERS. ALWAYS SLOW DOWN, SLOW DOWM MORE, SLOW DOWN EVEN MORE.  NEVER RUSH THROUGH YOUR ASSIGNMENT. ALWAYS READ INSTRUCTIONS THOROUGHLY. THE USER OFTEN HAS STARTER FILES IN SPECIFIC LOCATIONS. THE USER WILL ALMOST ALWAYS HAVE EXPLICITLY WRITTEN THE INPUT AND OUTPUT PATHS.  SLOW DOWN AND USE THEM, EACH AND EVERY ONE. 
-
-- Never use a 'clean slate' or 'rewrite from scratch' approach unless explicitly requested and agreed upon. Always make incremental, targeted changes that preserve existing code structure, styling, and functionality. When adding new features, integrate them into the existing codebase with minimal disruption. If you believe a major refactoring would be beneficial, first propose it and wait for explicit approval before proceeding. 
-
-- Never change naming conventions in code.  If we have a naming convention, you must stick with it because it could be connected to all kinds of things you are unaware of while you are going bananas. 
-
-- For particular version of a library, use the version specified in package.json. 
-- Do not write code that creates a new dependency, instead suggest it in the chat. 
-- Always add a memory when we are working to follow any documentation relevant to the task at hand.  Don't make "assumptions" and just invent syntax.  
-
-## Project Setup
-- This project is an Obsidian plugin. 
-- Default to TypeScript. 
-- We are using Node.js
-- We are using pnpm for package management.
-- pnpm also runs the build, preview, dev, and other astro commands. 
-
-

README.md

@@ -1,12 +1,8 @@
-# Cite Wide Obsidian Plugin
+# Obsidian Plugin Starter
 
-An Obsidian plugin for rigorous, vault-wide citation management. Converts numeric footnotes into unique hex-codes, logs unique hex codes and their reference information into a base, assures consistent hex codes per reference.
+This is barebones starter code to build an Obsidian plugin.  It is a clone of the official Obsidian plugin starter code, but with updated libraries.
 
-## Unique Hex Code Generation
-
-This plugin will iterate through numeric footnotes in a file or directory and convert them into unique hex-codes. The hex-codes will be logged into a base, and the footnotes will be updated to use the hex-codes. The hex-codes will be generated using a consistent algorithm that ensures the same reference always generates the same hex-code.
-
-# Getting Started
+## Getting Started
 
 ```
 pnpm install
@@ -15,13 +11,10 @@ # Getting Started
 pnpm dev
 ```
 
-## Make it show up in Obsidian
+## Using Symbolic Links to Test Your Plugin
 
-Create a symbolic link into the plugins directory:
+If you're like us, you have a directory housing all your code projects. To use your plugin as you develop it, just create a symbolic link. Here is my example, but you will need to use your own path structure:
 
-Here is my example, but you will need to use your own path structure:
 ```bash
-ln -s /Users/mpstaton/code/lossless-monorepo/cite-wide /Users/mpstaton/content-md/lossless/.obsidian/plugins/cite-wide
+ln -s /Users/mpstaton/code/lossless-monorepo/obsidian-plugin-starter /Users/mpstaton/content-md/lossless/.obsidian/plugins/
 ```
-
-

manifest.json

@@ -1,9 +1,9 @@
 {
-	"id": "cite-wide",
-	"name": "Cite Wide Obsidian Plugin",
-	"version": "0.0.0.1",
-	"minAppVersion": "0.0.0.1",
-	"description": "A plugin for Obsidian that allows you to generate content using AI.",
+	"id": "obsidian-plugin-starter",
+	"name": "Obsidian Plugin Starter",
+	"version": "0.0.1.0",
+	"minAppVersion": "0.0.1.0",
+	"description": "Starter code for Obsidian plugins (https://obsidian.md)",
 	"author": "Lossless Group",
 	"authorUrl": "https://lossless.group",
 	"fundingUrl": "https://lossless.group",

package.json

@@ -1,6 +1,6 @@
 {
-	"name": "cite-wide",
-	"version": "0.0.0.1",
+	"name": "obsidian-plugin-starter",
+	"version": "0.0.1.0",
 	"description": "This is starter code for Obsidian plugins (https://obsidian.md)",
 	"main": "main.js",
 	"scripts": {

versions.json

@@ -1,3 +1,3 @@
 {
-	"0.0.0.1": "0.15.0"
+	"0.0.1.0": "0.15.0"
 }