refactor: rewrite profile readme in quarto

[kelly-sovacool]

Changes

Re-write the make_readme action and scripts as a quarto document for a simplified design. Removes a lot of boilerplate code and makes the readme easier to understand. Instead of calling make_readme.sh, the readme is now updated with quarto render profile/README.qmd. The content in the rendered file (profile/README.md) is nearly identical to the original, with the only differences being line wrapping.

Importantly, the workflow now fails when data cannot be retrieved from the GitHub API. This ensures the workflow doesn't fail silently when tokens expire or have insufficient permissions.

You can test how the README file is rendered without running the Python code chunks with:

quarto render profile/README.qmd -M eval:false

AI Use: I used Copilot in VS Code to assist in this refactor, plus Copilot via the GitHub web interface for refinement.

Issues

fixes #45
resolves #67

PR Checklist

(Strikethrough any points that are not applicable.)

• This comment contains a description of changes with justifications, with any relevant issues linked.
• [ ] Write unit tests for any new features, bug fixes, or other code changes.
• [ ] Update docs if there are any API changes.
• [ ] Update CHANGELOG.md with a short description of any user-facing changes and reference the PR number. Guidelines: https://keepachangelog.com/en/1.1.0/

[kelly-sovacool]

@copilot When the omnitoken expires, the quarto is still rendered and the workflow completes successfully, but data is missing because insufficient permissions were provided for the github api due to the expired token. See this recent commit for an example of this problem: 9494464. Fix the code so that an explicit error is thrown if critical data cannot be retrieved such as due to an expired token.

[Copilot]

@copilot When the omnitoken expires, the quarto is still rendered and the workflow completes successfully, but data is missing because insufficient permissions were provided for the github api due to ...

Implemented in a268994. I updated the README data-fetch scripts to fail fast with explicit RuntimeError messages when critical GitHub API calls fail (including auth/permission failures like expired GITHUB_TOKEN) instead of silently returning partial/empty data. This now causes Quarto rendering to fail explicitly when critical data cannot be retrieved. No UI changes were made (workflow/script-only change).

[kopardev]

Reviewing the workflow changes, I found one functional bug and a near-term Actions runtime risk.