neon_sakura 0.1.4

data/config/brakeman.ignore

@@ -0,0 +1,28 @@
+{
+  "ignored_warnings": [
+    {
+      "warning_type": "Cross-Site Request Forgery",
+      "warning_code": 86,
+      "fingerprint": "811fccd4f1d716b6b7a6467653259cdfe25de28e0c24d729729f6bc78670da05",
+      "check_name": "ForgerySetting",
+      "message": "`protect_from_forgery` should be configured with `with: :exception`",
+      "file": "app/controllers/errors_controller.rb",
+      "line": 11,
+      "link": "https://brakemanscanner.org/docs/warning_types/cross-site_request_forgery/",
+      "code": "protect_from_forgery(:with => :null_session)",
+      "render_path": null,
+      "location": {
+        "type": "controller",
+        "controller": "ErrorsController"
+      },
+      "user_input": null,
+      "confidence": "Medium",
+      "cwe_id": [
+        352
+      ],
+      "note": "Error pages don't have forms to submit, so :null_session is appropriate for CSRF protection"
+    }
+  ],
+  "updated": "2025-12-10 00:00:00 +0000",
+  "brakeman_version": "7.1.1"
+}

data/config/initializers/neon_sakura.rb

@@ -0,0 +1,15 @@
+# Configure Neon Sakura gem
+# This file should be placed in config/initializers/neon_sakura.rb
+
+require "pagy"
+
+# Configure default values
+NeonSakura.configure do |config|
+  config.app_name = "My Application"
+  config.show_version = true
+  config.show_header = true
+  config.nav_links = [
+    { name: "Home", path: "/" },
+    { name: "About", path: "/about" }
+  ]
+end

data/config/license_overrides.yml

@@ -0,0 +1,13 @@
+# License Override Configuration
+# This file allows manual approval of gems with problematic or unknown licenses
+# Use this for gems that have been manually verified as safe for commercial use
+
+# Gems with licenses that have been manually verified as commercial-friendly
+approved_gems:
+  bundler-audit: "GPL-3 allows commercial use"
+
+# Notes:
+# - Each entry should include the reason for approval
+# - Review these periodically when updating gems
+# - Remove entries when gems are updated with proper license metadata
+# - Consider contributing license fixes back to upstream gems

data/config/routes.rb

@@ -0,0 +1,21 @@
+# frozen_string_literal: true
+
+NeonSakura::Engine.routes.draw do
+  # Error routes - only if enabled in configuration
+  if NeonSakura.configuration.enable_error_pages
+    get "/400", to: "errors#bad_request", as: :bad_request
+    get "/401", to: "errors#unauthorized", as: :unauthorized
+    get "/403", to: "errors#forbidden", as: :forbidden
+    get "/404", to: "errors#not_found", as: :not_found
+    get "/406", to: "errors#not_acceptable", as: :not_acceptable
+    get "/422", to: "errors#unprocessable_entity", as: :unprocessable_entity
+    get "/500", to: "errors#internal_server_error", as: :internal_server_error
+    get "/503", to: "errors#service_unavailable", as: :service_unavailable
+  end
+
+  # Style guide route - only if enabled AND in development/test environment
+  # Route is NOT defined in production (returns Rails 404)
+  if NeonSakura.configuration.enable_style_guide && (Rails.env.development? || Rails.env.test?)
+    get "/style-guide", to: "style_guide#index", as: :style_guide
+  end
+end

data/config/theme_mappings.yml

@@ -0,0 +1,61 @@
+# Theme Mappings for External CSS Frameworks
+# Maps framework-specific color variables to neon_sakura CSS custom properties
+
+# Bootstrap 5 Theme Mapping
+bootstrap:
+  primary: --color-accent
+  secondary: --color-text-secondary
+  success: --color-notification
+  danger: --color-alert
+  warning: --color-warning
+  info: --color-info
+  light: --color-surface
+  dark: --color-background-dark
+  body-bg: --color-background
+  body-color: --color-text-primary
+  border-color: --color-border
+  link-color: --color-accent
+  link-hover-color: --color-accent-hover
+
+# Material UI Theme Mapping
+material_ui:
+  palette.primary.main: --color-accent
+  palette.primary.light: --color-accent-light
+  palette.primary.dark: --color-accent-dark
+  palette.secondary.main: --color-text-secondary
+  palette.background.default: --color-background
+  palette.background.paper: --color-surface
+  palette.text.primary: --color-text-primary
+  palette.text.secondary: --color-text-secondary
+  palette.text.disabled: --color-text-muted
+  palette.success.main: --color-notification
+  palette.error.main: --color-alert
+  palette.divider: --color-border
+
+# Tailwind CSS Theme Mapping
+tailwind:
+  # Primary colors
+  gray-900: --color-background-dark
+  gray-800: --color-surface-dark
+  gray-700: --color-border
+  gray-600: --color-text-secondary
+  gray-50: --color-background-light
+  white: --color-background
+
+  # Accent colors (customize based on theme)
+  blue-500: --color-accent
+  blue-600: --color-accent-dark
+  green-500: --color-notification
+  red-500: --color-alert
+
+# Custom Theme Structure
+# Use this as a template for creating custom themes
+custom:
+  accent: --color-accent
+  background: --color-background
+  surface: --color-surface
+  text: --color-text-primary
+  text-muted: --color-text-muted
+  success: --color-notification
+  error: --color-alert
+  border: --color-border

data/docs/PRYSM_ASSETS.md

@@ -0,0 +1,210 @@
+# Prys-m Assets Catalog
+
+Assets extracted from the Prys-m application for use in Neon Sakura.
+
+## SVG Assets
+
+### Application Icons
+
+#### prysm-icon.svg
+- **Source**: `/public/icon.svg`
+- **Description**: Main application icon featuring a magazine/document design
+- **Colors**:
+  - Accent Green: `#009990` (Persian green)
+  - Text Gray: `#545E75` (Payne's gray)
+  - Alert Red: `#DE5959` (Chestnut)
+  - White: `#ffffff`
+- **Design**: Layered magazine pages with content lines and bookmark
+- **Dimensions**: 512x512
+- **Features**: Gradient background, rounded corners (rx="64")
+
+### Third-Party Service Icons
+
+#### pushbullet-1.svg
+- **Source**: `/app/assets/images/pushbullet-1.svg`
+- **Description**: Pushbullet logo (colored version)
+- **Colors**: Green gradient (#67BF79, #4CB36B to #3EA16F)
+- **Dimensions**: 256x256
+- **Design**: Circle badge with "P!" branding
+
+#### pushbullet-2.svg
+- **Source**: `/app/assets/images/pushbullet-2.svg`
+- **Description**: Pushbullet logo (simple stroke version)
+- **Colors**: Black stroke (#000000)
+- **Dimensions**: 192x192
+- **Design**: Minimalist outline version of "P!" branding
+
+## PNG Assets
+
+#### prysm-icon.png
+- **Source**: `/public/icon.png`
+- **Description**: Raster version of the main application icon
+- **Format**: PNG
+- **Use Case**: Fallback for environments that don't support SVG
+
+## Font Awesome Icons Used
+
+The Prys-m application extensively uses Font Awesome 6.5.1 icons. Below is a comprehensive list of all icons used:
+
+### Navigation & UI
+- `fa-bars` - Menu toggle
+- `fa-arrow-left` - Back navigation
+- `fa-times` - Close/dismiss
+- `fa-search` - Search functionality
+- `fa-filter` - Filter controls
+- `fa-filter-circle-xmark` - Clear filters
+- `fa-cog` / `fa-cogs` - Settings
+- `fa-expand-arrows-alt` - Expand/fullscreen
+
+### User & Authentication
+- `fa-user` - User profile
+- `fa-user-circle` - User avatar
+- `fa-user-plus` - Add user
+- `fa-sign-in-alt` - Login
+- `fa-sign-out-alt` - Logout
+- `fa-key` - API keys/credentials
+- `fa-lock` / `fa-unlock` - Security status
+- `fa-crown` - Premium/admin status
+- `fa-shield-alt` - Security features
+
+### Content & Actions
+- `fa-bookmark` - Bookmarked items
+- `fa-heart` - Favorites
+- `fa-heart-broken` - Unfavorite
+- `fa-star` - Featured/starred
+- `fa-archive` - Archived items
+- `fa-trash` - Delete
+- `fa-edit` - Edit
+- `fa-copy` - Copy/duplicate
+- `fa-save` - Save
+- `fa-check` / `fa-check-circle` - Success/completed
+- `fa-plus` - Add new
+- `fa-undo` / `fa-redo` - Undo/redo
+
+### Import & Export
+- `fa-file-import` - Import data
+- `fa-file-export` - Export data
+- `fa-file-csv` - CSV export
+- `fa-cloud-upload-alt` - Upload
+- `fa-upload` - Upload files
+- `fa-download` - Download
+- `fa-inbox` - Inbox/unread items
+- `fa-get-pocket` - Pocket integration
+
+### Tools & Features
+- `fa-receipt` - Receipt processing
+- `fa-qrcode` - QR code generator
+- `fa-image` / `fa-file-image` - Image tools
+- `fa-crop` - Image cropping
+- `fa-palette` - Color/theme tools
+- `fa-magic` - AI/auto features
+- `fa-brain` - AI processing
+- `fa-tools` - Tool collection
+- `fa-eraser` - Clear/reset
+- `fa-adjust` - Image adjustments
+
+### Organization
+- `fa-folder` / `fa-folder-open` - Collections
+- `fa-folder-plus` - New collection
+- `fa-tag` / `fa-tags` - Tags
+- `fa-layer-group` - Groups/categories
+- `fa-table` - Table view
+- `fa-list` - List view
+
+### Information & Status
+- `fa-info-circle` - Information
+- `fa-question-circle` - Help
+- `fa-exclamation-circle` - Warning
+- `fa-exclamation-triangle` - Alert
+- `fa-bell` / `fa-bell-exclamation` - Notifications
+- `fa-spinner` / `fa-spin` - Loading
+- `fa-clock` - Time/history
+- `fa-history` - History
+- `fa-calendar` / `fa-calendar-alt` - Date/schedule
+
+### Analytics & Stats
+- `fa-chart-bar` - Bar charts
+- `fa-chart-line` - Line charts
+- `fa-chart-pie` - Pie charts
+- `fa-user-stats` - User statistics
+
+### Social & Sharing
+- `fa-share-alt` - Share
+- `fa-external-link-alt` - External link
+- `fa-paper-plane` - Send/submit
+- `fa-envelope` - Email
+- `fa-rss` - RSS feed
+- `fa-globe` - Public/web
+
+### Theme & Display
+- `fa-sun` / `fa-moon` - Light/dark mode toggle
+- `fa-lightbulb` - Ideas/tips
+- `fa-eye` - View/preview
+- `fa-search-plus` / `fa-search-minus` - Zoom controls
+
+### Misc
+- `fa-magazine` - Magazine view style
+- `fa-book` - Documentation
+- `fa-store` - Marketplace/shop
+- `fa-rocket` - Launch/deploy
+- `fa-puzzle-piece` - Plugins/extensions
+- `fa-network-wired` - Integrations
+- `fa-mobile-alt` - Mobile devices
+- `fa-camera` - Camera capture
+- `fa-file-alt` - Documents
+- `fa-play` - Start/run
+- `fa-sync` - Refresh/sync
+- `fa-google` - Google integration
+
+## Color Palette
+
+The Prys-m application uses a consistent color scheme:
+
+- **Primary Text**: `#545E75` (Payne's gray)
+- **Accent Color**: `#009990` (Persian green)
+- **Alert Color**: `#DE5959` (Chestnut)
+- **Background**: `#FFFFFF` (White) / `#0f172a` (Dark mode)
+- **Bold Text**: `#000000` (Black) / `#f8fafc` (Dark mode)
+
+## Typography
+
+- **Primary Font**: Montserrat (sans-serif) - Headings, navigation, UI elements
+- **Secondary Font**: Source Serif 4 (serif) - Article content, body text
+
+## Integration with Neon Sakura
+
+When Prys-m is used as part of the Neon Sakura application:
+
+1. Replace custom SVG icons with Neon Sakura icon system
+2. Unify Font Awesome icon usage across applications
+3. Sync color palettes and theming
+4. Consolidate typography choices
+5. Share image processing utilities
+
+## File Locations
+
+All Prys-m assets are now integrated into the main Neon Sakura asset structure:
+
+```
+neon_sakura/
+├── docs/
+│   └── PRYSM_ASSETS.md (this file)
+└── app/
+    └── assets/
+        └── images/
+            ├── prysm-icon.svg
+            ├── prysm-icon.png
+            ├── pushbullet-1.svg
+            └── pushbullet-2.svg
+```
+
+## Notes
+
+- All SVG files use viewBox for responsive scaling
+- Icons maintain accessibility through proper semantic markup
+- Color values can be customized via CSS variables
+- Font Awesome version: 6.5.1
+
+## License
+
+Assets extracted from Prys-m application. Refer to source repository for licensing information.

data/docs/plans/extract_ai_reviewer_plan.md

@@ -0,0 +1,151 @@
+Below is a concise “recipe” for pulling the Neon Sakura AI‑reviewer pipeline out into its own
+  repository and wiring it up in any number of downstream projects.
+
+  ---
+  1. What files are involved in the current repo?
+
+  | Directory          | What it holds
+                                | Why it matters                             |
+  |--------------------|-------------------------------------------------------------------------
+  ------------------------------|--------------------------------------------|
+  | .github/workflows/ | GitHub Actions YAMLs that run RuboCop, Brakeman, the AI‑reviewer, etc.
+                                | These are what actually execute in CI.     |
+  | .ai‑reviewer/      | Bash/Ruby scripts that orchestrate the AI‑review – e.g. token‑counting,
+  API calls, result formatting. | Core logic that can be reused.             |
+  | bin/               | Wrapper scripts that may call the reviewer or run pre‑commit / pre‑push
+  hooks.                        | These are the entry points for developers. |
+
+  ---
+  2. Turn it into a reusable GitHub Action
+
+  a. Create a new repo
+
+  - ai-reviewer-action (or similar) – a public or private GitHub org/repo.
+
+  b. Re‑organise the source
+
+  ai-reviewer-action/
+  ├─ action.yml          # composite action metadata
+  ├─ scripts/
+  │   ├─ run-review.sh   # entry script
+  │   └─ …               # copy everything from .ai‑reviewer/
+  └─ tests/ (optional)  # small test harness for the composite action
+
+  *Move the contents of .ai‑reviewer/ into scripts/ and make the bash file executable (chmod +x).
+  If the reviewer was written in Ruby, you can keep the Ruby files in scripts/ and invoke them
+  from the shell script.
+
+  c. Define the composite action
+
+  # action.yml
+  name: "Neon Sakura AI Reviewer"
+  description: "Runs RuboCop/Brakeman and the AI‑review pipeline."
+  branding:
+    icon: "shield"
+    color: "purple"
+  inputs:
+    repo-token:
+      description: "GitHub token for API access"
+      required: true
+  runs:
+    using: "composite"
+    steps:
+      - name: Checkout repo
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Set up Ruby
+        uses: ruby/setup-ruby@v1
+        with: { ruby-version: 3.3 }
+
+      - name: Install deps
+        run: bundle install --jobs 4
+
+      - name: Run RuboCop
+        run: bundle exec rubocop
+
+      - name: Run Brakeman
+        run: bundle exec brakeman --quiet
+
+      - name: Run AI review
+        env:
+          GH_TOKEN: ${{ inputs.repo-token }}
+        run: |
+          bash scripts/run-review.sh
+
+  The run-review.sh script should be a thin wrapper around whatever logic lives in the old
+  .ai‑reviewer/ folder. Pass any environment vars you need (API keys, etc.) from the calling
+  workflow.
+
+  ---
+  3. Create a reusable CI workflow that calls the action
+
+  Place the following in any repo that should use the AI‑reviewer:
+
+  name: 🐛 AI‑Reviewer
+
+  on:
+    pull_request:
+      branches: [main]
+    workflow_dispatch:   # Manual trigger if desired
+
+  jobs:
+    review:
+      permissions:
+        contents: read          # needed for checkout
+        issues: write           # optional, if you want to comment
+      uses: org/ai-reviewer-action/.github/workflows/review.yml@v1
+      secrets:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}  # for GitHub API calls
+        AI_API_KEY: ${{ secrets.AI_API_KEY }}      # your LLM key
+
+  Inside the reusable workflow (.github/workflows/review.yml) you would simply forward the
+  repo-token input to the action:
+
+  jobs:
+    run:
+      uses: org/ai-reviewer-action@v1
+      secrets:
+        repo-token: ${{ github.token }}
+
+  When the repo’s PR or push triggers the workflow, GitHub will fetch the ai-reviewer-action
+  repo, execute action.yml, and run the composite steps. All downstream projects just need to
+  depend on a tag (e.g. v1, v2) or branch that contains the action.
+
+  ---
+  4. Optional: Turn the scripts into a tiny CLI
+
+  If you prefer to run the reviewer locally or in CI scripts, consider packaging bin/ai-reviewer
+  as a Ruby gem or a simple Docker container that exposes the same shell script. Keep the source
+  in ai-reviewer-action/cli/ and build a lightweight image that can be pushed to GitHub Container
+   Registry. Down‑stream repos can then call:
+
+  - name: Run AI reviewer
+    run: docker run --rm -e TOKEN=$AI_API_KEY ghcr.io/yourorg/ai-reviewer:latest
+
+  ---
+  5. Documentation & publishing
+
+  1. README – explain the action, inputs, outputs, required secrets.
+  2. Action badges – action.yml generates
+  https://github.com/org/ai-reviewer-action/workflows/Release/badge.svg.
+  3. Release workflow – Tag releases with semantic versioning (e.g. v1.0.0). Use git tag -a
+  v1.0.0 -m "Initial public release" && git push --tags.
+  4. GitHub Template – If you foresee many repos needing the same setup, create a template
+  repository in GitHub. Each new project can copy from it.
+
+  ---
+  Quick checklist
+
+  - Move .ai‑reviewer/ → ai-reviewer-action/scripts/
+  - Convert scripts to a composite action.yml
+  - Publish the action in a separate org/repo
+  - Add a reusable workflow that references the action
+  - Update downstream projects to use the reusable workflow (uses:)
+  - Add documentation and badges
+
+  With this structure, every project that wants the same AI‑reviewer logic just pulls a single
+  action and any future changes—bug fixes, new LLM providers, or workflow tweaks—are propagated
+  by bumping the action’s tag. No matter how many repos you own, you deploy the CI logic once,
+  keep it under version control, and reuse it everywhere.

data/docs/plans/neon_sakura_gem_plan.md

@@ -0,0 +1,138 @@
+# Plan: Extract Styling and Theming Components into `neon_sakura` Gem
+
+## Overview
+This document outlines the approach for extracting the styling and theming components from the Artemis Rails application into a separate `neon_sakura` gem that can be reused across multiple Rails projects.
+
+## Analyzed Components
+
+### Core CSS Structure
+Based on my analysis, the application uses a modular CSS approach with the following files:
+- `app/assets/stylesheets/application.css` - Main manifest file
+- `app/assets/stylesheets/base.css` - Core utility classes (713 lines)
+- `app/assets/stylesheets/components.css` - UI components (278 lines)
+- `app/assets/stylesheets/forms.css` - Form styling (87 lines)
+- `app/assets/stylesheets/pagy-tailwind.css` - Pagination styles (65 lines)
+
+### Layout Components
+- `app/views/layouts/mission_control/jobs/application.html.erb` - Mission Control layout with custom dropdown JavaScript
+- `app/views/layouts/error.html.erb` - Error page layout
+- `app/views/shared/_footer.html.erb` - Site footer component
+- `app/views/shared/icons/*.html.erb` - SVG icon components
+
+### Authentication Views
+- `app/views/devise/sessions/new.html.erb` - Login form with dark theme styling
+
+## Components to Extract
+
+### 1. CSS Stylesheets
+- All CSS files from `app/assets/stylesheets/`
+- `base.css` - Core utilities, layout, typography, colors, responsive utilities
+- `components.css` - UI components (navigation, cards, badges, buttons, tables, alerts)
+- `forms.css` - Form element styling
+- `pagy-tailwind.css` - Pagination styles
+
+### 2. Layout Templates
+- `app/views/layouts/mission_control/jobs/application.html.erb` - Mission Control layout
+- `app/views/layouts/error.html.erb` - Error page layout
+
+### 3. View Components
+- `app/views/shared/icons/` - All SVG icon partials (29 files)
+- `app/views/shared/_footer.html.erb` - Site footer
+
+### 4. JavaScript Components (if needed)
+- Mission Control dropdown JavaScript from layout (vanilla JS, not Stimulus)
+- May need to preserve it in a separate JS file
+
+## Implementation Approach
+
+### Step 1: Create Gem Structure
+```
+neon_sakura/
+├── lib/
+│   ├── neon_sakura/
+│   │   ├── version.rb
+│   │   └── engine.rb
+│   └── neon_sakura.rb
+├── app/
+│   ├── assets/
+│   │   ├── stylesheets/
+│   │   │   ├── application.css
+│   │   │   ├── base.css
+│   │   │   ├── components.css
+│   │   │   ├── forms.css
+│   │   │   └── pagy-tailwind.css
+│   │   └── javascripts/
+│   │       └── neon_sakura/
+│   │           └── dropdown.js
+│   └── views/
+│       └── shared/
+│           └── icons/
+├── neon_sakura.gemspec
+├── Gemfile
+├── Rakefile
+└── README.md
+```
+
+### Step 2: Extract CSS Files
+- Copy all CSS files to gem's `app/assets/stylesheets/`
+- Update `application.css` to `@import` the extracted files
+- Update import paths for proper gem resolution
+
+### Step 3: Extract Layouts and Partials
+- Extract the layout templates to gem's `app/views/layouts/`
+- Extract icon components to gem's `app/views/shared/icons/`
+- Extract footer component to gem's `app/views/shared/`
+
+### Step 4: JavaScript Components
+- Place dropdown JavaScript in `app/assets/javascripts/neon_sakura/dropdown.js`
+- Ensure proper dependency management
+
+### Step 5: Gem Configuration
+- Create gemspec with proper metadata
+- Implement Rails engine to integrate with host application
+- Handle asset precompilation properly
+
+### Step 6: Usage in Host Application
+1. Add gem to Gemfile: `gem 'neon_sakura'`
+2. Configure asset pipeline in host app
+3. Include the gem's assets in application layout
+4. Use gem-provided layouts and components
+
+### Step 7: Documentation
+- Create comprehensive README
+- Document usage and configuration options
+- Include examples of how to customize theme
+
+## Key Considerations
+
+### Asset Precompilation
+- The gem's assets should be precompilable for production
+- Maintain proper CSS import order for style inheritance
+- Ensure proper handling of digest paths in production
+
+### Layout Integration
+- Mission Control layout has no Stimulus controllers, so it should work with vanilla JS
+- Error layout should work directly without modification
+- Footer and icons should integrate seamlessly
+
+### Customization
+- Allow for theme overrides in host applications
+- Document how to customize design system
+- Support for multiple themes if needed
+
+### File Structure Migration
+- Must maintain backwards compatibility where possible
+- Host application should be able to override gem components
+- Proper handling of relative paths in different environments
+
+## Dependencies
+- Rails 8+
+- Propshaft asset pipeline
+- Modern browsers for CSS features used
+
+## Benefits
+1. Reusability across multiple projects
+2. Consistent theming across applications
+3. Easier maintenance of shared styling components
+4. Better separation of concerns
+5. Version control and deployment of theme components