Point doc-updater at ohcnetwork/care for change detection

[amjithtitus09]

Intent

The daily-doc-updater agentic workflow previously scanned this docs repo (ohcnetwork/docs) for merged PRs/commits to document. That's wrong — the product code lives in ohcnetwork/care. This change points the workflow's change-detection source at the CARE product repo, while keeping documentation edits and the output pull request in this repo (ohcnetwork/docs).

Source vs. destination:

• Source of changes it reviews → ohcnetwork/care (product repo)
• Where docs are edited & the PR is opened → ohcnetwork/docs (this repo, via safe-outputs)

What changed

.github/workflows/daily-doc-updater.md (body / prompt instructions only — frontmatter behavior unchanged):

• Step 1 "Scan Recent Activity": the search_pull_requests query now targets repo:ohcnetwork/care is:pr is:merged merged:>=YYYY-MM-DD (was repo:${{ github.repository }}). pull_request_read, list_commits, and get_commit are all explicitly directed at owner: ohcnetwork, repo: care.
• Mission, doc-location step, PR template, edge cases, and notes clarified so it's explicit that the change source is the product repo while docs edits and the create-pull-request output live in ohcnetwork/docs. PR-reference templates now use ohcnetwork/care#PR_NUMBER.
• The pre_activation check throttle (gh pr list --repo "$GITHUB_REPOSITORY" ... in:title "[docs]") is intentionally left unchanged — it counts this repo's own open [docs] PRs to cap concurrent doc PRs, so it must keep pointing at ohcnetwork/docs.

.github/workflows/daily-doc-updater.lock.yml regenerated with gh aw compile (extension pinned to v0.81.6, matching the current lock's compiler_version):

• body_hash updated to match the new markdown body; frontmatter_hash, compiler_version (v0.81.6) and engine version (copilot 1.0.65) are unchanged — no version drift.
• The compiler dropped the now-unused GH_AW_GITHUB_REPOSITORY prompt-interpolation env var, since the prompt no longer references ${{ github.repository }}.
• Verified: a second gh aw compile is a no-op (idempotent).

Permissions / token note

The workflow's tools.github uses the default toolset with no explicit github-token:, and it does not need one for this change:

• ohcnetwork/care is a public repository, so the default GITHUB_TOKEN can read its public PR/commit/search data cross-repo. No frontmatter change is required.
• The compiled workflow already resolves the GitHub MCP token as GH_AW_GITHUB_MCP_SERVER_TOKEN || GH_AW_GITHUB_TOKEN || GITHUB_TOKEN. So if the maintainer later wants higher rate limits (or if ohcnetwork/care ever becomes private), they can simply set a GH_AW_GITHUB_MCP_SERVER_TOKEN (or GH_AW_GITHUB_TOKEN) repo secret to a PAT/GitHub App token with read access to ohcnetwork/care — no workflow edit needed, the lock already reads that secret with fallback.

Recommendation: ship as-is for the public repo; consider adding a read-only PAT/App token secret if search/API rate limits on the default token become a reliability concern.

Notes

• Only the two workflow files changed. The untracked gh aw compile artifacts (.github/aw/actions-lock.json, .github/workflows/agentics-maintenance.yml) are not included, consistent with the repo's current tracking.

[cloudflare-workers-and-pages]

Deploying coredocs with    Cloudflare Pages

Latest commit:	cc56ccd
Status:	✅  Deploy successful!
Preview URL:	https://19a03dff.coredocs.pages.dev
Branch Preview URL:	https://doc-updater-scan-care.coredocs.pages.dev

View logs