coilyco-flight-deck/ward

Fork 0

Humanize user-visible ward timestamps #690

New issue

Open

opened 2026-07-08 19:32:17 +00:00 by coilyco-ops · 5 comments

coilyco-ops commented

2026-07-08 19:32:17 +00:00

Member

Goal

Humanize every user-visible timestamp ward emits.

Kai's preferred format is:

8th July 2026 12:28 PM PDT (UTC+WhateverItIs)

The first noticed case is the ward agent reservation comment, which currently emits ISO-style timestamps such as reserved 2026-07-08T19:29:28Z.

Do

Inventory user-visible timestamp emission paths in ward. Start with agent reservation comments, dispatch/broker comments, failure comments, reaper/salvage comments, director status output, and any issue comments ward writes.
Add a shared timestamp formatter instead of one-off string rewrites.
Use ordinal day numbers (8th), full month names, 12-hour time with AM/PM, local timezone abbreviation, and the UTC offset in parentheses.
Preserve machine-readable timestamps only where an API, serialized state, audit log, filename, or test fixture requires stable parseable values. This request is for human-facing output, not storage protocols.
Update tests that assert reservation/comment text.
Add focused coverage for the preferred format, including ordinal suffixes and UTC offsets.

Acceptance

A reservation comment reads like reserved 8th July 2026 12:28 PM PDT (UTC-07:00) rather than reserved 2026-07-08T19:28:00Z.
Other human-facing ward comments and status lines use the same formatter.
Audit logs, filenames, API payload fields, and other machine-facing timestamps stay parseable and stable.
ward exec test passes.

Filed from the read-only director surface after Kai called out the reservation comment timestamp.

## Goal Humanize every user-visible timestamp ward emits. Kai's preferred format is: ```text 8th July 2026 12:28 PM PDT (UTC+WhateverItIs) ``` The first noticed case is the `ward agent` reservation comment, which currently emits ISO-style timestamps such as `reserved 2026-07-08T19:29:28Z`. ## Do * Inventory user-visible timestamp emission paths in ward. Start with agent reservation comments, dispatch/broker comments, failure comments, reaper/salvage comments, director status output, and any issue comments ward writes. * Add a shared timestamp formatter instead of one-off string rewrites. * Use ordinal day numbers (`8th`), full month names, 12-hour time with AM/PM, local timezone abbreviation, and the UTC offset in parentheses. * Preserve machine-readable timestamps only where an API, serialized state, audit log, filename, or test fixture requires stable parseable values. This request is for human-facing output, not storage protocols. * Update tests that assert reservation/comment text. * Add focused coverage for the preferred format, including ordinal suffixes and UTC offsets. ## Acceptance * A reservation comment reads like `reserved 8th July 2026 12:28 PM PDT (UTC-07:00)` rather than `reserved 2026-07-08T19:28:00Z`. * Other human-facing ward comments and status lines use the same formatter. * Audit logs, filenames, API payload fields, and other machine-facing timestamps stay parseable and stable. * `ward exec test` passes. Filed from the read-only director surface after Kai called out the reservation comment timestamp.

coilyco-ops commented

2026-07-08 19:32:24 +00:00

Author

Member

🔒 Reserved by ward agent --harness codex — container engineer-codex-ward-690 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-08T19:32:22Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL); --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/ward#690 · branch issue-690 · harness codex · workflow direct-main
Run: engineer-codex-ward-690 · ward v0.463.0 · dispatched 2026-07-08T19:32:22Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.463.0).

— Codex, via ward agent

🔒 Reserved by `ward agent --harness codex` — container `engineer-codex-ward-690` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-08T19:32:22Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL); `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh** — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/ward#690` · branch `issue-690` · harness `codex` · workflow `direct-main` - **Run:** `engineer-codex-ward-690` · ward `v0.463.0` · dispatched `2026-07-08T19:32:22Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.463.0). </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue

2026-07-08 19:38:12 +00:00

Update Codex launch adapter for current codex exec flags #691

coilyco-ops commented

2026-07-08 21:14:38 +00:00

Author

Member

🔒 Reserved by ward agent --harness codex — container engineer-codex-ward-690 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-08T21:14:36Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL); --force overrides.

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/ward#690 · branch issue-690 · harness codex · workflow direct-main
Run: engineer-codex-ward-690 · ward v0.463.0 · dispatched 2026-07-08T21:14:36Z
Comment thread: 0 included in the pre-flight read, 1 stripped (ward's own automated comments).
- stripped: @coilyco-ops (2026-07-08T19:32:24Z)

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.463.0).

— Codex, via ward agent

🔒 Reserved by `ward agent --harness codex` — container `engineer-codex-ward-690` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-08T21:14:36Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL); `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh** — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/ward#690` · branch `issue-690` · harness `codex` · workflow `direct-main` - **Run:** `engineer-codex-ward-690` · ward `v0.463.0` · dispatched `2026-07-08T21:14:36Z` - **Comment thread:** 0 included in the pre-flight read, 1 stripped (ward's own automated comments). - stripped: @coilyco-ops (2026-07-08T19:32:24Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.463.0). </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-08 21:55:53 +00:00

Author

Member

🔒 Reserved by ward agent --harness codex — container engineer-codex-ward-690 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-08T21:55:51Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL); --force overrides.

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/ward#690 · branch issue-690 · harness codex · workflow direct-main
Run: engineer-codex-ward-690 · ward v0.466.0 · dispatched 2026-07-08T21:55:51Z
Comment thread: 0 included in the pre-flight read, 2 stripped (ward's own automated comments).
- stripped: @coilyco-ops (2026-07-08T19:32:24Z), @coilyco-ops (2026-07-08T21:14:38Z)

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.466.0).

— Codex, via ward agent

🔒 Reserved by `ward agent --harness codex` — container `engineer-codex-ward-690` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-08T21:55:51Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL); `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh** — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/ward#690` · branch `issue-690` · harness `codex` · workflow `direct-main` - **Run:** `engineer-codex-ward-690` · ward `v0.466.0` · dispatched `2026-07-08T21:55:51Z` - **Comment thread:** 0 included in the pre-flight read, 2 stripped (ward's own automated comments). - stripped: @coilyco-ops (2026-07-08T19:32:24Z), @coilyco-ops (2026-07-08T21:14:38Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.466.0). </details>  — Codex, via `ward agent`

coilyco-ops added the

headless

labels

2026-07-09 18:09:24 +00:00

coilyco-ops added

consult

and removed

headless

labels

2026-07-10 09:00:37 +00:00

coilyco-ops commented

2026-07-10 09:00:40 +00:00

Author

Member

Fresh evidence from the 2026-07-10 director sweep:

warded list now works from a read-only director surface, but its user-visible timestamps are still ISO/RFC3339-style:

reserved: 2026-07-10T09:00:09.093207Z
started: 2026-07-10T09:00:11.344937801Z

Reservation comments are also still ISO-style, for example reserved 2026-07-10T09:00:09Z.

That confirms this issue is still current after ward#874 landed the list command. Please include ward agent list / warded list in the timestamp inventory alongside reservation, dispatch, broker, reaper, and director status output.

Fresh evidence from the 2026-07-10 director sweep: `warded list` now works from a read-only director surface, but its user-visible timestamps are still ISO/RFC3339-style: * `reserved: 2026-07-10T09:00:09.093207Z` * `started: 2026-07-10T09:00:11.344937801Z` Reservation comments are also still ISO-style, for example `reserved 2026-07-10T09:00:09Z`. That confirms this issue is still current after `ward#874` landed the list command. Please include `ward agent list` / `warded list` in the timestamp inventory alongside reservation, dispatch, broker, reaper, and director status output.

coilyco-ops commented

2026-07-10 09:00:46 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-ward-690 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-10T09:00:45Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL). --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/ward#690 · branch issue-690 · harness codex · workflow pull-requests-and-merge
Run: engineer-codex-ward-690 · ward v0.569.0 · dispatched 2026-07-10T09:00:45Z
Comment thread: 1 included in the pre-flight read, 3 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-10T09:00:40Z)
- stripped: @coilyco-ops (2026-07-08T19:32:24Z), @coilyco-ops (2026-07-08T21:14:38Z), @coilyco-ops (2026-07-08T21:55:53Z)

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.569.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-690` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T09:00:45Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL). `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/ward#690` · branch `issue-690` · harness `codex` · workflow `pull-requests-and-merge` - **Run:** `engineer-codex-ward-690` · ward `v0.569.0` · dispatched `2026-07-10T09:00:45Z` - **Comment thread:** 1 included in the pre-flight read, 3 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-10T09:00:40Z) - stripped: @coilyco-ops (2026-07-08T19:32:24Z), @coilyco-ops (2026-07-08T21:14:38Z), @coilyco-ops (2026-07-08T21:55:53Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.569.0). </details> </details>  — Codex, via `ward agent`