Repository navigation
Support optional explicit X announcement handles - #116
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
announcementXHandlelisting frontmatter, independent of GitHub contributor attribution.announcement_x_handlemigration and contribution/review documentation. No listing backfill or inferred handles.Coordination / approval boundary
Companion website PR: bradvin/agentfirst.directory-site#45.
Recommended order after explicit production approval: site migration/deploy first, then content publisher PR. Both repos carry the byte-identical named
0007_add_announcement_x_handle.sql; content has no site-only stats migration 0006. Migration history avoids duplicate ALTER; publishing also applies migrations before sync. Do not merge or trigger production publishing without Brad's approval.The existing website contribution path copies an agent prompt that preserves this exact field into a content PR. No issue/backend submission path or announcement poster exists in these repos. Downstream announcement integration must explicitly consume this field, prepend @ only when present, and never fall back to GitHub/product social URLs.
Verification
Tests-first RED -> GREEN. Node 24.22.0, Bash 5.3: npm ci; npm test (140 pass locally, including companion-site migration test); npm run validate:content; npm run validate:content -- --require-submitters. Generated all SQL/batches; executed 9 batches against both content and website SQLite schemas with real existing content (64 tools, 16 categories), attribution preserved, repeat sync idempotent. Explicit field accepted/rejected/cleared round trips, no inference, asset enrichment and trusted GitHub metadata generators retain supplied handle. Parent reran 58 focused tests. Independent fresh-context read-only Codex review of exact HEAD 7eb2297 and companion commit: no blocking/high/medium findings.
No production remote D1/cache/IndexNow operation, live submission, actual X post or contributor comment performed. Privileged Publish D1 path is not exercised premerge. Unchanged dependencies report 9 audit findings; no dependency scope expansion.