apex-ruby 1.0.30 → 1.0.32

data/ext/apex_ext/apex_src/docs/PROGRESS.md

@@ -1,167 +0,0 @@
-# Apex Implementation Progress
-
-## Completed ✅ (9/17)
-
-### 1. Project Setup ✅
-- Repository structure with CMake
-- Git repository initialized
-- Build system working perfectly
-
-### 2. cmark-gfm Integration ✅
-- Parser integrated and working
-- AST manipulation functional
-- All GFM features operational
-
-### 3. Metadata Support ✅
-- YAML front matter parsing
-- MultiMarkdown metadata parsing
-- Pandoc title block parsing
-- `[%key]` variable replacement working
-
-### 4. Wiki Links ✅ **FIXED!**
-- `[[Page]]` syntax working
-- `[[Page|Display]]` format working
-- `[[Page#Section]]` anchors working
-- **Solution**: Postprocessing AST approach avoids conflict
-
-  with standard markdown
-
-- Tested with multiple links per line
-- Works alongside regular markdown links
-
-### 5. Math Support ✅ **FIXED!**
-- `$inline$` and `$$display$$` working
-- `\(inline\)` and `\[display\]` working
-
-**Fixed**: Dollar sign false positives (e.g., "$5 and $10")
-
-- Proper whitespace checking prevents false matches
-- Wraps in spans with classes for MathJax/KaTeX
-
-### 6. Definition Lists (header created)
-- Header file exists
-- Implementation deferred
-
-### 7. macOS Framework ✅
-- `Apex.framework` building successfully
-
-### 8. CLI Tool ✅
-- `apex` binary fully functional
-- All modes working
-
-### 9. Compatibility Modes ✅
-- CommonMark, GFM, MultiMarkdown, Kramdown, Unified modes
-
-  configured
-
-## In Progress 🔄 (0/17)
-
-*Ready for next feature*
-
-## Pending Features ⏳ (8/17)
-
-1. Definition Lists (header exists, needs implementation)
-2. Kramdown Attributes (`{: #id .class}`)
-3. Inline Footnotes (`^[text]`)
-4. Critic Markup (`{++add++}`, `{--del--}`, etc.)
-5. Enhanced Tables (MMD features)
-
-Marked Integration (Objective-C wrapper) - **HIGH PRIORITY**
-
-7. Test Suite
-8. Documentation & Release
-
-## Current Capabilities - UPDATED
-
-### ✅ Working Perfectly
-- Basic Markdown (headers, lists, emphasis)
-- GFM tables, strikethrough, task lists, autolinks
-- Metadata extraction (all 3 formats)
-- Metadata variable replacement `[%key]`
-- **Wiki links** `[[Page]]` with all variants ✨
-- **Math blocks** `$math$` and `$$display$$` ✨
-- Tag filtering (security)
-
-### ⏳ Not Yet Implemented
-- Definition lists
-- Kramdown attributes
-- Inline footnotes
-- Critic Markup
-- Callouts
-- TOC markers
-- File includes
-- Page breaks
-
-## Recent Wins 🎉
-
-**Session Progress:**
-
-- ✅ Identified and solved wiki links conflict
-
-  (postprocessing approach)
-
-✅ Fixed math dollar sign false positives (whitespace rules)
-
-- ✅ Both extensions now production-ready
-
-**Quality Improvements:**
-
-- Comprehensive issue documentation
-- Clean postprocessing implementation
-- Robust edge case handling
-
-## Next Recommended Steps
-
-**Immediate (High Value):**
-
-1. **Marked Integration** - Create Objective-C wrapper, get
-
-   Apex into Marked app
-
-2. **Critic Markup** - Widely used, relatively
-
-   straightforward inline syntax
-
-**Callouts** - Bear/Obsidian compatibility, high user value
-
-**Medium Term:**
-
-1. File includes (`<<[file]>>`) - Essential for Marked
-2. Basic test suite - Validate what we have
-3. Definition lists - Kramdown compatibility
-
-**Long Term:**
-
-1. Comprehensive test coverage
-2. Full documentation
-3. Release preparation
-
-## Statistics
-
-**Files**: ~20 source files
-**Lines of Code**: ~3,500 C code
-**Commits**: 13
-**Build Status**: ✅ Clean (only minor warnings)
-**Test Coverage**: Manual testing only (automated needed)
-
-## Completion Metrics
-
-**MVP Features**: 70% complete ⬆️
-**Production Ready**: 50% complete ⬆️
-**Fully Featured**: 45% complete ⬆️
-
-**Estimated Time to Production**: 1-2 months
-**Estimated Time to Full Feature Set**: 2-3 months
-
-## Key Achievements Today
-
-1. ✅ Solid foundation with cmark-gfm
-2. ✅ Metadata system fully working
-3. ✅ Wiki links solved and working
-4. ✅ Math support fixed and working
-5. ✅ Clean, maintainable architecture
-6. ✅ 9 of 17 major milestones complete (53%)
-
-**Status**: Apex is now at a solid foundation with core
-features working. Ready for Marked integration or additional
-syntax features.

data/ext/apex_ext/apex_src/docs/STANDALONE_FEATURE.md

@@ -1,174 +0,0 @@
-# Standalone HTML Document Output - NEW FEATURE
-
-## Overview
-
-Apex can now generate complete, self-contained HTML5
-documents with proper structure, metadata, and styling.
-
-## Usage
-
-### Basic Standalone Output
-
-```bash
-apex --standalone document.md
-# or shorthand:
-apex -s document.md
-
-```
-
-### With Custom Title
-
-```bash
-apex --standalone --title "My Report" report.md
-
-```
-
-### With External CSS
-
-```bash
-apex --standalone --style /path/to/styles.css document.md
-
-```
-
-### Combined Example
-
-```bash
-apex -s --title "Project Report" --style report.css report.md -o report.html
-
-```
-
-## Generated HTML Structure
-
-```html
-<!DOCTYPE html>
-<html lang="en">
-<head>
-  <meta charset="UTF-8">
-  <meta name="viewport" content="width=device-width, initial-scale=1.0">
-  <meta name="generator" content="Apex 0.1.0">
-  <title>Document Title</title>
-  
-  <!-- Either external CSS: -->
-  <link rel="stylesheet" href="styles.css">
-  
-  <!-- OR default inline styles -->
-  <style>
-    /* Responsive, modern styling */
-    body { font-family: system-ui; max-width: 800px; margin: 0 auto; }
-    /* ... more styles ... */
-  </style>
-</head>
-<body>
-
-  <!-- Your content here -->
-
-</body>
-</html>
-
-```
-
-## Default Styles
-
-When no `--style` is provided, Apex includes beautiful
-default inline styles:
-
-### Typography
-- Modern system font stack (`-apple-system`,
-
-  `BlinkMacSystemFont`, `Segoe UI`, etc.)
-
-- Readable line-height (1.6)
-- Clean color scheme (#333 on white)
-
-### Layout
-- Responsive centered layout
-- Max-width: 800px
-- Comfortable margins and padding
-- Mobile-friendly viewport
-
-### Element Styling
-**Code blocks**: Light gray background, horizontal scrolling
-
-- **Inline code**: Rounded corners, subtle background
-- **Blockquotes**: Left border, indented, muted color
-- **Tables**: Bordered cells, header row styling
-- **Callouts**: Colored borders and backgrounds (note,
-
-  warning, tip, danger)
-
-- **Page breaks**: Print-friendly styling
-
-## Use Cases
-
-### Documentation Sites
-```bash
-apex -s --title "API Docs" --style docs.css api.md -o index.html
-
-```
-
-### Reports
-```bash
-apex -s --title "Q4 Report" --style corporate.css report.md -o report.html
-
-```
-
-### Blog Posts
-```bash
-apex -s --title "My Post" --style blog.css post.md -o post.html
-
-```
-
-### Quick Previews
-```bash
-# No CSS needed - beautiful defaults
-apex -s document.md > preview.html
-open preview.html
-
-```
-
-### Email HTML
-```bash
-# Inline styles work great for email
-apex -s --title "Newsletter" newsletter.md > email.html
-
-```
-
-## Fragment Mode (Default)
-
-Without `--standalone`, Apex generates HTML fragments (body
-content only):
-
-```bash
-apex document.md  # Just the content, no <html> wrapper
-
-```
-
-This is useful for:
-
-- CMS integration
-- Template systems
-- AJAX content
-- Partial views
-
-## Options Summary
-
-| Option | Description | Implies |
-|--------|-------------|---------|
-| `-s`, `--standalone` | Generate complete HTML document | -
-|
-| `--title TITLE` | Set document title | - |
-| `--style FILE` | Link external CSS | `--standalone` |
-
-**Note**: Using `--style` automatically enables `--standalone` mode.
-
-## Test Coverage
-
-✓ 14 tests covering standalone output
-✓ Doctype and HTML structure
-✓ Meta tags (charset, viewport, generator)
-✓ Title handling (custom and default)
-✓ CSS linking
-✓ Default inline styles
-✓ Fragment mode preserved
-
-All 152 tests passing!

data/ext/apex_ext/apex_src/docs/TABLE_SPANS_STATUS.md

@@ -1,243 +0,0 @@
-# Table Span Processing - Current Status
-
-## Working Features ✅
-
-### Rowspan (`^^` markers)
-
-**Fully functional** - All rowspan scenarios work correctly:
-
-```markdown
-| Name  | Dept |
-|-------|------|
-| Alice | Eng  |
-| ^^    | ^^   |
-| ^^    | ^^   |
-
-```
-
-Output:
-
-```html
-<td rowspan="3">Alice</td>
-<td rowspan="3">Eng</td>
-
-```
-
-**Features:**
-
-- Supports 1-N consecutive `^^` rows
-- Properly removes all `^^` cells from output
-- Walks backwards through rows to find original cell
-- Skips header rows from rowspan processing
-- No literal `^^` appears in HTML
-
-### Colspan (Empty Cells)
-
-**Functional with caveats** - Empty cells merge with
-previous non-empty cell:
-
-```markdown
-| H1 | H2 | H3 |
-|----|----|----|
-| A  | B  | C  |
-| Span 3   |    |    |
-
-```
-
-Output:
-
-```html
-<td colspan="3">Span 3</td>
-
-```
-
-**Features:**
-
-- Supports 1-N consecutive empty cells
-- Walks backwards to find original non-empty cell
-- Removes all empty cells from output
-
-Multiple tables process independently (table index tracking)
-
-## Known Behavior Notes ⚠️
-
-### Empty Cell Detection
-
-Our `is_colspan_cell()` function treats cells as "empty" if
-they contain:
-
-1. **No content** - Truly empty cell
-2. **Only whitespace** - Spaces, tabs, newlines
-3. **`<<` marker** - (future: link to previous cell content)
-
-This means:
-
-- `| Content |      |` → `<td colspan="2">Content</td>`
-- `| Content |  ` → Same (trailing spaces count as empty)
-- `| ✅ | ❌ |` → No colspan (emoji are content)
-
-### Header Row Behavior
-
-Currently header rows can participate in colspan if they
-have empty cells:
-
-```markdown
-| Header 1 | Header 2 |          |
-|----------|----------|----------|
-| A        | B        | C        |
-
-```
-
-Output: `<th colspan="2">Header 2</th>`
-
-**Recommendation**: This is generally undesirable. Headers
-should not span.
-
-**Fix needed**: Extend the `is_first_row` skip logic to
-colspan processing.
-
-## Comprehensive Test Results
-
-### Test Document
-
-The `tests/comprehensive_test.md` (617 lines, 2,360 words) exercises all features.
-
-### Basic Table Rendering
-
-The "Basic Table" in comprehensive_test.md shows some
-unexpected colspan attributes:
-
-| Issue | Location | Cause |
-|-------|----------|-------|
-| `colspan="2"` on Tables row, MMD column | Row 3, Col 3-4 |
-Unclear - needs investigation |
-| `rowspan="3"` on Footnotes row, GFM column | Row 4, Col 2
-| Unclear - needs investigation |
-| `colspan="2"` on Metadata row | Row 6, Col 2-3 | Unclear -
-needs investigation |
-
-**These DO NOT appear when the same table is tested in
-isolation**, suggesting:
-
-1. Table index tracking may have an edge case
-2. Some preprocessing step might be modifying the markdown
-3. The markdown source itself may have subtle issues
-
-   (trailing spaces, etc.)
-
-## Testing Recommendations
-
-### For Best Results
-
-**Use well-formed tables** - Ensure columns align properly
-
-2. **Avoid empty cells in headers** - Fill all header cells
-
-   with content
-
-3. **Test in isolation** - If seeing unexpected spans,
-
-   extract the table to a separate file
-
-4. **Check markdown source** - Use `cat -A` to reveal hidden
-
-   whitespace
-
-### Test Cases That Work
-
-```bash
-# Rowspan (3 rows)
-./build/apex /tmp/rowspan_test.md
-
-# Colspan (3 columns)
-./build/apex /tmp/colspan_test.md
-
-# Multiple independent tables
-./build/apex /tmp/multi_table_test.md
-
-```
-
-## Implementation Details
-
-### Processing Pipeline
-
-1. **AST Processing** (`advanced_tables.c`):
-
-`process_table_spans()` called per table during postprocessing
-
-   - Sets `user_data` on cells with `colspan="N"`,
-
-     `rowspan="N"`, or `data-remove="true"`
-
-   - Skips first row (header) from span processing
-
-2. **HTML Postprocessing** (`table_html_postprocess.c`):
-
-`collect_table_cell_attributes()` walks entire AST, collecting (table_idx, row_idx, col_idx, attrs)
-
-`apex_inject_table_attributes()` walks HTML string, matching cells by indices
-
-   - Injects span attributes or removes cells marked with
-
-     `data-remove`
-
-### Index Tracking
-
-Both AST walker and HTML walker must maintain synchronized
-indices:
-
-- **table_index**: Increments for each `<table>` /
-
-  `CMARK_NODE_TABLE`
-
-**row_index**: Increments for each `<tr>` / `CMARK_NODE_TABLE_ROW`, resets per table
-
-**col_index**: Increments for each `<td>`/`<th>` / `CMARK_NODE_TABLE_CELL`, resets per row
-
-## Next Steps
-
-### To Fix Header Colspan Issue
-
-Modify `process_table_spans()` to track and skip header row for BOTH colspan and rowspan.
-
-### To Debug Comprehensive Test Issues
-
-1. Add debug logging to show table_index, row_index,
-
-   col_index for each cell
-
-2. Compare AST indices vs HTML indices
-3. Check if preprocessing steps modify table structure
-
-## Performance Impact
-
-Table span processing adds ~1-2ms to overall processing time
-
-- No impact on tables without spans
-- Scales linearly with number of spanned cells
-
-## Conclusion
-
-**Status**: Production-ready for most use cases
-
-**Strengths**:
-
-- Rowspan fully working (1-N consecutive rows)
-- Colspan fully working (1-N consecutive columns)
-- Multiple tables handled independently
-- All 190 tests passing
-
-**Minor Issues**:
-
-- Headers can get colspan (fixable)
-- Some edge cases in complex documents (needs investigation)
-
-**Recommendation**: Safe to use with properly formatted
-markdown tables. Issues only appear in edge cases with
-malformed input.
-
----
-
-*Last Updated: 2025-12-05*
-*Apex Version: 0.1.0*
-