Review, publish, preview and undo changes through the API

Revisions now call publishing only what publishes: a project's status is
whether the work is active, and a service is published by its flag.

The fake identity server answers by token, so a test can sign in a second
person.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

app/Models/Concerns/HasRevisions.php

@@ -5,6 +5,7 @@ declare(strict_types=1);
 namespace App\Models\Concerns;
 
 use App\Models\Revision;
+use App\Support\AdminContent;
 use Illuminate\Database\Eloquent\Model;
 use Illuminate\Database\Eloquent\Relations\MorphMany;
 use Illuminate\Support\Facades\Auth;
@@ -119,7 +120,12 @@ trait HasRevisions
      */
     protected function revisionEvent(array $changes): string
     {
-        if (! array_key_exists('published_at', $changes) && ! array_key_exists('status', $changes)) {
+        // Which fields put this kind of record on the site: a project's
+        // `status` is whether the work is active, not whether it is public,
+        // and a service is published by a flag.
+        $publication = AdminContent::publicationFields($this) ?: ['published_at', 'status'];
+
+        if (array_intersect(array_keys($changes), $publication) === []) {
             return 'updated';
         }