plresearch-org · edit-ai-opportunity-spaces-r6 · round 6

Round 6: fix byline placement + expand to all CMS pages

@daviddao

Reported in prod: daviddao.org edited Economies & Governance, the audit record landed on blewit.us-west.host.bsky.network, the indexer picked it up — yet the byline stubbornly refused to appear. Two bugs stacked on top of each other: r5 only wired the byline onto opportunity-space detail pages (not area pages), and when I extended it on the quick-fix commit I put the byline as a sibling of the fixed-positioned <EditPageButton>, which dropped it ~2500 px down the document.

Date: 2026-04-20 · Target: Economies & Governance · Previous: r5 (pass) · pass

---

Headline result

The two bugs

#	Bug	Effect	Fix
B1	r5 only imported <EditHistoryByline> in the 4 opportunity-space detail pages, not on area pages, about, or outreach.	daviddao’s edit of the area-economies-governance page record landed on her PDS and in the indexer, but the target surface (/areas/economies-governance/) had no byline to render it.	Wire <PageEditHistoryByline rkey=…> on 7 additional page routes.
B2	First attempt to wire the byline put it as a sibling of <EditPageButton>.	<EditPageButton> is position: fixed & its JSX lives near the end of each page file. The byline <div> fell wherever EditPageButton sat in source order — for the E&G page, top: 2500.5px out of a ~3000px page height. Cosmetically invisible.	Move the byline to sit directly below <Breadcrumb>, where it visually anchors as a subtitle.

B2 was visible in the DOM (get html showed it existed) but not in screenshots. The computed getBoundingClientRect() confirmed it:

// browser console on /areas/economies-governance/ after the broken deploy
> document.querySelector('.mt-4 > .flex').getBoundingClientRect()
{ top: 2500.5, left: 88, width: 1104, height: 20 }

Opportunity-space detail pages happened to work in r5 because their <EditPageButton> sat right after <Breadcrumb> in JSX — pure coincidence. The 7 newer pages all had content between the two.

What changed

Two commits on plresearch.org@main:

Pages that now render the byline (when the target record has at least one audit event):

• / — actually dropped; no breadcrumb and the full-bleed hero has no sane anchor point. Admins still have /admin for history.
• /about/
• /areas/
• /areas/[slug]/ — covers the 3 generic area pages
• /areas/economies-governance/
• /areas/economies-governance/subareas/
• /areas/economies-governance/impact/
• /outreach/collaboration/
• 4× /areas/*/opportunity-spaces/[slug]/ — unchanged from r5

Walkthrough

Verification

daviddao’s raw audit record, still on her PDS, cryptographically signed by her key:

$ curl -sG "https://blewit.us-west.host.bsky.network/xrpc/com.atproto.repo.listRecords" \
    --data-urlencode "repo=did:plc:qc42fmqqlsmdq7jiypiiigww" \
    --data-urlencode "collection=org.plresearch.editEvent" | jq '.records[0].value'
{
  "$type":    "org.plresearch.editEvent",
  "editor":   "did:plc:qc42fmqqlsmdq7jiypiiigww",
  "editorHandle": "daviddao.org",
  "target":   "at://did:plc:pgwr6hkosgznfl5nz7egajei/org.plresearch.page/area-economies-governance",
  "targetCid": "bafyreihukoqyujcafnsexgpzu7cnmvvrwd3tfmsgvwbznbi5ntn4xum6mi",
  "collection": "org.plresearch.page",
  "changedFields": ["sections"],
  "editedAt": "2026-04-20T21:55:12.319Z"
}

After the r6 deploy, our API surfaces it:

$ curl -s "https://www.plresearch.org/api/edit-history?target=at://…/org.plresearch.page/area-economies-governance" | jq '.count, .events[0].editorHandle, .events[0].changedFields'
1
"daviddao.org"
["sections"]

Findings

Reproducing