routing-table-updater

Automating routing table updates involves scanning your repository to identify all skills and agents, extracting their metadata, generating routing entries, and safely updating the tables. This pipeline preserves manual entries and provides backups before applying changes.

The phase-gated pipeline is a five-stage process—SCAN, EXTRACT, GENERATE, UPDATE, VERIFY—used to deterministically map skills to routing entries. It ensures safe updates by executing scripts sequentially, reporting diffs, and validating markdown syntax.

Yes, automated routing updates preserve manual entries. The pipeline identifies existing routing table entries and safeguards your manual additions during the update phase, ensuring only generated entries are replaced while originals are backed up.

If markdown validation fails during the VERIFY phase, the pipeline provides rollback options to restore the original routing tables from backups. This ensures your routing configuration remains accurate and safe even when validation encounters errors.

You can track changes using the pipeline's built-in diff reporting, which outputs statuses and differences between original and generated routing tables. This visibility guides operators through the update process by clearly showing what entries were added or modified.