Skip to content

Sharpen recruiter-facing Relay copy and credit both builders - #45

Merged
sykosyber merged 2 commits into
mainfrom
cursor/recruiter-readme-4b22
Sep 6, 2026
Merged

sykosyber merged 2 commits into
mainfrom
cursor/recruiter-readme-4b22

Conversation

@sdcarlson

Copy link
Copy Markdown
Contributor

Problem and result

Recruiters opening this repo (or Seth’s / Mateo’s GitHub) need a product they can explain in one pass. The previous README led with setup caveats and only credited the lead engineer, so the product and the two-person team were easy to miss.

This updates the canonical public description so Relay reads as SyberLabs’ job-search product: a private review workspace that remembers researched roles, accepted drafts, and interview follow-ups. Assistants help write; Relay keeps the record. It does not send applications.

After merge, the scheduled public-copy sync will refresh the organization profile, Seth’s GitHub README, and the syberlabs.space Relay paragraph from the same source.

Evidence

  • Checks run and result: pnpm test — 100 passed, 0 failed. pnpm public-copy:check — project: current. oxlint on the generator and public-copy tests — clean.
  • User-visible proof: generated README block now names both maintainers and states the product in recruiter language; Team and Stack sections sit above local-run details.
  • Security, data migration, and rollback impact: copy and credit only. No schema, auth, or deployment change. Revert the commit to restore the previous public text.

Review

  • One issue owns this scope; unrelated changes are separate. (No ticket; recruiter-copy request.)
  • Tests exercise the changed behavior, including failure paths (peer credit + peerProfile URL validation).
  • No credentials, personal applications, or private research are included.
  • Agent findings are fixed or answered with evidence.
  • A maintainer other than the author will approve.
  • Public capabilities, integration limits and lead-engineer credit match docs/public-copy.json; run pnpm public-copy:check and follow docs/PUBLIC-COPY.md when these change.
Open in Web Open in Cursor 

Rewrite the canonical public description so GitHub visitors can tell
what Relay is, who built it, and that it is a review workspace rather
than an auto-applier. Keep the existing product contracts: exact draft
acceptance, owner-scoped history, and no application sending.

Co-authored-by: Seth Carlson <sdcarlson@users.noreply.github.com>
@sdcarlson
sdcarlson requested a review from sykosyber as a code owner September 6, 2026 01:43

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review (a884c15)

No actionable defects on this head. Copy, credit, and generator changes only. No auth, schema, workflow, or release-path edits.

Checked claims against adjacent contracts:

  • Exact acceptance, import-as-evidence, and no-send boundaries remain in the managed block and Why section.
  • live-loop matches product status Live loop (lib/domain.ts); follow-ups on Submitted/Live loop do not reset status (ARCHITECTURE.md).
  • “Verified facts” is the existing packet field, not a new verification claim. Claude/Notion/CSV verification limits still live in integrations/README.md.
  • peerProfile uses the same github.com HTTPS / no-credentials gate as leadProfile. Tests lock both maintainer URLs.
  • Hosting/rollback controls remain in docs/hosting.md; the README stack line matches package.json (React 19, Vinext).

Ran: node --test tests/public-copy.test.mjs (6 pass); pnpm public-copy:check (project: current).

Inspected only: PR diff vs 9296d9d; scripts/sync-public-copy.mjs render/URL checks; docs/public-copy.json vs README/LAUNCH; AGENTS.md + docs/threat-model.md. Did not run the full unit, API, or browser suites. GitHub CI at review time: Quality, Integration (api/production), Dependency security, Bundled agent contracts, and CodeQL success; Integration (browser) was still in progress.

Human approval remains mandatory. This review does not approve or merge.

Open in Web View Automation 

Sent by Cursor Automation: RELAY pull request review

@sykosyber sykosyber left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Partner Extra High review of a884c155b1d1910210a35b8c36186e98c4d2520f. Approving this SHA.

Independent of the High Fast comment on this head. Extra High is not merging.

Unique 6-file delta is copy, credit, and the public-copy generator/tests. No app/, auth, schema, workflow, or release-path change.

Traced:

  • Managed block still comes from docs/public-copy.json via scripts/sync-public-copy.mjs. Project and organization credit both maintainers. peerProfile is gated the same way as leadProfile (https: + github.com + no embedded credentials). Tests lock both URLs and reject javascript:, data:, other hosts, and user:pass@.
  • Product contracts in the generated block and Why/Team copy: exact accepted wording, imports stay research and cannot approve a draft, no application sending, no background account sync, fictional examples only. Claude’s “verified facts” is the existing packet field (integrations/connectors.mjs), not a claim that Relay independently verified employer facts.
  • live-loop in the capability line matches product status Live loop (lib/domain.ts). Follow-ups on Submitted / Live loop still do not reset status.
  • README stack names the intended architecture; Hosting still says the first production release needs verification. #3 stays open. This PR does not close #5 or #22.
  • Quality on this head includes pnpm public-copy:check (Quality succeeded).

Required CI is green, including combined CI, Quality, Integration (api/browser/production), CodeQL, and dependency security: Actions 34004624216.

This head is behind current main (includes landed #40). The unique copy files do not overlap that diagnostic work. Extra High is not merging; a later rebase needs a new SHA review.

@sykosyber sykosyber left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Partner Extra High review of b681fc3bf5496756085a3ff0b4f5372fba19b48b. Approving this SHA.

Independent of the High Fast comment, which was on a884c15. Extra High is not merging.

This head is a merge of current main (9296d9d, #40 diagnostics) into the previously reviewed copy commit a884c15. Unique vs main is still the same 6 files: copy, credit, and the public-copy generator/tests. No app/, auth, schema, workflow, or release-path change.

Unique blobs are identical to Extra High's prior review of a884c15:

  • docs/public-copy.json 0ca6850
  • scripts/sync-public-copy.mjs 87506a0
  • tests/public-copy.test.mjs 3afcefe
  • README.md f4e7ed3
  • LAUNCH.md 668ace7
  • docs/PUBLIC-COPY.md c05731b

Traced on this SHA:

  • Managed block still comes from docs/public-copy.json via scripts/sync-public-copy.mjs. Project and organization credit both maintainers. peerProfile is gated the same way as leadProfile (https: + github.com + no embedded credentials). Tests lock both URLs and reject javascript:, data:, other hosts, and user:pass@.
  • Product contracts in the generated block and Why/Team copy: exact accepted wording, imports stay research and cannot approve a draft, no application sending, no background account sync, fictional examples only. Claude's "verified facts" is the existing packet field, not a claim that Relay independently verified employer facts.
  • live-loop matches product status Live loop (lib/domain.ts). Follow-ups on Submitted / Live loop still do not reset status.
  • README stack names the intended architecture; Hosting still says the first production release needs verification. #3 stays open. This PR does not close #5 or #22.
  • .github/workflows/ci.yml stays permissions: contents: read. Quality on this head includes pnpm public-copy:check (Quality succeeded).

Required CI is green on this head, including combined CI, Quality, Integration (api/browser/production), CodeQL, and dependency security: Actions 34005228905.

Last-push approval needs this SHA, not the Extra High APPROVE that was submitted on a884c15 before the merge. Extra High is not merging.

@sdcarlson

Copy link
Copy Markdown
Contributor Author

Approval audit: GitHub attaches the approval to b681fc3, but its body explicitly approves only a884c15 and requests fresh SHA review after a later rebase. Please obtain confirmation naming the latest head before merge; I will not infer latest-head approval from the API attachment alone. Required checks are still completing.

@sykosyber

Copy link
Copy Markdown
Member

Confirmation for the approval audit: Extra High independently approved the current head by name in review 5123789140 on b681fc3bf5496756085a3ff0b4f5372fba19b48b.

That review is separate from 5123766073, which named a884c15 before the merge of main. GitHub can attach an older review to a later SHA; Extra High does not treat that attachment as last-push approval of b681fc3.

Required checks on b681fc3 completed successfully, including combined CI: Actions 34005228905. Extra High is not merging.

@sykosyber
sykosyber merged commit b6202e9 into main Sep 6, 2026
9 checks passed
@sykosyber
sykosyber deleted the cursor/recruiter-readme-4b22 branch September 6, 2026 02:03
cursor Bot pushed a commit that referenced this pull request Sep 6, 2026
…ities.

Resolve #49 conflicts against #45 public-copy: preserve dual-builder credit
and recruiter wording, then add fact-ledger, batch review, planning, board
pulls, and receipted outcomes. Regenerate the managed README block. Open a
job from the existing queue for the dirty-navigation Chromium check.

Co-authored-by: sykosyber <sykosyber@users.noreply.github.com>
@cursor cursor Bot mentioned this pull request Sep 6, 2026
4 of 6 tasks
sdcarlson pushed a commit that referenced this pull request Sep 6, 2026
<!-- CURSOR_AGENT_PR_BODY_BEGIN -->
## Problem and result

Closes #47
Closes #48

The cleanup queue that deferred closed PR #26 has landed. Open PR #46
already contains #26, but it cannot merge: it conflicts with current
`main` on `README.md`, `app/globals.css`, `integrations/connectors.mjs`,
and `package.json`, and it still carries a stale toolchain.

This PR reconciles that work onto current `main` (`ad4bb8f`, including
#44, #45, and #51). After merge, a signed-in applicant can:

- Keep a verified fact ledger and learned style rules that **refuse**
unsupported agent claims at the API (nothing invented reaches the review
queue).
- Review logged drafts in batches; staging is not acceptance and never
sends an application.
- Set preferences by choosing between real postings, then get a weekly
plan that maximises the expected value of the **best single offer**
under an attention budget.
- Pull public Greenhouse and Lever boards onto existing job identity
(read-only, no credentials).
- Record outcomes with a **receipt** before a submission counts toward
reply rates, including an explicit Track action for a newly accepted
Ready job. Ended applications cannot be reopened by import.

Who needed this: people using assistants at volume, and anyone whose
Live loop currently has no honest terminal/receipt model. What failed
before: #26 was closed as deferred-not-rejected; #46 was blocked on
conflicts. What they can do afterward: use `/profile`, `/review`,
`/preferences`, `/plan`, and `/track` on current `main` without dropping
session expiry, dirty-editor navigation, null-URL packet identity,
recruiter-facing copy, dual-builder credit, or public-copy generation.

Supersedes reopening #26. Do not merge conflicted #46 directly. PR #46
commits can stay until this replacement is accepted.

## Evidence

- Prior `3e081b4` blockers remain cleared: Offer-to-Accepted,
Held-to-Accepted empty draft, empty `delta:[]` 400, stale outcome 409
with versioned Track caller.
- Review 5123899043 merge blockers, fixed on `49ff152` (ponytail list
not applied):
1. `POST /api/preferences` no longer persists a client `delta`. Winner
and loser job keys are the record; the comparison is recomputed from
owned Held posting features. `delta: []` and four repeated `[1e308,…]`
payloads return 400 and leave `answered` unchanged. The preferences UI
sends only those two keys.
2. `numberIsAboutEmployer` is deleted. Every digit in a non-question is
a claim. Mixed-subject sentences and `I read your 2024 post on storage
engines.` refuse `validateDraftLog` with `cited: []`.
3. Track GET prep includes Ready jobs. Ready rows expose a receipt field
and **Record submission** (`kind: 'submitted'`, `version`, `receipt`)
through `app/track/page.tsx`. Playwright covers that caller. Seth
independently verified the receipt UI on `179df12` and resolved those
threads. Overflow on `179df12` was also resolved as bounded `[-1,1]`
components.
- Review 5123907359 on superseded `179df12`: nearest-subject still
missed `I bring your team 15 years of experience.` and `I offer your
company 12 years of experience.` Those sentences reject on `49ff152`
(exemption deleted). `91e7e57` adds those two strings as regressions.
The parser was not expanded.
- GitHub Integration (production) on `91e7e57` failed at `owner-a save`
with Wrangler `worker restarted mid-request` (503, process still
running). Same tree passes `pnpm test:production` locally. `e5c00b3`
retriggers required CI only; #22 stays a separate investigation.
- Checks run and result (local, including `e5c00b3` production re-run):
`pnpm lint` clean; `pnpm typecheck` clean; `pnpm test` 174/174; `pnpm
public-copy:check` current; `pnpm build` succeeded; `pnpm test:api`
passed; `pnpm test:calibration` passed; `pnpm test:orchestration`
passed; `pnpm test:e2e` 8/8; `pnpm test:production` passed including
migrations `0000`–`0004`.
- Review re-requested on this head. Do not reopen #26 or merge #46. Do
not wait on hosting #3.

## Review

- [x] One issue owns this scope; unrelated changes are separate.
- [x] Tests exercise the changed behavior, including failure paths.
- [x] No credentials, personal applications, or private research are
included.
- [ ] Agent findings are fixed or answered with evidence.
- [ ] A maintainer other than the author will approve.

- [x] Public capabilities, integration limits and lead-engineer credit
match `docs/public-copy.json`; run `pnpm public-copy:check` and follow
`docs/PUBLIC-COPY.md` when these change.

### Landing notes for review

- Merged `origin/main` (`ad4bb8f`) and resolved public copy in favor of
#45 wording and credit, plus this PR's capabilities.
- Kept current `package.json` (Apache-2.0, React 19.2.8, Vinext beta.9,
Node 24). Did not restore unused UI-kit deps from #46.
- Dirty-nav confirm on `/profile`, `/review`, `/preferences`, `/plan`,
`/track`.
- Terminal statuses are workspace filters and protected saves; they are
not import statuses. Offer can still be accepted as an outcome.
- Live suites `tests/api.test.mjs`, `tests/calibration.test.mjs`, and
`tests/orchestration.test.mjs` each run on a dedicated freshly migrated
D1 in required CI.

Standing instruction for agents: #47 and #48 must not be deferred behind
hosting #3 or experiment #5.
<!-- CURSOR_AGENT_PR_BODY_END -->

<div><a
href="https://cursor.com/agents/bc-3877d527-b5e4-46d7-8c5f-573418309ece?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-web-light.png"><img
alt="Open in Web" width="114" height="28"
src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a
href="https://cursor.com/background-agent?bcId=bc-3877d527-b5e4-46d7-8c5f-573418309ece&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img
alt="Open in Cursor" width="131" height="28"
src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div>

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: sykosyber <sykosyber@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants