…and fixes

…and fixex

* chore: smaller improvements

* fix(config): read profiles via CLI as well

* fix(config): implement comprehensive profile loading from all sources

Resolves config loading limitations where profiles were only read from
application.properties, preventing flexible configuration in deployment environments.

**Core Changes:**
- Simplified profile resolution logic in NanoUtils.readProfiles() (70→25 lines)
- Fixed profile loading order: app_profile → CONFIG_PROFILES → spring → micronaut → generic
- Removed complex Spring external detection logic from NanoBase.java
- Added proper CLI args and system properties profile support

**Framework Compatibility:**
- ✅ Spring: spring.profiles.active, spring_profiles_active
- ✅ Micronaut: micronaut.environments, micronaut_profiles
- ✅ Generic: profiles.active, profiles_active
- ✅ Nano: app.profiles, app_profiles, app.profile

**Testing Improvements:**
- Added @execution(ExecutionMode.SAME_THREAD) to prevent test race conditions
- Expanded test coverage from 6 to 10 tests with comprehensive edge cases
- Removed text block syntax incompatible with older Java versions
- Enhanced test isolation and cleanup procedures

**Precedence Order (Now Working):**
CLI args > System Properties > Environment Variables > Config Files

**Verified Fix:**
- ✅ `export SPRING_PROFILES_ACTIVE=dev,prod` now works
- ✅ `--app.profiles=local,staging` now works
- ✅ `-Dspring.profiles.active=test` now works
- ✅ Mixed sources with correct priority now work

Closes: Profile loading from external sources not supported
Tests: 10/10 config tests passing, all main tests passing
* chore(tests): improve test reliability and code formatting

**Test Improvements:**
- Removed unused SHORT_AWAIT_MS constant from NanoSchedulerTest
- Standardized timeout usage to TEST_TIMEOUT for consistency
- Fixed indentation and formatting in NanoTest
- Moved configFilesTest from NanoTest to NanoConfigLoadingTest (better organization)
- Removed unused imports and variables

**Code Quality:**
- Enhanced test isolation and reliability
- Better test organization by moving config-specific tests to config test class
- Consistent formatting and style improvements
* fix(threads): implement virtual threads for schedulers and JVM lifecycle management

Resolves scheduler thread management issues where schedulers weren't using virtual threads
consistently and Nano was terminating immediately after startup due to lack of non-daemon threads.

**Core Changes:**
- ✅ Scheduler now uses GLOBAL_THREAD_FACTORY for consistent virtual thread usage
- ✅ Added per-instance keep-alive thread in NanoThreads constructor to prevent JVM exit
- ✅ Simplified thread naming with NANO_THREAD_PREFIX constant
- ✅ Added proper shutdown hook for keep-alive thread interruption

**Thread Management:**
- Scheduler extends ScheduledThreadPoolExecutor with virtual thread factory
- Keep-alive thread runs Thread.sleep(Long.MAX_VALUE) as non-daemon thread
- Graceful shutdown interrupts keep-alive thread during application shutdown
- Thread-safe implementation without complex atomic operations

**Performance Benefits:**
- ✅ All schedulers now use lightweight virtual threads instead of platform threads
- ✅ Consistent thread naming: "nano-thread-" prefixed virtual threads
- ✅ Minimal memory footprint with single keep-alive thread per Nano instance
- ✅ JVM stays alive properly until explicit shutdown

**Verified Fix:**
- ✅ 1280+ scheduler tests passing with virtual thread implementation
- ✅ Application no longer exits immediately after startup
- ✅ Proper graceful shutdown with thread cleanup
- ✅ Virtual thread performance benefits realized

Closes: Scheduler virtual thread inconsistency and immediate JVM exit
Tests: All scheduler and main Nano tests passing
* docs(events): add EVENT_CONFIG_CHANGE broadcast best practices and prevent acknowledgment

Addresses EVENT_CONFIG_CHANGE reliability issues by providing comprehensive user guidance
instead of framework-level exceptions, maintaining clean architecture principles.

**Documentation Updates:**
- ✅ Added detailed best practices section in `/docs/events/README.md`
- ✅ Clear examples of what NOT to do (acknowledging config events)
- ✅ Clear examples of recommended approach (use payload() without acknowledgment)
- ✅ Alternative solution: use broadcast(true) when sending if acknowledgment needed
- ✅ Added warning link in `/docs/context/README.md` EVENT_CONFIG_CHANGE table entry
- ✅ Enhanced `Event.acknowledge()` javadocs with propagation warning

**Code Improvements:**
- ✅ Fixed NanoBase.java to not acknowledge EVENT_CONFIG_CHANGE (line 74)
- ✅ Minor cleanup in Service.java event handling logic
- ✅ Maintains original event dispatch behavior without special exceptions

**Why This Approach:**
- Clean Design: No hard-coded exceptions for specific event types
- User Education: Comprehensive documentation with clear examples
- Performance: No additional runtime checks or special handling
- Maintainable: Simple, consistent event handling across all event types

**User Guidance:**
- Configuration changes need to reach all services simultaneously
- Database connections, caches, HTTP clients all need config updates
- Acknowledgment stops propagation, causing inconsistent configuration states
- Solution: Use payload() instead of payloadAck() for config events

Resolves: EVENT_CONFIG_CHANGE not reliably broadcast to multiple listeners
Tests: All existing tests continue to pass
* feat(services): enhance FileWatcher with group-based watching and automatic config reloading

Transforms FileWatcher into a generic, reusable service with comprehensive file system monitoring
capabilities and automatic EVENT_CONFIG_CHANGE triggering for configuration files.

**Core Enhancements:**
- ✅ Group-based file watching for multi-component reusability
- ✅ Automatic EVENT_CONFIG_CHANGE triggering for application.properties files
- ✅ Thread-safe concurrency with ReentrantReadWriteLock
- ✅ Duplicate prevention with intelligent path deduplication
- ✅ Clean group removal without affecting overlapping groups

**New API Features:**
- EVENT_WATCH_GROUP/EVENT_UNWATCH_GROUP for group-based operations
- CONFIG_CHANGE_GROUP constant for automatic config file monitoring
- getWatchedGroups()/getGroupPaths() for introspection
- Enhanced processFileEvent() with group-specific handling

**Automatic Config Integration:**
- Monitors config/, resources/, .config/ directories automatically
- Parses changed config files and triggers EVENT_CONFIG_CHANGE
- Provides normalized config keys (dot, underscore, uppercase variants)
- Broadcasts config changes to ensure all listeners receive updates

**Concurrency & Performance:**
- Thread-safe group registration/unregistration
- Efficient duplicate path detection
- Handles overlapping groups correctly
- Minimal memory footprint with concurrent data structures

**Comprehensive Testing:**
- 10 test scenarios covering all functionality
- Group-based watching tests with concurrent operations
- Config change trigger verification
- Multi-group overlap and cleanup testing
- Concurrency stress testing with 10 parallel operations

**Documentation:**
- Complete FileWatcher service documentation
- Usage examples for HttpServer certificate reloading
- Kubernetes ConfigMap integration patterns
- Best practices and troubleshooting guide

**Use Cases Enabled:**
- Automatic config reloading without application restart
- SSL certificate hot-swapping for HttpServer/HttpClient
- Multi-environment configuration watching
- Kubernetes ConfigMap/Secret monitoring
- Resource file change detection

**Backward Compatibility:**
- Legacy EVENT_WATCH_FILE/EVENT_UNWATCH_FILE still supported
- Existing file watching behavior unchanged
- All existing tests continue to pass

Resolves: FileWatcher integration for automatic EVENT_CONFIG_CHANGE triggering
Tests: 10/10 FileWatcher tests passing, all main framework tests passing
* feat: enhance config reader

* Add config watcher and file change events

* Guard config updates with equality check

* Refresh docs for current events and services

* Keep HTTPS endpoint responsive after live reload

* Wire HttpServer into FileWatcher reloads

* Refine FileWatcher tests

* Honor startup config map in profile overlays

* Ensure HTTPS reload keeps serving

* Add HTTPS reload regression tests

* Document HTTP TLS hot reload

* chore: clean up

* chore: clean up

* Stabilize NanoThread wait tests

* Add contributor guide and stabilize memory metric

* Suppress stale file watcher events after unwatch

* docs: highlight conventional commits in agent guides

---------