build: file the package under Administration rather than Network

[raspbeguy]

SECTION moves from net to admin and CATEGORY from Network to Administration. uapi is a management surface rather than a networking daemon, so it reads better beside the administration tools than beside the web servers.

One correction to the premise, because it changes how much this matters. The shipped package carries no section or category. Reading the installed database on a device, the fields apk records for uapi are A C D F I L M P R S T U V Z a f g k m o p, where S: is the size in bytes; there is no section field, and no s: line exists for any of the 294 installed packages. So these two values never reach the artifact, the installed database, or the feed index.

What they do affect is menuconfig placement for anyone building from source, which is the whole of the change.

Precedent is mixed, for the record. OpenWrt's Administration category is conventionally CLI sysadmin tooling: atop, btop, earlyoom, debootstrap. The closest functional analogue to uapi is rpcd, the ubus RPC backend, which sits in utils / Base system, while uhttpd, which uapi runs inside, is net / Network under a Web Servers/Proxies submenu. An argument exists for any of the three. Administration is a defensible pick and the one that matches how an operator thinks about the package.

Does this change the wire surface? No, and it does not change the package either. Build-recipe metadata only.

Was it verified against a real device, or only by CI? The claim being verified here is the negative one, that this is invisible in the artifact, and that came from the installed database on the rc3 box. make lint and 1230 unit tests pass. A local SDK rebuild to confirm the built package is unchanged ran past my time limit and is not part of the evidence; verify-arch-build on a tag exercises it properly.

Was LuCI checked? Not applicable. The companion luci-app-uapi package carries its own category and is untouched.

If the preference is really about how the package presents to operators, worth knowing that the visible surface is TITLE, T: in the database, which currently reads "Native HTTP REST API for OpenWrt". That one does ship, and can be changed independently of this.