Re-extract Legacy Documentation Pipeline

When to Use

• A legacy Confluence HTML export is available
• Database needs rebuilding from scratch
• Schema changes require fresh extraction
• New RouterOS versions available in restraml GitHub Pages

Do not use this skill as the migration path for <https://manual.mikrotik.com>;. MikroTik's new Docusaurus manual and CLI Reference require extractor and MCP/TUI result-shape redesign; read DESIGN.md and briefings/B-0012-docusaurus-manual-migration.md first.

Procedure

1. Verify prerequisites

- Bun is installed: bun --version - Dependencies installed: bun install - Legacy HTML export exists in box/documents-export-*/ROS/ - For commands: internet access to https://tikoci.github.io/restraml/ (or provide a local docs path explicitly)

1. Clean existing database

``sh make clean ``

1. Run full pipeline (choose one)

Single version (fast, latest stable only): ``sh make extract ``

All versions (slower, all 46 RouterOS versions): ``sh make extract-full ``

Pipeline order: - extract-html — HTML → pages + callouts tables - extract-properties — Property tables from HTML → properties table - extract-commands or extract-all-versions — inspect.json → commands + rosversions + commandversions - link — command ↔ page mapping

1. Verify results

``sh make search query="firewall filter" `` Expected counts (full pipeline): - ~317 pages, ~4860 properties, ~1034 callouts - ~40K commands (primary version), ~1.67M commandversions - 46 rosversions, ~92% dir link coverage

1. Validate with type check and lint

``sh bun run typecheck && make lint ``

Troubleshooting

• If HTML directory changed, update HTML_DIR in the root Makefile
• If using offline/local data, pass explicit source paths to extract-commands.ts or extract-all-versions.ts
• Each extractor is idempotent — safe to re-run individually
• FK deletion order matters: callouts → properties → pages