Skip to content

feat(docs): LinkedIn bot-detection notes + AI tooling + harness sync#8

Merged
saagpatel merged 1 commit into
mainfrom
feat/linkedin-bot-detection-doc
May 11, 2026
Merged

feat(docs): LinkedIn bot-detection notes + AI tooling + harness sync#8
saagpatel merged 1 commit into
mainfrom
feat/linkedin-bot-detection-doc

Conversation

@saagpatel
Copy link
Copy Markdown
Owner

Summary

  • docs/LINKEDIN-BOT-DETECTION.md — new. Documents how the LinkedIn adapter avoids bot detection (persistent real-browser session, hard rate limits, randomized delays, Easy Apply only, real DOM interactions), what still triggers detection (CAPTCHA mid-flow, fingerprint reuse, DOM drift, multi-restart volume), and an operator playbook. Sourced from sidecar/src/adapters/linkedin.py.
  • docs/developer/ai-tooling.md — new. Claude Code commands and task-focused agents.
  • docs/developer/README.md — link the new ai-tooling doc into the dev index.
  • AGENTS.md, CLAUDE.md — portfolio-context blocks.
  • package.json, src-tauri/tauri.conf.json — prettier auto-format sync (spaces→tabs), no logic change.
  • package-lock.json — minor lockfile drift.
  • src-tauri/binaries/jcc-sidecar-aarch64-apple-darwin — rebuilt sidecar binary (current arm64 build).

Context

Resolves part of the overdue packet "GitHub finish packet" — task "Finish validation: prove the real 5-job batch, document LinkedIn bot-detection behavior, then revisit the default-branch posture".

Specifically: the LinkedIn bot-detection documentation is now complete. The remaining packet items (5-job live batch proof + default-branch posture decision) require operator-side action and are out of this PR's scope.

Note

pnpm-lock.yaml diverged drastically (3855+/1293-) and is left uncommitted here. Recommend resolving it in a dedicated dependency-hygiene PR after auditing whether the regeneration was intentional.

docs/LINKEDIN-BOT-DETECTION.md: how the LinkedIn adapter avoids bot

detection (persistent real-browser session, hard rate limits,

randomized delays, Easy Apply only), what still triggers detection

(CAPTCHA mid-flow, fingerprint reuse, DOM drift), operator playbook.

Sourced from sidecar/src/adapters/linkedin.py.

docs/developer/ai-tooling.md: Claude Code commands + task agents.

docs/developer/README.md: link the new ai-tooling doc.

AGENTS.md, CLAUDE.md: portfolio-context blocks.

package.json, src-tauri/tauri.conf.json: prettier auto-format sync.

package-lock.json: minor lockfile drift.

src-tauri/binaries/jcc-sidecar-aarch64-apple-darwin: rebuilt sidecar.

pnpm-lock.yaml diverged drastically and is left uncommitted; resolve

in a dedicated dependency-hygiene PR.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@saagpatel saagpatel changed the base branch from polish/v1.0-improvements to main May 11, 2026 06:50
@saagpatel saagpatel merged commit 17c7273 into main May 11, 2026
0 of 3 checks passed
@chatgpt-codex-connector
Copy link
Copy Markdown

💡 Codex Review

- uses: pnpm/action-setup@v4

P1 Badge Specify a pnpm version before using the action

This frontend job will fail before any tests run because pnpm/action-setup@v4 is invoked without a version, and this package.json does not define a packageManager field for the action to infer from. In the GitHub Actions environment, the setup step errors out instead of installing pnpm, so the subsequent pnpm install/test commands are never reached.


- run: cd sidecar && pip install -r requirements.txt

P1 Badge Install the sidecar test dependencies in CI

The Python workflow installs only sidecar/requirements.txt, but the tests import packages that are not in that file, such as pytest, anthropic, and playwright from the sidecar's test/pyproject configuration. On a fresh GitHub runner this makes cd sidecar && pytest fail with missing commands/modules before exercising the sidecar tests; install the project with its test extra or keep the requirements file in sync.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

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.

1 participant