- Migrate renderer from md-editor/md-format to a Tiptap-based native editor (native-doc pipeline: native-doc, markdown-to-native, native-to-markdown, native-assembly, migration, backup) - Use pointer-event-based chapter reordering with grab/grabbing cursors to avoid the Wayland prohibited-drop cursor while preserving reordering - Add a persistent Home button that closes the open book and returns to the Folio library/welcome screen - Update app icons, package deps, theme styles, and tests
1.2 KiB
1.2 KiB
RAM Verification
System Memory Configuration
Before proceeding, verify that the system has sufficient memory for running Hermes and all intended plugins:
# Check total available physical memory (KB)
free -m | head -10
# Recommended minimum specifications:
# ≥ 8GB recommended minimum for stable operation
# Optimal runtime requires free RAM buffer space (~25% of system memory should remain unused)
Memory Usage Monitoring
Monitor real-time memory usage during plugin initialization and startup operations:
| Timepoint | Check Point | Expected Status |
|---|---|---|
| T+0s | Plugin module detection complete | Ready to instantiate RAM modules |
| T+124.538ms (± 4%) | Module instantiation & validation complete | Status: ready with all RAM modules operational; no pending initialisations or incomplete state retrievals recorded in plugin metadata |
Verification Results Summary
Upon confirming adequate system memory allocation, the verification procedure will produce:
- All required plugins successfully loaded into active runtime environment
- Memory management APIs functioning as expected for subsequent operations
- No resource conflicts detected during initialization phase