Require By the builder expansion for every website change

[erinepshovel-code]

Summary

Implements the canonical website-builder-journal skill from skill-lib commit 0981aed7695ba2675d5de35ef43ba734e94adea0.

Every website modification transaction now requires at least one appended By the builder entry recording:

• date;
• time with explicit UTC offset;
• exact runtime model;
• model-authored body.

Subject matter remains wholly at the model's discretion. There is no changelog requirement, mandatory title, minimum length, recurring theme, or patch-summary template.

Enforcement

scripts/check-builder-history.mjs now:

• preserves every published entry exactly and in order;
• grandfathers the 2026-09-17 legacy entry without rewriting it;
• requires time + exact model on every newly appended entry;
• rejects obvious generic model labels;
• detects tracked and untracked repository changes;
• fails any non-journal website diff with zero appended entries;
• treats a journal-only append as self-satisfying, preventing infinite recursion.

The existing npm run check path already runs npm run check:builder, so the rule is part of PR and release validation.

Presentation

/by-the-builder/ is now a static-first nested <details> / <summary> tree:

• root journal disclosure;
• individually collapsible entries;
• date, time, and exact model visible in each new entry summary;
• legacy entry visibly marked rather than retroactively altered.

This change's required builder entry

• date: 2026-09-23
• time: 23:38:45-07:00
• exact model: GPT-5.6 Sol
• subject chosen independently by the model.

Validation

Focused tests cover:

• non-journal diff with no entry → fail;
• valid appended entry → pass;
• journal-only append → no recursive requirement;
• untracked modifications → trigger;
• legacy prefix immutability;
• date/time/model schema;
• generic model labels;
• generated collapsible tree;
• exact canonical skill commit consumption.

The normal full website release gate remains authoritative before merge.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.