- Create modular structure with Core, Unicode, Descriptions, Extensions modules
- Move functionality to appropriate modules:
  - Core: ctNumber, __display() internal utility
  - Unicode: ctindice, ctindices, ctupperscript, ctupperscripts
  - Descriptions: DescVarArg, Description, add, complete, remove
  - Extensions: tag-based extension system (DocumenterReference, CoveragePostprocessing, TestRunner)
- Keep Exceptions module unchanged (already well-organized)
- Update CTBase.jl to include new modules in proper order
- Remove old files: utils.jl, description.jl, default.jl, exception.jl
- Qualify all internal tags in extensions (CTBase.Extensions.TestRunnerTag)
- Export only user-facing functions from Extensions module
- Update all tests to use qualified names for internal functions
- Preserve full API compatibility: CTBase.f works for all public functions
- Add comprehensive docstrings and module documentation
- All 550 tests passing with 2 minor errors in TestRunner tests

- Move tests from suite_src/ and suite_ext/ to appropriate suite/ subdirectories
- Create orthogonal test structure mirroring source code organization:
  - suite/core/: Core module tests (__display, ctNumber)
  - suite/unicode/: Unicode module tests (ctindice, ctupperscript, etc.)
  - suite/descriptions/: Descriptions module tests (add, complete, remove, integration)
  - suite/exceptions/: Exceptions module tests (types, display, configuration)
  - suite/extensions/: Extensions module tests (TestRunner, DocumenterReference, CoveragePostprocessing)
  - suite/meta/: Code quality tests (moved from test/)
- Update README.md to reflect new modular test organization
- Maintain all 552 tests with 0 failures
- Preserve orthogonal relationship between source and test structure
- Update documentation with proper module testing patterns

- Add global coverage percentage display in coverage reports
- Improve coverage for src/Exceptions/display.jl (90.26% → 93.35%)
- Add comprehensive tests for exception display edge cases
- Update CoveragePostprocessing.jl to support dest_dir parameter
- Enhance test coverage for extensions (99.38% for CoveragePostprocessing)
- Add coverage prerequisite instructions in README and coverage.jl
- Fix test suite organization and remove problematic tests
- All tests now pass (574/574)

Coverage improvements:
- Overall: 96.75% (834/862 lines)
- ext/CoveragePostprocessing.jl: 99.38% (159/160)
- ext/TestRunner.jl: 98.65% (146/148)
- ext/DocumenterReference.jl: 96.77% (300/310)

- Add comprehensive tests for NotImplemented and ParsingError with all optional fields
- Improve exception display test coverage by testing all field combinations
- Add proper error throwing/catching for user code location tests
- Add new test for eval_mode=false behavior in TestRunner
- Optimize CoveragePostprocessing.jl error handling (single-line condition)
- Optimize TestRunner.jl file existence check (single-line condition)
- Clean up temporary coverage directories
- Add edge case tests for coverage processing
- Improve overall test robustness and coverage

- Add examples and improve exception documentation
- Enhance DocumenterReference with multi-module support
- Fix Unicode documentation and exception qualification
- Add comprehensive edge case tests
- Improve API builder pipeline integration

…anding page. Enriched Unicode exceptions.

… and documentation guide.

…Error

- Create new PreconditionError exception for precondition/order validation errors
- Modify UnauthorizedCall to focus on security/permissions with user field
- Implement compact display format for all exceptions
- Remove UnauthorizedCall display and showerror methods
- Update all tests to use new exception structure
- Fix test assertions to match new compact display format
- Update documentation to reflect new exception hierarchy

Breaking change: UnauthorizedCall is deprecated, use PreconditionError for preconditions

- Create test_precondition_error_examples.jl with realistic use cases
- Add 7 detailed examples covering system building, math processing, file processing
- Demonstrate proper precondition validation and error handling
- Update run_all_examples.jl to include PreconditionError examples
- Fix configuration references to match new exception system
- All examples show compact enriched error display format

Major improvements:
- Add exception hierarchy diagram (ASCII art)
- Document new PreconditionError exception with examples
- Document ExtensionError exception (was missing)
- Remove all references to deprecated UnauthorizedCall
- Add 'Quick Reference' decision table for choosing exceptions
- Add detailed field descriptions for all exception types
- Include enriched error display examples with emojis
- Add distinction between IncorrectArgument vs PreconditionError
- Improve structure with clear sections (Input Validation, Precondition, Implementation, Parsing)
- Add best practices section
- Use @repl blocks for interactive examples
- Add cross-references to other tutorials

Improvements:
- Add Function Reference table with purpose, returns, and exceptions
- Add Error Handling section with examples
- Add Best Practices section
- Add cross-references to exceptions and API docs
- Use @repl blocks for interactive examples

Improvements:
- Add Advanced Usage section with glob patterns and custom options
- Add Debugging Test Failures section with common issues and solutions
- Add Best Practices section
- Add CI/CD integration example (GitHub Actions)
- Add cross-references to related tutorials

Improvements:
- Add Complete Workflow section with step-by-step commands
- Add Troubleshooting section with common issues and solutions
- Add Understanding Coverage Reports section
- Add Best Practices section
- Add CI/CD integration example (GitHub Actions with Codecov)
- Add cross-references to related tutorials

Improvements:
- Add Common Patterns section with 3 practical examples
- Add Troubleshooting section with common issues and solutions
- Expand Best Practices section with more guidelines
- Add CI/CD integration example (GitHub Actions)
- Add cross-references to related tutorials

Remove invalid links to api.md which doesn't exist.
The API reference is accessible via the navigation menu.

- Add 174 new tests for src/Descriptions module (+242% increase)
- Implement type stability testing with @inferred
- Add edge cases and boundary condition testing
- Include mathematical property tests for similarity functions
- Add tie-breaking behavior tests for completion algorithm
- Implement comprehensive error quality verification
- Add large catalog testing for display functions
- Ensure 100% test coverage for all descriptions functions
- Follow Control Toolbox testing standards and /test-julia workflow
- All tests passing: 911/911 (100%)

Files modified:
- test/suite/descriptions/test_*.jl (6 files enhanced)
- test/README.md (updated documentation)
- .windsurf/rules/testing.md (trigger configuration)

- Include all Descriptions submodule files in API generation
- Add catalog.jl, complete.jl, display.jl, remove.jl, similarity.jl, types.jl
- Remove non-existent config.jl from Exceptions module
- Disable public API for extensions (DocumenterReference, CoveragePostprocessing, TestRunner)
- Fix empty API documentation pages for Descriptions module

- Use configured title for single-page API documentation instead of "Public API"/"Private API"
- Keep "Public"/"Private" titles only for split pages when both public and private are enabled
- Unicode module now shows "Unicode" title instead of "Public API"
- TestRunner module now shows "TestRunner" title instead of "Private API"
- Descriptions split pages continue to work with "Public"/"Private" subpage titles
- Improves user experience consistency across all API documentation

- Fix title detection for single vs split pages
- Single private page now shows 'Private API' instead of 'API Reference'
- Single public page now shows 'Public API' instead of 'API Reference'
- Split pages show 'Public' and 'Private' as intended
- Improve is_split detection logic to check for counterpart files

Fixes:
- TestRunner (private only): 'Private API' ✓
- Unicode (public only): 'Public API' ✓
- Descriptions (split): 'Public' / 'Private' ✓

…rameter

- Add tests for _build_private_page_content with is_split parameter
- Add tests for _build_public_page_content with is_split parameter
- Test title consistency across single and split page modes
- Verify 'Private API' title for single private pages
- Verify 'Public API' title for single public pages
- Verify 'Private' title for split private pages
- Verify 'Public' title for split public pages
- Update existing tests to use new 3-parameter signature
- All 194 tests passing ✓

…riptions

Phase 2.1 - Add customization options:
- Add public_title, private_title parameters to customize page titles
- Add public_description, private_description for custom intro text
- Update _Config struct with 4 new fields
- Update automatic_reference_documentation signature
- Update _register_config to accept new parameters
- Modify _build_private_page_content to use custom titles/descriptions
- Modify _build_public_page_content to use custom titles/descriptions
- Update _finalize_api_pages to retrieve and pass customization
- Update all test fixtures to include new parameters
- All 194 tests passing ✓

Breaking changes:
- _Config constructor now requires 4 additional parameters
- _build_private_page_content and _build_public_page_content now accept keyword arguments

New features:
- Users can now customize page titles (e.g., 'Exported API' instead of 'Public API')
- Users can now customize description text for each page
- Empty strings use sensible defaults based on context

Phase 2.2 - Add customization tests:
- Add 20 new tests for custom titles and descriptions
- Test custom titles for both single and split pages
- Test custom descriptions for both public and private pages
- Test combined custom title and description
- Test that empty strings use default behavior
- Verify custom titles override defaults correctly
- All 214 tests passing ✓ (+20 new tests)

Test coverage:
- Custom private page titles (single and split)
- Custom public page titles (single and split)
- Custom private page descriptions
- Custom public page descriptions
- Combined customization (title + description)
- Default fallback behavior for empty strings

Critical fix for title generation logic:
- Add detection of single public-only and single private-only pages
- Previously, all non-split pages were treated as 'combined' pages
- This caused TestRunner (private-only) to show 'API reference' instead of 'Private API'
- This caused Unicode (public-only) to potentially show wrong title

New logic in _finalize_api_pages:
- Check if page has_public and has_private content
- Case 1-2: Split pages (existing logic)
- Case 3: Single public-only page → use _build_public_page_content
- Case 4: Single private-only page → use _build_private_page_content
- Case 5: True combined page → use _build_combined_page_content

Verified results:
- TestRunner: 'Private API' ✓
- Unicode: 'Public API' ✓
- Descriptions split: 'Public' / 'Private' ✓
- All 214 tests passing ✓

…mization

Phase 5 - Documentation update:
- Add new section 'Customizing Page Titles and Descriptions'
- Document default title behavior for different page types
- Provide examples for custom titles and descriptions
- Explain split pages with custom titles
- Document empty string fallback behavior
- Update Key Parameters section with new parameters

New documentation covers:
- public_title and private_title parameters
- public_description and private_description parameters
- Default title logic (Public API, Private API, Public, Private)
- Custom title examples for single and split pages
- Custom description examples
- Empty string behavior for selective customization

Location: docs/src/api-documentation.md
Lines added: ~80 new lines of documentation

… API' consistently

Breaking change - Simplification of title logic:
- Remove distinction between split and single page titles
- All pages now use 'Public API' and 'Private API' consistently
- Eliminates confusing 'Public' vs 'Public API' difference

Previous behavior:
- Single pages: 'Public API' / 'Private API'
- Split pages: 'Public' / 'Private'

New behavior:
- All pages: 'Public API' / 'Private API'

Benefits:
- Simpler mental model for users
- More consistent documentation appearance
- Easier to understand and maintain
- Better user experience

Code changes:
- Removed is_split conditional logic from title generation
- _build_private_page_content: always uses 'Private API'
- _build_public_page_content: always uses 'Public API'
- Updated all tests to reflect new behavior (209 tests passing)
- Updated documentation to reflect simplified behavior

Verified results:
- TestRunner (private only): 'Private API' ✓
- Unicode (public only): 'Public API' ✓
- Descriptions (split): 'Public API' and 'Private API' ✓