Drop the dual-accept legacy product names from the jaah-ce

Epic 10450 asked to "Look for any sensitive or internal information". The published jaah-ce (main 245471666, v1.2.4927) still spells the retired internal product name in 5 shipped files, 13 hits. These are the dual-accept legacy names kept for one release (#7154 allowed them through scoped `[[sensitive.allow]]` entries in tools/community_edition/manifest.toml). (a) Repro (finish 10494): `python3 tools/community_edition/build_tree.py <out>; grep -rhoi "skynet[a-z_-]*" <out> | sort | uniq -c`. The hits are SKYNET_NODE_AGENT_TOKEN ×3, SKYNET_CP_BASE_URL ×2, skynet ×2, skynet-cp-self-loopback-v, skynet-cp, SkynetNode, SKYNET_HOME, SKYNETD_COCKPIT_AGENTS, SKYNET, in apps/api/app/console_direct.py, apps/api/app/node_credentials.py, apps/api/app/aws/ownership.py, apps/jaahd/env_helpers.py and apps/jaahd/main.py. (b) Cause: the R4–R6 dual-accept tail (CP↔CP labels still mint the old spelling this release; env and lock fallbacks). Counts live in tools/mirror/retired_name_counts.toml, and the legacy rows in apps/jaahd/README.md § Legacy names still served. R6 (10491) named the remainder "draft R7 #10667". This finish runner could not read #10667 (404 from this project). If it exists and covers this, settle as `no_pr` duplicate, naming it. (c) Fix: once every dev and prod node runs a release that mints and accepts only the jaah spelling (the rename-wave census rule; if prod is short, ASK one round with header `Human act` to promote), remove the old spellings at source. Then delete the five CE `[[sensitive.allow]]` entries for them, lower retired_name_counts.toml with `sensitive.py --monorepo --write`, and drop the matching README rows. (d) Acceptance: the grep in (a) over a fresh CE build → 0. `python3 tools/community_edition/check_tree.py <out>` → 0 findings with no legacy-name allow entry. `./dc check full` green in the merge lane, Jaah Deploy green, and the dev census shows nodes healthy after the deploy. Out of scope: wire or stored-name changes beyond dropping the old accepted spelling; AWS or GitHub names (done in R5); the mirror repos themselves (they reach the change by the next normal publish); repo visibility. Done means: - Zero retired-name hits in the built jaah-ce tree, with no allow entries for them. - The census precondition is cited (dev and prod), the PR is merged, and Jaah Deploy is green.

Dropped the dual-accept legacy names from jaah-ce: the CE build has 0 hits and check_tree 0 findings, and the 5 allow entries are gone. Census: dev and prod CPs on R6, all online nodes current. #7158 merged; Jaah Deploy green (40566961539). AWS legacy tags kept in a cloud-only module. Memory: none applied.