docs(specs): discovery for long-running service jobs

New briefs: host-failure-job-recovery (jobs on a lost host are requeued or
end EXIT after a grace period; stale copies fenced on rejoin; manual
requeue), service-supervision (profile kind service: restart policy and
liveness/readiness probes run by each replica's own worker, in-place
restart), service-replica-set (controller-held service object owning
independent replica jobs; event-driven replacement, scaling and rolling
update; no head agent, no promotion), service-endpoint (per-replica ports,
endpoints of ready replicas), job-resize (backlog, elastic jobs).

application-profile brief gains the service section; roadmap lists the new
specs, the existing-spec updates and the backlog item.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

.kiro/specs/application-profile/brief.md

@@ -34,6 +34,15 @@ decisions):**
   still taken from the profile at dispatch time; requirements decide whether
   dispatch freezes them on the job record.
 
+**Update 2026-10-10 (`/kiro-discovery`, long-running services):** a profile
+may declare **kind `service`** with a service section: restart policy
+(always / on-failure / never, backoff, give-up), liveness and readiness
+probes (command / TCP / HTTP), named ports, default replica count, spread
+rule and rollout settings. The section is defined with this spec and
+consumed by `service-supervision` (worker probes and restarts),
+`service-replica-set` (replicas, scaling, rolling update) and
+`service-endpoint` (ports, endpoints).
+
 ## Problem
 XCE users run many kinds of applications: trusted in-house codes, untrusted
 scripts, vendor binaries, MPI solvers. Each needs a different way of running: