Split QueryStatus.Accepted into ProAccepted/ClientAccepted

Distinguish the two parties' acceptances: ProAccepted (provider) and
ClientAccepted (client) replace the single Accepted value for new
acceptances. Accepted=2 is retained as a legacy value so existing DB rows
keep their integer mapping.

- FrontOfficeApiController.AcceptQuery sets status by ActorRole
- BillingController provider-ongoing filters match the new values
- FrontOfficeController (MVC) dashboard counts use ProAccepted||Accepted
- PostIt: IsOngoingStatus, GetStatusRank (client-accepted ranks first for
  the pro), and status-badge switches (P/C glyphs) handle the new values
- Tests assert ProAccepted (provider) vs ClientAccepted (client)

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

src/Yavsc.Abstract/Workflow/QueryStatus.cs

@@ -5,15 +5,28 @@ namespace Yavsc
      /// should be associated to any
     /// client user query to a provider user or
     /// other external entity.
+    ///
+    /// <para>
+    /// Acceptance is split by party: <see cref="ProAccepted"/> when the
+    /// provider accepts the client's request (and produces/submits the
+    /// estimate), <see cref="ClientAccepted"/> when the client accepts
+    /// the provider's estimate. <see cref="Accepted"/> is the legacy
+    /// single-value kept for rows written before the split; new writes
+    /// use the party-specific values. Its integer value (2) is stable
+    /// so existing rows still deserialize.
+    /// </para>
     /// </summary>
     public enum QueryStatus: int
     {
-        Inserted,
-        Rejected,
-        Accepted,
-        InProgress,
+        Inserted = 0,
+        Rejected = 1,
+        Accepted = 2,
+        InProgress = 3,
         // final states
-        Failed,
-        Success
+        Failed = 4,
+        Success = 5,
+        // party-specific acceptance (see summary)
+        ProAccepted = 6,
+        ClientAccepted = 7,
     }
-}
+}