fix(ci): checkout PhenoObservability as sibling so workspace path-dep resolves

[KooshaPari]

User description

Problem

Every cargo test --workspace run on main and on PR branches (including the just-opened connector-parser PR #83) fails before any tests execute:

error: failed to load manifest for workspace member `.../crates/focus-always-on`
Caused by: failed to load manifest for dependency `phenotype-observably-macros`
Caused by: failed to read `.../PhenoObservability/crates/phenotype-observably-macros/Cargo.toml`

11 crates in the FocalPoint workspace depend on phenotype-observably-macros via
path = "../../../PhenoObservability/crates/phenotype-observably-macros". From
crates/<name>/ that resolves to a sibling of the FocalPoint checkout. CI only
checks out FocalPoint, so the relative path is missing.

Fix

• Check out PhenoObservability into $GITHUB_WORKSPACE/PhenoObservability (sibling of $GITHUB_WORKSPACE/FocalPoint).
• Pin actions/checkout to the same SHA used in the rest of the org.
• Move subsequent steps under working-directory: FocalPoint so they keep operating on the workspace.

Risk

• Workflow-only change.
• No code or path-deps touched.
• All run: blocks are hardcoded (no untrusted github.event.* inputs).

Test Plan

• Pushed as fix/ci-checkout-phenoobservability
• CI run on this branch: cargo test --workspace and cargo clippy should execute and report results
• Re-run PR fix(connectors): notion/readwise parsers handle single-page + empty + batched shapes #83 (connector parser fix) — test and Journey Verification jobs should now pass

🤖 Generated with Claude Code

---

Note

Low Risk
Workflow-only change with pinned third-party actions and no application or dependency manifest edits.

Overview
Fixes CI failing before tests run because workspace crates resolve phenotype-observably-macros via a relative path to a sibling PhenoObservability repo that was never checked out.

The workflow now checks out FocalPoint into FocalPoint/ and KooshaPari/PhenoObservability into PhenoObservability/ under the same workspace root, adds a small guard that fails fast if PhenoObservability is a broken symlink, pins checkout, rust-toolchain, and rust-cache to specific SHAs, scopes rust-cache to FocalPoint, and runs cargo test / cargo clippy with working-directory: FocalPoint.

^{Reviewed by Cursor Bugbot for commit 4da4eff. Bugbot is set up for automated code reviews on this repo. Configure here.}

---

CodeAnt-AI Description

Make CI check out the sibling workspace so tests can run

What Changed

• CI now checks out both FocalPoint and PhenoObservability side by side, so workspace dependencies resolve the same way they do on a local machine.
• The workflow now runs tests and linting from the FocalPoint checkout instead of the repository root.
• The checkout and Rust setup steps are pinned to fixed versions for consistent CI runs.

Impact

✅ Fewer workspace load failures in CI
✅ Reliable cargo test runs on PRs
✅ Clearer CI results for workspace and lint checks

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[codeant-ai]

CodeAnt AI is reviewing your PR.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[coderabbitai]

Warning

Review limit reached

@KooshaPari, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 44 minutes and 37 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: d2838f21-cab6-4089-9b8d-e2a5e58121e0

📥 Commits

Reviewing files that changed from the base of the PR and between 1cff1b4 and 4da4eff.

📒 Files selected for processing (1)

• .github/workflows/ci.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/ci-checkout-phenoobservability

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch fix/ci-checkout-phenoobservability

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[KooshaPari]

Closing as superseded: PR #80 (fix/focalpoint-observably-vendor) is the proper fix — it vendors phenotype-observably-macros into the workspace and switches 11 deps to workspace = true, eliminating the broken ../../../PhenoObservability path-dep at the source. My PR #84 was a CI-only band-aid that added a sibling checkout; with the macro vendored, the path-dep disappears and CI no longer needs the extra checkout step. Land #80 and no follow-up CI changes are needed.