Copilot Fix(CI Failure): Remove intentional exit 1 from Fake CI workflow

[github-actions]

The "Fake CI" workflow is failing due to an intentional `exit 1` command that causes every build to fail.

Why did the CI workflow go to therapy? Because it had exit issues! 🚪💥

https://github.com/austenstone/copilot-cli/actions/runs/19875688100/job/

💥 Error Log

```
buildRun exit 12025-12-02T22:31:25.7185848Z ##[group]Run exit 1
buildRun exit 12025-12-02T22:31:25.7186387Z exit 1
buildRun exit 12025-12-02T22:31:25.7204536Z shell: /usr/bin/bash -e {0}
buildRun exit 12025-12-02T22:31:25.7205066Z ##[endgroup]
buildRun exit 12025-12-02T22:31:25.7256517Z ##[error]Process completed with exit code 1.
```

🕵️‍♂️ Diagnosis

The workflow file `.github/workflows/ci.yml` contains a hardcoded `exit 1` command on line 15. This is causing the workflow to fail unconditionally after printing "Hello, world!". The command explicitly terminates the job with exit code 1, which GitHub Actions interprets as a failure.

Root Cause: Line 15 of `.github/workflows/ci.yml` contains `- run: exit 1`

🛠️ Proposed Fix

Remove the `- run: exit 1` step from the workflow (line 15). The workflow will then complete successfully after executing the echo command.

Note: Due to GitHub security restrictions, the automated Copilot CLI cannot directly modify workflow files without `workflows` permission. This PR includes comprehensive documentation of the required fix that must be applied manually by a repository maintainer.

See `CI_FIX_19875688100.md` in this PR for detailed fix instructions and options.

[austenstone]

Closing as stale — the workflow this was fixing no longer exists.

These PRs were generated by copilot-ci-fix.yml reacting to an intentional exit 1 in a "Fake CI" workflow (.github/workflows/ci.yml). That file has since been removed from main (404), so there is nothing left to fix. There are four near-identical PRs open for the same phantom failure (#49, #61, #63, #68).

Worth noting what they surfaced: several tried to fix CI by editing README.md or dropping stray CI_FIX_*.md proposal files at the repo root, and each reported that the token lacked the workflows permission. That last part is expected — workflows is not a GITHUB_TOKEN scope, so no permissions: setting can grant it. #78 removes the write-all that was there in the belief that it could.