What problem does it solve? Writing a tik4net.objects entity for a MikroTik API path by hand requires reconciling live router field sets, wiki documentation, read-only splits, enum vocabularies, and subtle mapper conventions (nullable bools, DefaultValue rules, TikEntity attributes) — a slow, error-prone process that previously relied on two deleted WinForms generator tools. ## Core Features & Use Cases - Entity scaffolding from a path: Produces a complete C# class with [TikEntity]/[TikProperty] attributes, correct namespace and naming conventions, enums with [TikEnum] wire values, and a ToString override. - Multi-source field resolution: Combines live router queries over multiple transports (Api, WinboxNative, Rest, CLI), CLI Tab-completion for the writable field set, and MikroTik wiki/CLI-reference pages for types, defaults, and documentation. - Convention enforcement: Applies the add-path DefaultValue rules, bool? vs bool distinctions, read-only private setters, and WinBox GUI name documentation, then adds the standard List/Add integration tests. - Use Case: Ask for an entity for /ip/dhcp-server/lease and receive a finished, buildable FirewallFilter-style class plus its integration tests, validated against a live router. ## Quick Start Ask the assistant to generate a tik4net entity for the MikroTik API path /interface/vlan, including its standard integration tests.