@rubytech/create-maxy-code 0.1.576 → 0.1.578

package/payload/platform/plugins/cloudflare/skills/data-portal/template/functions/api/visits.ts

@@ -17,6 +17,47 @@ export interface VisitRow {
   status: string
   startDate: string
   purpose: string
+  /**
+   * What the worker recorded, as COUNTS (Task 2511).
+   *
+   * Counts and never contents, which is this interface's own rule above applied
+   * rather than relaxed: the contents are files and the Task 1910 exchange
+   * carries them. A count says what was recorded and what is still missing,
+   * which is what the office could not see at all before, without putting a
+   * real person's written note or signature in a mirror on the open web. The
+   * contents are Task 2563.
+   *
+   * `checklistDone` is read against `checklistTotal` and never alone: a count
+   * of ticked items with no total says nothing about whether the work is done.
+   */
+  notes: number
+  media: number
+  parts: number
+  checklistDone: number
+  checklistTotal: number
+  signatures: number
+}
+
+/**
+ * One candidate for one unallocated visit (Task 2511).
+ *
+ * Precomputed on the install by the one implementation of qualification and
+ * clash, and rendered as returned. This endpoint applies no such rule of its own
+ * and neither does the page, for the reason `processVisits` states below.
+ *
+ * `kind` decides which of the last two fields carries anything. An `offered`
+ * row has an empty `reason` and its conflicts, which is `[]` when the worker is
+ * free; an `excluded` row has empty conflicts and its reason. A qualified
+ * worker already committed is OFFERED with the conflict shown and never
+ * dropped, because the office double-books on purpose.
+ */
+export interface CandidateRow {
+  visitId: string
+  workerId: string
+  name: string
+  kind: string
+  reason: string
+  conflicts: Array<{ visitId: string; start: string; end: string }>
 }
 
 /**
@@ -46,6 +87,16 @@ export interface RosterRow {
 export interface Meta {
   vocabulary: { job: string; visit: string; worker: string }
   statuses: Array<{ name: string; terminal: boolean }>
+  /**
+   * The account's legal moves, `[from, to]` (Task 2511).
+   *
+   * Absent from the list means refused, and an empty list therefore refuses
+   * every move, which is what an account declaring none means. The page refuses
+   * from this published copy, so an illegal drag is refused while the install is
+   * offline; `visit-status.ts` refuses from the same copy, which is the refusal
+   * that binds.
+   */
+  transitions: Array<[string, string]>
   zone: string
   publishedAt: string
 }
@@ -100,7 +151,10 @@ export async function processVisits(
   // makes against directory_state, for the same reason.
   const sql =
     `SELECT v.visitId AS visitId, v.ownerId AS ownerId, v.jobId AS jobId,
-            v.status AS status, v.startDate AS startDate, v.purpose AS purpose
+            v.status AS status, v.startDate AS startDate, v.purpose AS purpose,
+            v.notes AS notes, v.media AS media, v.parts AS parts,
+            v.checklistDone AS checklistDone, v.checklistTotal AS checklistTotal,
+            v.signatures AS signatures
        FROM visits v
        JOIN visits_state s
          ON s.accountId = v.accountId AND s.currentGeneration = v.generation
@@ -143,16 +197,69 @@ export async function processVisits(
     workingHours: parseJson<Record<string, [string, string]>>(r.workingHours, {}),
   }))
 
+  // THE SAME TWO FILTERS, applied through the visits join rather than beside it
+  // (Task 2511). A candidate row names a colleague, so an own-scoped person
+  // receiving candidates for a visit they cannot see would learn the roster the
+  // roster read above deliberately withholds from them. The join IS the owner
+  // filter; there is no second check to keep in step with it.
+  //
+  // Read through the generation pointer, and joined to the visits at the SAME
+  // generation, so the offers on screen always belong to the week on screen.
+  const candidateSql =
+    `SELECT c.visitId AS visitId, c.workerId AS workerId, c.name AS name,
+            c.kind AS kind, c.reason AS reason, c.conflicts AS conflicts
+       FROM visit_candidates c
+       JOIN visits v
+         ON v.accountId = c.accountId AND v.visitId = c.visitId
+        AND v.generation = c.generation
+       JOIN visits_state s
+         ON s.accountId = c.accountId AND s.currentGeneration = c.generation
+      WHERE c.accountId = ?` +
+    (scoped ? ' AND v.ownerId = ?' : '') +
+    ' ORDER BY c.visitId ASC, c.workerId ASC'
+  const candidateStmt = env.DB.prepare(candidateSql)
+  const candidateRows = await (
+    scoped
+      ? candidateStmt.bind(env.PORTAL_ACCOUNT_ID, session.ownerId)
+      : candidateStmt.bind(env.PORTAL_ACCOUNT_ID)
+  ).all<{
+    visitId: string
+    workerId: string
+    name: string
+    kind: string
+    reason: string
+    conflicts: string
+  }>()
+
+  // Parsed here, once, for the reason the roster's workingHours is: a column of
+  // JSON parsed by every consumer is a shape each of them can disagree about.
+  // An excluded row carries no conflicts at all, so its empty column reads as
+  // an empty list rather than throwing.
+  const candidates: CandidateRow[] = (candidateRows.results ?? []).map((c) => ({
+    visitId: c.visitId,
+    workerId: c.workerId,
+    name: c.name,
+    kind: c.kind,
+    reason: c.reason,
+    conflicts: parseJson<Array<{ visitId: string; start: string; end: string }>>(c.conflicts, []),
+  }))
+
   const metaRow = await env.DB.prepare(
-    `SELECT m.vocabulary AS vocabulary, m.statuses AS statuses, m.zone AS zone,
-            m.publishedAt AS publishedAt
+    `SELECT m.vocabulary AS vocabulary, m.statuses AS statuses, m.transitions AS transitions,
+            m.zone AS zone, m.publishedAt AS publishedAt
        FROM dispatch_meta m
        JOIN visits_state s
          ON s.accountId = m.accountId AND s.currentGeneration = m.generation
       WHERE m.accountId = ?`,
   )
     .bind(env.PORTAL_ACCOUNT_ID)
-    .first<{ vocabulary: string; statuses: string; zone: string; publishedAt: string }>()
+    .first<{
+      vocabulary: string
+      statuses: string
+      transitions: string
+      zone: string
+      publishedAt: string
+    }>()
 
   // NOT owner-scoped. The nouns, the statuses and the account's timezone are
   // configuration, not a record about a person, and the page cannot draw a day
@@ -161,6 +268,11 @@ export async function processVisits(
     ? {
         vocabulary: parseJson(metaRow.vocabulary, { job: '', visit: '', worker: '' }),
         statuses: parseJson<Array<{ name: string; terminal: boolean }>>(metaRow.statuses, []),
+        // A malformed list falls back to EMPTY, which refuses every move. The
+        // other direction would be worse in kind rather than in degree: a page
+        // that accepts every move enforces nothing and is indistinguishable on
+        // screen from one that enforces correctly.
+        transitions: parseJson<Array<[string, string]>>(metaRow.transitions, []),
         zone: metaRow.zone,
         publishedAt: metaRow.publishedAt,
       }
@@ -172,9 +284,9 @@ export async function processVisits(
   log(
     `[data-portal] op=visits owner=${q(session.ownerId)} account=${q(session.accountId)} ` +
       `scope=${session.recordScope} visits=${visits.length} roster=${roster.length} ` +
-      `meta=${meta !== null} result=ok`,
+      `candidates=${candidates.length} meta=${meta !== null} result=ok`,
   )
-  return { status: 200, payload: { ok: true, visits, roster, meta } }
+  return { status: 200, payload: { ok: true, visits, roster, meta, candidates } }
 }
 
 interface PagesContext {

package/payload/platform/plugins/dispatch/PLUGIN.md

@@ -123,6 +123,8 @@ A move from one status to another is legal when the account's own transition lis
 
 Neither refusal is swallowed. A status that quietly failed to change cannot be told apart from one nobody tried to change.
 
+The office planner on an account's own portal enforces the same list, from a copy published with the week. The page refuses an undeclared move before sending it, so an illegal drag is refused even while the device is offline, and the portal's write door refuses it again from that same copy. Only the door's refusal binds; the page's exists so the person is told at once rather than a minute later. A status equal to the one already held is not a move on either side, so re-timing or re-assigning a record never has to invent a transition to itself.
+
 ## A busy worker is offered, not hidden
 
 Only a missing qualification excludes a worker from the candidate list, and every exclusion is named with its worker and its reason. A qualified worker who is already committed in the window is offered with the clash shown.

package/payload/platform/plugins/dispatch/mcp/dist/lib/allocate.d.ts

@@ -1,59 +1,28 @@
 /**
  * Who can be sent to this job, and why the others cannot.
  *
- * The rule that matters: **a qualified worker who is already committed in the
- * window is offered WITH the conflict shown, never dropped.** The office
- * routinely double-books on purpose — a job runs short, a customer is on the
- * way home, an engineer volunteers. A tool that silently removes the busy
- * option makes that decision for them and gives no way to see it was made.
+ * `selectCandidates`, `overlaps` and their types moved to
+ * `platform/lib/dispatch-read` in Task 2511, so the portal visits push and these
+ * tools share one implementation of qualification and clash. The push runs in
+ * `platform/ui` and cannot import a plugin's build output, and a second copy of
+ * these rules is the defect `functions/api/visits.ts:33-36` names. The queries
+ * and the rules moved; they did not change. This module stays as the plugin's
+ * import surface, exactly as `lib/read.ts` did for the Cypher reads.
  *
- * Only a missing qualification excludes, and every exclusion is named with its
- * worker and its reason, because `offered=0` with no explanation is the shape a
- * quiet day and an unstaffable job type share.
+ * `Commitment` now comes from that package's `read.ts`, where
+ * `readCommitments` declares it. The second structurally-identical declaration
+ * that used to live here is gone: two declarations of one contract can drift on
+ * a field.
  *
- * Task 2509 added the travel estimate. A candidate carries `travelMinutes` when
- * one could be produced and **omits the key** when it could not, with the
- * reason in `travelReason` — never a zero and never a null, either of which
- * would read as a measurement. `selectCandidates` below is deliberately
- * untouched by it: no estimator state may change who is offered.
+ * Task 2509 added the travel estimate, and it stays here. A candidate carries
+ * `travelMinutes` when one could be produced and **omits the key** when it
+ * could not, with the reason in `travelReason` — never a zero and never a null,
+ * either of which would read as a measurement. `selectCandidates` is
+ * deliberately untouched by it: no estimator state may change who is offered.
  */
-import type { DispatchConfig } from "./types.js";
-export interface Commitment {
-    readonly visitId: string;
-    readonly start: string;
-    readonly end: string;
-}
-export interface Candidate {
-    readonly workerId: string;
-    readonly name: string;
-    /** Commitments overlapping the requested window. Empty means free. */
-    readonly conflicts: readonly Commitment[];
-}
-export interface Exclusion {
-    readonly workerId: string;
-    readonly reason: "missing-qualification";
-}
-export interface SelectCandidatesParams {
-    readonly jobType: string;
-    readonly cfg: DispatchConfig;
-    /** Committed visits per workerId, already narrowed to the window. */
-    readonly commitments: ReadonlyMap<string, readonly Commitment[]>;
-}
-export interface CandidateSelection {
-    readonly offered: readonly Candidate[];
-    readonly excluded: readonly Exclusion[];
-    /** The qualification the job type demands, echoed for the log line. */
-    readonly required: string;
-}
-export declare function selectCandidates(params: SelectCandidatesParams): CandidateSelection;
-/** `[a, b)` overlap. Touching endpoints do not overlap. */
-export declare function overlaps(a: {
-    start: string;
-    end: string;
-}, b: {
-    start: string;
-    end: string;
-}): boolean;
+import type { Exclusion } from "../../../../../lib/dispatch-read/dist/index.js";
+export { overlaps, selectCandidates, } from "../../../../../lib/dispatch-read/dist/index.js";
+export type { Candidate, CandidateSelection, Commitment, Exclusion, SelectCandidatesParams, } from "../../../../../lib/dispatch-read/dist/index.js";
 /**
  * Why a candidate carries no estimate, or the estimate itself.
  *

package/payload/platform/plugins/dispatch/mcp/dist/lib/allocate.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"allocate.d.ts","sourceRoot":"","sources":["../../src/lib/allocate.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;GAkBG;AACH,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,YAAY,CAAC;AAEjD,MAAM,WAAW,UAAU;IACzB,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;IACzB,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,QAAQ,CAAC,GAAG,EAAE,MAAM,CAAC;CACtB;AAED,MAAM,WAAW,SAAS;IACxB,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC;IAC1B,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,sEAAsE;IACtE,QAAQ,CAAC,SAAS,EAAE,SAAS,UAAU,EAAE,CAAC;CAC3C;AAED,MAAM,WAAW,SAAS;IACxB,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC;IAC1B,QAAQ,CAAC,MAAM,EAAE,uBAAuB,CAAC;CAC1C;AAED,MAAM,WAAW,sBAAsB;IACrC,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;IACzB,QAAQ,CAAC,GAAG,EAAE,cAAc,CAAC;IAC7B,qEAAqE;IACrE,QAAQ,CAAC,WAAW,EAAE,WAAW,CAAC,MAAM,EAAE,SAAS,UAAU,EAAE,CAAC,CAAC;CAClE;AAED,MAAM,WAAW,kBAAkB;IACjC,QAAQ,CAAC,OAAO,EAAE,SAAS,SAAS,EAAE,CAAC;IACvC,QAAQ,CAAC,QAAQ,EAAE,SAAS,SAAS,EAAE,CAAC;IACxC,uEAAuE;IACvE,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC;CAC3B;AAED,wBAAgB,gBAAgB,CAAC,MAAM,EAAE,sBAAsB,GAAG,kBAAkB,CAuBnF;AAED,2DAA2D;AAC3D,wBAAgB,QAAQ,CACtB,CAAC,EAAE;IAAE,KAAK,EAAE,MAAM,CAAC;IAAC,GAAG,EAAE,MAAM,CAAA;CAAE,EACjC,CAAC,EAAE;IAAE,KAAK,EAAE,MAAM,CAAC;IAAC,GAAG,EAAE,MAAM,CAAA;CAAE,GAChC,OAAO,CAET;AAED;;;;;;;GAOG;AACH,MAAM,MAAM,YAAY,GAAG,MAAM,GAAG,mBAAmB,GAAG,aAAa,CAAC;AAExE,wBAAgB,oBAAoB,CAAC,CAAC,EAAE;IACtC,KAAK,EAAE,MAAM,CAAC;IACd,2DAA2D;IAC3D,WAAW,EAAE,MAAM,GAAG,IAAI,CAAC;IAC3B,QAAQ,EAAE,MAAM,CAAC;IACjB,MAAM,EAAE,YAAY,CAAC;IACrB,EAAE,EAAE,MAAM,CAAC;CACZ,GAAG,MAAM,CAKT;AAED,wBAAgB,wBAAwB,CAAC,CAAC,EAAE;IAC1C,KAAK,EAAE,MAAM,CAAC;IACd,QAAQ,EAAE,MAAM,CAAC;IACjB,OAAO,EAAE,MAAM,CAAC;IAChB,QAAQ,EAAE,SAAS,SAAS,EAAE,CAAC;CAChC,GAAG,MAAM,CAST"}
+{"version":3,"file":"allocate.d.ts","sourceRoot":"","sources":["../../src/lib/allocate.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AAGH,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,gDAAgD,CAAC;AAEhF,OAAO,EACL,QAAQ,EACR,gBAAgB,GACjB,MAAM,gDAAgD,CAAC;AACxD,YAAY,EACV,SAAS,EACT,kBAAkB,EAClB,UAAU,EACV,SAAS,EACT,sBAAsB,GACvB,MAAM,gDAAgD,CAAC;AAExD;;;;;;;GAOG;AACH,MAAM,MAAM,YAAY,GAAG,MAAM,GAAG,mBAAmB,GAAG,aAAa,CAAC;AAExE,wBAAgB,oBAAoB,CAAC,CAAC,EAAE;IACtC,KAAK,EAAE,MAAM,CAAC;IACd,2DAA2D;IAC3D,WAAW,EAAE,MAAM,GAAG,IAAI,CAAC;IAC3B,QAAQ,EAAE,MAAM,CAAC;IACjB,MAAM,EAAE,YAAY,CAAC;IACrB,EAAE,EAAE,MAAM,CAAC;CACZ,GAAG,MAAM,CAKT;AAED,wBAAgB,wBAAwB,CAAC,CAAC,EAAE;IAC1C,KAAK,EAAE,MAAM,CAAC;IACd,QAAQ,EAAE,MAAM,CAAC;IACjB,OAAO,EAAE,MAAM,CAAC;IAChB,QAAQ,EAAE,SAAS,SAAS,EAAE,CAAC;CAChC,GAAG,MAAM,CAST"}

package/payload/platform/plugins/dispatch/mcp/dist/lib/allocate.js

@@ -1,31 +1,4 @@
-export function selectCandidates(params) {
-    const { jobType, cfg, commitments } = params;
-    const type = cfg.jobTypes.find((t) => t.name === jobType);
-    if (!type) {
-        // An unknown job type is the caller's error, not a staffing outcome. Every
-        // worker is excluded for a reason that would be a lie, so none are: the
-        // caller checks the type before asking.
-        return { offered: [], excluded: [], required: "" };
-    }
-    const offered = [];
-    const excluded = [];
-    for (const worker of cfg.workers) {
-        if (!worker.qualifications.includes(type.requiredQualification)) {
-            excluded.push({ workerId: worker.workerId, reason: "missing-qualification" });
-            continue;
-        }
-        offered.push({
-            workerId: worker.workerId,
-            name: worker.name,
-            conflicts: commitments.get(worker.workerId) ?? [],
-        });
-    }
-    return { offered, excluded, required: type.requiredQualification };
-}
-/** `[a, b)` overlap. Touching endpoints do not overlap. */
-export function overlaps(a, b) {
-    return a.start < b.end && b.start < a.end;
-}
+export { overlaps, selectCandidates, } from "../../../../../lib/dispatch-read/dist/index.js";
 export function formatTravelEstimate(p) {
     return (`[dispatch] op=travel-estimate jobId=${p.jobId} fromVisitId=${p.fromVisitId ?? "none"} ` +
         `provider=${p.provider} result=${p.result} ms=${p.ms}`);

package/payload/platform/plugins/dispatch/mcp/dist/lib/allocate.js.map

@@ -1 +1 @@
-{"version":3,"file":"allocate.js","sourceRoot":"","sources":["../../src/lib/allocate.ts"],"names":[],"mappings":"AAqDA,MAAM,UAAU,gBAAgB,CAAC,MAA8B;IAC7D,MAAM,EAAE,OAAO,EAAE,GAAG,EAAE,WAAW,EAAE,GAAG,MAAM,CAAC;IAC7C,MAAM,IAAI,GAAG,GAAG,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,KAAK,OAAO,CAAC,CAAC;IAC1D,IAAI,CAAC,IAAI,EAAE,CAAC;QACV,2EAA2E;QAC3E,wEAAwE;QACxE,wCAAwC;QACxC,OAAO,EAAE,OAAO,EAAE,EAAE,EAAE,QAAQ,EAAE,EAAE,EAAE,QAAQ,EAAE,EAAE,EAAE,CAAC;IACrD,CAAC;IACD,MAAM,OAAO,GAAgB,EAAE,CAAC;IAChC,MAAM,QAAQ,GAAgB,EAAE,CAAC;IACjC,KAAK,MAAM,MAAM,IAAI,GAAG,CAAC,OAAO,EAAE,CAAC;QACjC,IAAI,CAAC,MAAM,CAAC,cAAc,CAAC,QAAQ,CAAC,IAAI,CAAC,qBAAqB,CAAC,EAAE,CAAC;YAChE,QAAQ,CAAC,IAAI,CAAC,EAAE,QAAQ,EAAE,MAAM,CAAC,QAAQ,EAAE,MAAM,EAAE,uBAAuB,EAAE,CAAC,CAAC;YAC9E,SAAS;QACX,CAAC;QACD,OAAO,CAAC,IAAI,CAAC;YACX,QAAQ,EAAE,MAAM,CAAC,QAAQ;YACzB,IAAI,EAAE,MAAM,CAAC,IAAI;YACjB,SAAS,EAAE,WAAW,CAAC,GAAG,CAAC,MAAM,CAAC,QAAQ,CAAC,IAAI,EAAE;SAClD,CAAC,CAAC;IACL,CAAC;IACD,OAAO,EAAE,OAAO,EAAE,QAAQ,EAAE,QAAQ,EAAE,IAAI,CAAC,qBAAqB,EAAE,CAAC;AACrE,CAAC;AAED,2DAA2D;AAC3D,MAAM,UAAU,QAAQ,CACtB,CAAiC,EACjC,CAAiC;IAEjC,OAAO,CAAC,CAAC,KAAK,GAAG,CAAC,CAAC,GAAG,IAAI,CAAC,CAAC,KAAK,GAAG,CAAC,CAAC,GAAG,CAAC;AAC5C,CAAC;AAYD,MAAM,UAAU,oBAAoB,CAAC,CAOpC;IACC,OAAO,CACL,uCAAuC,CAAC,CAAC,KAAK,gBAAgB,CAAC,CAAC,WAAW,IAAI,MAAM,GAAG;QACxF,YAAY,CAAC,CAAC,QAAQ,WAAW,CAAC,CAAC,MAAM,OAAO,CAAC,CAAC,EAAE,EAAE,CACvD,CAAC;AACJ,CAAC;AAED,MAAM,UAAU,wBAAwB,CAAC,CAKxC;IACC,MAAM,UAAU,GACd,CAAC,CAAC,QAAQ,CAAC,MAAM,KAAK,CAAC;QACrB,CAAC,CAAC,MAAM;QACR,CAAC,CAAC,CAAC,CAAC,QAAQ,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,GAAG,CAAC,CAAC,QAAQ,IAAI,CAAC,CAAC,MAAM,EAAE,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;IACnE,OAAO,CACL,2CAA2C,CAAC,CAAC,KAAK,aAAa,CAAC,CAAC,QAAQ,IAAI,MAAM,GAAG;QACtF,WAAW,CAAC,CAAC,OAAO,aAAa,CAAC,CAAC,QAAQ,CAAC,MAAM,eAAe,UAAU,EAAE,CAC9E,CAAC;AACJ,CAAC"}
+{"version":3,"file":"allocate.js","sourceRoot":"","sources":["../../src/lib/allocate.ts"],"names":[],"mappings":"AA0BA,OAAO,EACL,QAAQ,EACR,gBAAgB,GACjB,MAAM,gDAAgD,CAAC;AAmBxD,MAAM,UAAU,oBAAoB,CAAC,CAOpC;IACC,OAAO,CACL,uCAAuC,CAAC,CAAC,KAAK,gBAAgB,CAAC,CAAC,WAAW,IAAI,MAAM,GAAG;QACxF,YAAY,CAAC,CAAC,QAAQ,WAAW,CAAC,CAAC,MAAM,OAAO,CAAC,CAAC,EAAE,EAAE,CACvD,CAAC;AACJ,CAAC;AAED,MAAM,UAAU,wBAAwB,CAAC,CAKxC;IACC,MAAM,UAAU,GACd,CAAC,CAAC,QAAQ,CAAC,MAAM,KAAK,CAAC;QACrB,CAAC,CAAC,MAAM;QACR,CAAC,CAAC,CAAC,CAAC,QAAQ,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,GAAG,CAAC,CAAC,QAAQ,IAAI,CAAC,CAAC,MAAM,EAAE,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;IACnE,OAAO,CACL,2CAA2C,CAAC,CAAC,KAAK,aAAa,CAAC,CAAC,QAAQ,IAAI,MAAM,GAAG;QACtF,WAAW,CAAC,CAAC,OAAO,aAAa,CAAC,CAAC,QAAQ,CAAC,MAAM,eAAe,UAAU,EAAE,CAC9E,CAAC;AACJ,CAAC"}

package/payload/platform/plugins/dispatch/skills/dispatch-page/SKILL.md

@@ -56,15 +56,41 @@ redeploy of a site that gained a page, not a new site.
 Nothing else is copied. The endpoint, the session library and the schema are the portal's and are
 already deployed with it.
 
+## What the office can do with a day
+
+Every action goes through the portal's existing `/api/visit-status` door, and the device carries the
+result into the graph within a minute. There is no second write endpoint and no second credential
+path.
+
+- **Advance a status.** Clicking a record moves it to the next status the account declared.
+- **Re-time it.** Dragging it to another day keeps its clock time and changes its date, computed in
+  the account's own timezone.
+- **Re-assign it.** Dragging it to another worker's row moves it to that worker. The device replaces
+  the attendance; a record two workers share is refused rather than silently losing one of them.
+- **See who could go.** Opening a record's panel lists the workers the install offered, each with
+  their commitments in that window, and the ones it excluded with the reason. Both lists are
+  computed on the device, never on the page.
+- **See what was recorded.** The panel shows how many notes, media, parts, checklist items and
+  signatures the record carries. Counts only; the contents are files and the portal's own file drop
+  already carries them.
+
+**A move the account did not declare is refused twice.** The page refuses it from the transition
+list published with the week, so an illegal drag is refused even while the device is offline, and
+the door refuses it again. Only the door's refusal binds; the page's exists so the person is told
+now rather than in a minute. A refused move returns the record to where it came from and says why,
+because a card that silently slides back is indistinguishable from a gesture that missed.
+
 ## What it does not do
 
-It does not allocate, re-time or re-assign. Clicking a visit moves it to the next status the account
-declared, through the portal's existing `/api/visit-status` door, and the device carries that into
-the graph within a minute. Enforcing which transitions are legal, and acting on a day rather than
-recording it, are not built here.
+It does not show a job list, counts of unallocated or past-target work, or the
+pressed-against-observed arrival panel. None of those is on this page today.
+
+A candidate carries no estimate of how long it takes to reach the site from where that worker
+already is. The office sees who is qualified and who is busy, and picks between two names with no
+idea one of them is ninety minutes away.
 
-It does not show a job list, counts of unallocated or past-target work, or the pressed-against-observed
-arrival panel. None of those is on this page today.
+The completed-work panel shows counts, not contents. Reading the note a worker wrote, or the
+signature they captured, still means opening the file drop.
 
 ## Done-gate
 
@@ -80,6 +106,19 @@ The page is not done until all five hold on the live domain:
    from a day off.
 5. Clicking a visit changes its status on screen, and `grep '\[portal-visits-pull\]' server.log`
    carries `op=applied visitId=` for it within one minute.
+6. `grep '\[portal-visits-push\]' server.log` shows `transitions=` above zero for this account. Zero
+   there is not a quiet account: it is a page that refuses every move while looking identical to one
+   that enforces correctly.
+7. Dragging a visit onto another worker's row shows it there, and the pull carries
+   `op=applied visitId= field=assignedOwnerId` within one minute.
+8. Attempting a move the account did not declare shows the refusal, returns the card, and the Pages
+   log carries `op=rejected reason=illegal-transition` while `grep 'op=applied' server.log` reports
+   nothing for that visit. A refusal that still wrote is the failure the transition gate exists to
+   prevent.
+
+Condition 5 could not pass before the write half shipped: the pull emitted `op=merged` and
+`op=unresolved` and no `op=applied` line existed anywhere. It does now, and it names the visit and
+the field, which is the only way to pair a write the door accepted to one the device applied.
 
 The freshness line in the page header states the age of what is on screen. "Never published" there
 means this account has never completed a push, not that the week is empty.

package/payload/platform/plugins/dispatch/skills/dispatch-page/template/planner.css

@@ -87,6 +87,66 @@
   font-size: 0.8rem;
 }
 
+/* Task 2511. A card is dragged to re-time or re-assign it. `grab` rather than
+   `move`, because the click that advances the status still works. */
+.pl-visit[draggable='true'] {
+  cursor: grab;
+}
+
+/* The cell under the pointer during a drag. `currentColor` and opacity rather
+   than a colour: portal.css owns the palette and rewrites its own :root, so a
+   literal here would render one install's colour on every other. */
+.pl-cell[data-over='true'] {
+  outline: 2px dashed currentColor;
+  outline-offset: -2px;
+}
+
+.pl-allocate {
+  margin-top: 0.75rem;
+  padding: 0.6rem 0.75rem;
+  border: 1px solid currentColor;
+  border-radius: 0.4rem;
+  position: relative;
+}
+
+.pl-allocate-close {
+  position: absolute;
+  top: 0.3rem;
+  right: 0.4rem;
+}
+
+.pl-allocate-head {
+  font-size: 0.82rem;
+  font-weight: 600;
+  margin: 0 0 0.4rem;
+  /* Room for the close button, which is positioned over this corner. */
+  padding-right: 2rem;
+}
+
+.pl-allocate-list {
+  list-style: none;
+  margin: 0;
+  padding: 0;
+  font-size: 0.78rem;
+}
+
+/* An excluded worker is dimmed rather than hidden. Hiding them would leave
+   `offered=0` with no explanation, which is the shape a quiet day and an
+   unstaffable job type share. */
+.pl-candidate[data-kind='excluded'] {
+  opacity: 0.6;
+}
+
+.pl-candidate + .pl-candidate {
+  margin-top: 0.2rem;
+}
+
+.pl-record {
+  font-size: 0.78rem;
+  margin: 0.5rem 0 0;
+  opacity: 0.85;
+}
+
 @media (max-width: 720px) {
   /* Seven readable columns that scroll, rather than seven unreadable slivers
      that do not. The scroll is the GRID's, never the page's. */

package/payload/platform/plugins/dispatch/skills/dispatch-page/template/planner.html

@@ -52,6 +52,19 @@
         </header>
         <div class="pl-grid" id="pl-grid"></div>
         <p class="pl-unplaceable" id="pl-unplaceable" hidden></p>
+
+        <!-- One record at a time: who may be sent to it, why the others may
+             not, and what has been recorded against it so far. Everything here
+             is rendered from what /api/visits returned. The page holds no rule
+             about who is qualified, who clashes, or which moves are legal. -->
+        <section id="pl-allocate" class="pl-allocate" hidden>
+          <button class="dp-iconbtn pl-allocate-close" id="pl-allocate-close" type="button">
+            &#215;
+          </button>
+          <p class="pl-allocate-head" id="pl-allocate-head"></p>
+          <ul class="pl-allocate-list" id="pl-allocate-list"></ul>
+          <p class="pl-record" id="pl-record"></p>
+        </section>
       </section>
     </main>
     <script src="/planner.js"></script>