routeros-centrslisted

# Driving RouterOS with centrs ## What this is for [`@tikoci/centrs`](https://github.com/tikoci/centrs) is a **friendly conduit** to RouterOS, not a configuration abstraction. You still speak RouterOS; centrs handles the parts that are tedious and error-prone to do by hand: - resolving `<router>` to an address, credentials, port, and a protocol; - **validating a RouterOS-shaped command before it runs**; - returning the same structured envelope whatever transport carried the call. Validation and structured diagnostics are the product. Without them it would be a worse `curl`. **Reach for centrs when** you need to run a RouterOS command, read state, or move a file — from a shell script, a test, or an agent loop. **Don't reach for it** when you need RouterOS *documentation* (use the `rosetta` MCP or the `routeros-fundamentals` skill), or when you need to *create* the router itself (use `routeros-quickchr-cli` from a shell, or `routeros-quickchr` for the TypeScript library — centrs consumes a quickchr VM, it does not boot one). > **Status:** `0.1.x` preview under active development. The repo README publishes > preview builds under npm's `next` tag, so pin `@next` rather than assuming `latest` > tracks them — confirm with `npm view @tikoci/centrs dist-tags`. Expect breaking > changes before 1.0 and exercise writes on lab or disposable targets first. > [`docs/MATRIX.md`](https://github.com/tikoci/centrs/blob/main/docs/MATRIX.md) is the > single source of truth for what works