archetypes: build an archetype agent from its archetype's module on the hive

The hive reads the agent-archetype key when it provisions and rebuilds an
agent and keeps it in swarm-agent-archetypes.json. For an archetype agent
the meta flake has no agent-<name> input and mkAgent imports
hyperhive.hyperhiveArchetypes.<name>.module; provisioning, rebuilds, the
meta-input cascade, a deploy's rev and the startup migration skip the
config repos. The harness gets HIVE_ARCHETYPE and the system prompt says
the agent has no config repo. The create form sends the picked archetype.
Adds the android-dev built-in.

Refs #5386

frontend/packages/swarm-ui/test/create-agent-archetype.test.mjs

@@ -2,7 +2,11 @@
 // Run by `npm test` with Node's type stripping.
 import assert from "node:assert/strict";
 import { test } from "node:test";
-import { archetypeKey, prefill } from "../src/pages/CreateAgentArchetype.ts";
+import {
+  archetypeKey,
+  prefill,
+  requestArchetype,
+} from "../src/pages/CreateAgentArchetype.ts";
 
 const defaults = ["messaging", "meta", "inbox", "execution"];
 
@@ -65,3 +69,17 @@ test("the key tells sources apart", () => {
     archetypeKey({ source: "b", name: "x", description: "" }),
   );
 });
+
+test("a picked archetype is sent by source and name, none is left out", () => {
+  const reviewer = {
+    source: "hyperhive",
+    name: "reviewer",
+    description: "reviews",
+    permissions: ["messaging"],
+  };
+  assert.deepEqual(requestArchetype(reviewer), {
+    source: "hyperhive",
+    name: "reviewer",
+  });
+  assert.equal(requestArchetype(undefined), undefined);
+});