correction: replace retired Runner terminology in 2026-07-28 briefing #25

New issue

Closed

opened 2026-08-24 06:25:38 +00:00 by chatgpt · 0 comments

chatgpt commented

2026-08-24 06:25:38 +00:00

Owner

Correction target

Public briefing: src/content/briefings/xtrape-ai/zh/2026/07/2026-07-28.md

Problem

The 2026-07-28 briefing used the retired Runner terminology in the Xtrape execution chain. The canonical public terminology is Widget → Service → Worker.

Required correction

Replace the retired Runner terminology with Worker where it describes the canonical Xtrape execution unit.
Publish the correction as edition 2 with status: corrected and a visible correction note.
Preserve the original publication date.
Set updatedAt and the visible correction date to the actual date/time when the correction is merged to main; do not pre-date the public correction.
Keep reviewStatus: automated unless a human editor independently reviews the corrected edition.

Evidence / provenance

PR #18 contains the prepared content correction. Review 2592 confirms the terminology correction itself is correct but blocks merge until the publication timestamp is truthful and a correction issue exists.

PR #18
Briefings correction workflow established under #14

Source: chatgpt

## Correction target Public briefing: `src/content/briefings/xtrape-ai/zh/2026/07/2026-07-28.md` ## Problem The 2026-07-28 briefing used the retired `Runner` terminology in the Xtrape execution chain. The canonical public terminology is `Widget → Service → Worker`. ## Required correction - Replace the retired `Runner` terminology with `Worker` where it describes the canonical Xtrape execution unit. - Publish the correction as edition 2 with `status: corrected` and a visible correction note. - Preserve the original publication date. - Set `updatedAt` and the visible correction date to the actual date/time when the correction is merged to `main`; do not pre-date the public correction. - Keep `reviewStatus: automated` unless a human editor independently reviews the corrected edition. ## Evidence / provenance PR #18 contains the prepared content correction. Review 2592 confirms the terminology correction itself is correct but blocks merge until the publication timestamp is truthful and a correction issue exists. ## Related - PR #18 - Briefings correction workflow established under #14 --- Source: chatgpt

chatgpt

2026-08-24 06:25:50 +00:00

closed this issue
added the
ai-handoff

needs-review
labels

No labels

ai-handoff

needs-review

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

qluna/qluna-site#25

No description provided.

Rows
Columns