[hivecommons-hive]

YouTube moves the per-video feed <updated> stamp on its own schedule, and nothing in src/ renders it. Because the refresh script compared it when deciding whether to rewrite data/meeting-recordings.json, each bump cost a full refresh PR plus CI run for a timestamp-only diff (#495, #562 were exactly that).

Now an updatedAt-only difference keeps the committed record and the file is not rewritten. New recordings or changes to title/publishedAt/url/thumbnail/description still rewrite it and refresh the store updatedAt. The updatedAt key stays on disk, so there is no schema change. An in-process test covers both the no-rewrite and rewrite cases.

Closes #565

— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign clubanderson for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Deploy Preview for hivecommons-docs canceled.

Name	Link
🔨 Latest commit	06725f8
🔍 Latest deploy log	https://app.netlify.com/projects/hivecommons-docs/deploys/6ae76d71fbc6612897092fa1

[hivecommons-hive]

Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor.

hive/awaiting-ci: CI pending — sweep will merge when green.

---

🐝 Hive Agent: scanner | Instance: hosted-available-oke-11-placeholder-r05x | SHA: unknown

— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88

Review findings from reviewer (folded here because this head already carries its hive review):

Read scripts/update-meeting-recordings.ts at 06725f8 and the renderer. This looks correct to me.

• scripts/update-meeting-recordings.ts:140-151 — merged is built as { ...previous, ...recording }, so the stripped-updatedAt JSON.stringify comparison against previous sees identical key order; the equality is not key-order-fragile. A field the feed newly supplies (or changes) alters the serialisation and still falls through to byId.set, so the existing no-op check at :156-160 continues to trigger a rewrite for real changes.
• The feed dropping <updated> entirely yields recording.updatedAt === undefined, which is stripped before comparison → the committed record (with its stored updatedAt) is kept rather than rewritten. Reasonable, and consistent with the stated intent.
• grep -rn updatedAt src/ confirms nothing under src/components/community/MeetingsPage.tsx or src/config/community-meetings.ts reads the per-recording stamp, matching [scanner] bug: meeting-recordings refresh opens churn PRs when only YouTube's per-video updated timestamp moves #565.
• Verified the new test is a real guard: with scripts/update-meeting-recordings.ts reverted to main and the test kept, does not rewrite the store when only a recording's feed <updated> moved fails (expected "log" to be called with ['meeting recordings: 1 (unchanged)']); with the PR applied, all 9 cases pass.

Body matches the diff (updatedAt-only → no rewrite; title/publishedAt/url/thumbnail/description → rewrite + store updatedAt refresh; key kept on disk). Changelog fragment uses the fixed-<issue> name the guard requires.

Evidence bundle `#56606725f8` sha256:7aafa7bfe4d473ef1f8d0555e77132200752a1c51bae73c1d110abe05844a664 — download from the dashboard or `hivectl review evidence #566`.

[hivecommons-hive]

Read scripts/update-meeting-recordings.ts at 06725f8 plus the src/ consumers. Looks correct to me.

What I checked:

• Key-order safety of the JSON.stringify comparison (update-meeting-recordings.ts:142-148): merged = { ...previous, ...recording } keeps previous's key order and only appends keys previous lacked, so an equal-content record always stringifies identically; a newly-present field (e.g. a description that was previously absent) still differs and triggers a rewrite. updatedAt: undefined is dropped by JSON.stringify on both sides.
• When continue is taken, byId retains previous unchanged, so the downstream existingStable === nextStable check (:155-158) hits the unchanged path — that is the mechanism that stops the rewrite, and the new test asserts both that path and the title-change rewrite path.
• The issue's "nothing renders per-recording updatedAt" claim holds: grep -rn updatedAt src/ only hits shared-config and RelatedProjects types, not Recording.
• Pre-existing behaviour preserved: a feed entry with no <updated> still overwrites previous.updatedAt with undefined when other fields change, exactly as before this PR.

Body matches the diff; Closes #565 is the right link. No findings.

— hive: agent=reviewer-2 backend=copilot model=claude-fable-5.1 copilot=1.0.88