[Promote][things-tokens #1] feat(things,tokens): re-land hidden 🕵️ links + PAT GET bridge + custom audiences 🎭 (#413/#431 never reached develop) (#613)

[lopugit]

✅ Develop S3 preview ready

• Commit: c0f7f3a6
• Environment: Vercel Custom Environment develop
• Preview: https://pr-680.previews.dev.thingtime.com
• Last successfully built: 08/09 00:13 AEST (Australia/Melbourne)
• Immutable deployment: https://thingtime-7e3oy4tqy-lopugits-projects.vercel.app
• Vercel status: open deployment

The alias passed the develop bucket CORS preflight and a final live PR/SHA fence.

Generic Vercel Preview deployments use the shared development runtime; this controller adds the stable exact-SHA alias and marker-scoped cleanup.

Automated promotion of #613 from develop to main, opened by the Promote features to main workflow for release review.

Source

Source PR	#613 — feat(things,tokens): re-land hidden 🕵️ links + PAT GET bridge + custom audiences 🎭 (#413/#431 never reached develop)
Author	@lopugit
Merged into develop	2026-09-07T05:39:09Z
Merge commit	a5093ead8fecd085f757a7dc8d6a3b1e9bb1f1bb
Head branch	claude/hidden-links-custom-audiences-reland

How to review

• This PR re-applies the source PR's exact changes onto main
  (git cherry-pick -x; each commit message references the original SHA).
• Merge it normally to release the change to main —
  the Sync main into develop workflow keeps develop aligned afterwards.
• Close it (without merging) to keep the change out of main;
  the workflow never recreates a closed promotion (reopen it to change your mind).
• Prefer shipping everything at once? Merge the standing omnibus
  Promote develop to main PR instead — this PR's diff then becomes
  empty and the workflow closes it automatically.

---

🤖 Generated by the promote-features-to-main workflow.

[github-actions]

✅ Source-lineage verification currently passes.

Source PR #613's exact patch is provably present at the current develop tip ce2274e9d20e6a887f6104bf02eec2dd9c84617e.

[lopugit]

✅ Develop S3 preview ready

• Commit: c0f7f3a6
• Environment: Vercel Custom Environment develop
• Preview: https://pr-680.previews.dev.thingtime.com
• Last successfully built: 08/09 00:13 AEST (Australia/Melbourne)
• Immutable deployment: https://thingtime-7e3oy4tqy-lopugits-projects.vercel.app
• Vercel status: open deployment

The alias passed the develop bucket CORS preflight and a final live PR/SHA fence.

Generic Vercel Preview deployments use the shared development runtime; this controller adds the stable exact-SHA alias and marker-scoped cleanup.

[github-actions]

🤖 Lopu live PR update

Status: ✅ Lopu finished — this PR is mergeable

Current phase: GitHub verified the published branch result

Estimated completion: Done — no further active-work ETA.

Time conversion (UTC source)

Moment	UTC	Los Angeles	Melbourne
Updated	2026-09-07 07:43 UTC (UTC+00:00)	2026-09-07 00:43 PDT (UTC-07:00)	2026-09-07 17:43 AEST (UTC+10:00)

Los Angeles and Melbourne use their real IANA time zones, so PDT/PST and AEST/AEDT offsets change automatically.

Lopu queue and PR pulse

Scope	Metric	Count
Repository	Open PRs	29
Repository	Conflicting	3
Repository	Out-of-date with target	1
Repository	GitHub state unknown	4
Repository	Part of an open stack	2
Repository	Touch files changed by another open PR	20
Repository	Target a non-root branch without an open parent PR	0
This resolver batch	Admitted snapshots	7
This resolver batch	Currently resolving	0
This resolver batch	Waiting	0
This resolver batch	Finished	7

Related PR context

• Stack: No open parent or child PR currently links to this branch.
• Target: main is a repository root/integration branch.
• Changed-file overlap: 37 changed files are also touched by #10, #295, #564, #590, #595, #607, #611, #638, #662, #665, #681, #682.

Exact branch pair: main → promote/pr-613-hidden-links-custom-audiences-reland--to-main.

Timeline

• 05:53 UTC — Detected that main needs to be merged into promote/pr-613-hidden-links-custom-audiences-reland--to-main; assigning the exact snapshot to the resolver queue.
• 06:04 UTC — Still safely queued behind earlier admitted Lopu work; no duplicate resolver was spawned.
• 06:08 UTC — Still safely queued behind earlier admitted Lopu work; no duplicate resolver was spawned.
• 06:15 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 06:19 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 06:25 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 06:29 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 06:36 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 06:40 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 06:46 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 06:51 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 06:57 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 07:02 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 07:08 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 07:10 UTC — Rebuilding Graphify structure and semantic context.
• 07:12 UTC — The resolver worker completed successfully and GitHub now reports this PR as mergeable.
• 07:13 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 07:23 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 07:33 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 07:43 UTC — The resolver worker completed successfully and GitHub now reports this PR as mergeable.

Technical run details — optional; this comment is the human-facing source of truth.

[github-actions]

🤖 Lopu live PR update

Status: ✅ Lopu finished — this PR is mergeable

Current phase: GitHub verified the published branch result

Estimated completion: Done — no further active-work ETA.

Time conversion (UTC source)

Moment	UTC	Los Angeles	Melbourne
Updated	2026-09-07 14:54 UTC (UTC+00:00)	2026-09-07 07:54 PDT (UTC-07:00)	2026-09-08 00:54 AEST (UTC+10:00)

Los Angeles and Melbourne use their real IANA time zones, so PDT/PST and AEST/AEDT offsets change automatically.

Lopu queue and PR pulse

Scope	Metric	Count
Repository	Open PRs	27
Repository	Conflicting	7
Repository	Out-of-date with target	1
Repository	GitHub state unknown	4
Repository	Part of an open stack	2
Repository	Touch files changed by another open PR	22
Repository	Target a non-root branch without an open parent PR	0
This resolver batch	Admitted snapshots	10
This resolver batch	Currently resolving	1
This resolver batch	Waiting	1
This resolver batch	Finished	8

Related PR context

• Stack: No open parent or child PR currently links to this branch.
• Target: main is a repository root/integration branch.
• Changed-file overlap: 38 changed files are also touched by #10, #295, #564, #590, #595, #602, #607, #611, #631, #659, #660, #662, +4 more.

Exact branch pair: main → promote/pr-613-hidden-links-custom-audiences-reland--to-main.

Timeline

• 12:18 UTC — Detected conflicts between main and promote/pr-613-hidden-links-custom-audiences-reland--to-main; assigning the exact snapshot to the resolver queue.
• 12:29 UTC — Still safely queued behind earlier admitted Lopu work; no duplicate resolver was spawned.
• 12:40 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 12:51 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 13:02 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 13:12 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 13:23 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 13:34 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 13:45 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 13:49 UTC — Using repository context to resolve the conflict semantics.
• 13:55 UTC — Regenerating the lockfile deterministically.
• 13:56 UTC — Rebuilding Graphify structure and semantic context.
• 14:06 UTC — 10-minute check-in: still working — Rebuilding Graphify structure and semantic context.
• 14:10 UTC — Working inside the isolated resolver environment.
• 14:12 UTC — The resolver worker completed successfully and GitHub now reports this PR as mergeable.
• 14:22 UTC — The resolver worker completed successfully and GitHub now reports this PR as mergeable.
• 14:32 UTC — The resolver worker completed successfully and GitHub now reports this PR as mergeable.
• 14:43 UTC — The resolver worker completed successfully and GitHub now reports this PR as mergeable.
• 14:54 UTC — The resolver worker completed successfully and GitHub now reports this PR as mergeable.

Technical run details — optional; this comment is the human-facing source of truth.

[github-actions]

🤝 Merged main into promote/pr-613-hidden-links-custom-audiences-reland--to-main — conflicts auto-resolved by Lopu's PR manager.

Conflicted files:

• graphify-out/snapshots/v1/9088e63452508f84ef83e9359cb11d967fde07f4be1cf435b8ece2eca594f05e/b49a638c7dd4d7fc264ea6fff5086f689416e3ae53167c201e093cd25be1f493/GRAPH_REPORT.md
• graphify-out/snapshots/v1/9088e63452508f84ef83e9359cb11d967fde07f4be1cf435b8ece2eca594f05e/b49a638c7dd4d7fc264ea6fff5086f689416e3ae53167c201e093cd25be1f493/cost.json
• graphify-out/snapshots/v1/9088e63452508f84ef83e9359cb11d967fde07f4be1cf435b8ece2eca594f05e/b49a638c7dd4d7fc264ea6fff5086f689416e3ae53167c201e093cd25be1f493/graph.json
• graphify-out/snapshots/v1/9088e63452508f84ef83e9359cb11d967fde07f4be1cf435b8ece2eca594f05e/b49a638c7dd4d7fc264ea6fff5086f689416e3ae53167c201e093cd25be1f493/manifest.json
• graphify-out/snapshots/v1/94433d17c176f2bdac5c0a3e90f71417ae106a476d7bd861d5d9b811b7fa25aa/a72fe54e341fcdc9153402f7ce761c58d7f7269bd5a972f94ac68e85ffc25a27/GRAPH_REPORT.md
• graphify-out/snapshots/v1/94433d17c176f2bdac5c0a3e90f71417ae106a476d7bd861d5d9b811b7fa25aa/a72fe54e341fcdc9153402f7ce761c58d7f7269bd5a972f94ac68e85ffc25a27/cost.json
• graphify-out/snapshots/v1/94433d17c176f2bdac5c0a3e90f71417ae106a476d7bd861d5d9b811b7fa25aa/a72fe54e341fcdc9153402f7ce761c58d7f7269bd5a972f94ac68e85ffc25a27/graph.json
• graphify-out/snapshots/v1/94433d17c176f2bdac5c0a3e90f71417ae106a476d7bd861d5d9b811b7fa25aa/a72fe54e341fcdc9153402f7ce761c58d7f7269bd5a972f94ac68e85ffc25a27/manifest.json
• graphify-out/snapshots/v1/984082b969db496ff66401bac879fdb80deaaf6e9bbcbca737c0a5b151cc3df8/3a0fc01eb858b55489f2a370c4441d91c18d46721a15d509de55783b4c5ee522/GRAPH_REPORT.md
• graphify-out/snapshots/v1/984082b969db496ff66401bac879fdb80deaaf6e9bbcbca737c0a5b151cc3df8/3a0fc01eb858b55489f2a370c4441d91c18d46721a15d509de55783b4c5ee522/cost.json
• graphify-out/snapshots/v1/984082b969db496ff66401bac879fdb80deaaf6e9bbcbca737c0a5b151cc3df8/3a0fc01eb858b55489f2a370c4441d91c18d46721a15d509de55783b4c5ee522/graph.json
• graphify-out/snapshots/v1/984082b969db496ff66401bac879fdb80deaaf6e9bbcbca737c0a5b151cc3df8/3a0fc01eb858b55489f2a370c4441d91c18d46721a15d509de55783b4c5ee522/manifest.json
• remix/app/api/utils/things/things.ts
• remix/app/components/Feed/PostCard.tsx
• remix/app/components/Feed/PostComposer.tsx
• remix/app/hooks/useApi.tsx

graphify-out/ was reset wholesale to the main side (repo rule: one side, never mixed — the graph merge driver is unavailable in CI).

Rebuilt and committed the merged code graph with graphify update .. LLM semantic extraction was attempted afterward but failed; the valid structural result was preserved (see the workflow log).

Please review the merge commit before relying on it.