Make the article slug run-unique so test:types can run twice

The article is the only type with a name, so its slug is derived from that
name and is constant. store-file-system's createFile() returns without
writing when the path already exists, while Indiekit still answers 202 with
a Location, so a second run published nothing and aborted on the store
guard with a misleading 'that is not the Indiekit this repo configures'.
CI never saw it because CI always clones into an empty store.

Also say that npm run build must be re-run after publishing; it is one-shot
and nothing watches, so a fresh post 404s until it is.

Author: rmdes

README.md

@@ -19,7 +19,9 @@ into `PASSWORD_SECRET`, and restart. Then in a second terminal:
 npm run build && npm run serve   # your site on :8080
 ```
 
-Publish a post in Indiekit and open the URL it gives you.
+Publish a post in Indiekit, then **re-run `npm run build`** and open the URL it gave you.
+Nothing watches for you: `npm run build` is one-shot, so a freshly published post 404s
+until you rebuild.
 
 When you deploy, set `INDIEKIT_URL` to where Indiekit actually runs before building. The
 `authorization_endpoint`, `token_endpoint` and `micropub` `<link rel>` tags are built from

test/all-types.mjs

@@ -23,6 +23,15 @@ const token = jwt.sign({ me: SITE, scope: "create media" }, SECRET, {
 
 const LIKED = "https://example.com/y";
 
+// Every other type below gets a run-unique slug for free: with no `name`,
+// @indiekit/endpoint-micropub slugs from the publish timestamp. The article
+// has a `name`, so it slugs from that instead — a constant name means a
+// constant path, and store-file-system's createFile() silently no-ops when
+// the path already exists (no write, no error, still a 202 + Location). That
+// makes a second run against a non-empty store publish nothing and abort on
+// the store guard. Keep the name run-unique.
+const RUN_ID = Date.now();
+
 // Upload a 1×1 GIF FIRST, so the photo post can reference an image that really
 // exists on this site. Testing a photo post against an off-site URL proves only
 // that a string was copied into an attribute — it never exercises the flow a
@@ -56,7 +65,7 @@ const PHOTO_PATH = new URL(PHOTO, SITE).pathname;
 
 // [type, properties, strings the page must contain, strings it must not]
 const TYPES = [
-  ["article", { name: "An Article", content: "MARKER_article" }, ["MARKER_article"]],
+  ["article", { name: `An Article ${RUN_ID}`, content: "MARKER_article" }, ["MARKER_article"]],
   ["note", { content: "MARKER_note" }, ["MARKER_note"]],
   ["bookmark", { "bookmark-of": "https://example.com/x", content: "MARKER_bookmark" }, ["MARKER_bookmark"]],
   ["like", { "like-of": LIKED }, [LIKED]],