The out-of-repo resume_arm_time.py copy is 45 diff-lines behind the canonical one and nothing reconciles them

[jaylfc]

CARD TITLE (intent, not commit subject): The out-of-repo resume_arm_time.py copy is 45 diff-lines behind the canonical one and nothing reconciles them

Autonomous build of board card tsk-iavmeu.

Files:
changelog.d/tsk-iavmeu-stale-copy-symlink.md | 3 +++
1 file changed, 3 insertions(+)

[qodo-code-review]

ⓘ Qodo reviews are paused because your trial has ended. Ask your workspace admin to add credits to resume reviews. Manage billing

[coderabbitai]

Warning

Review limit reached

@jaylfc, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

CodeRabbit couldn't verify your organization's usage billing state, so no usage-priced review was started. Retry after the billing service recovers.

How can I continue?

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.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 38e62cf1-f8ec-4dfd-a256-396d11a66a69

📥 Commits

Reviewing files that changed from the base of the PR and between 0778149 and 1cca86d.

📒 Files selected for processing (1)

• changelog.d/tsk-iavmeu-stale-copy-symlink.md

---

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.}

[gitar-bot]

Important

You are using the Gitar free plan. Upgrade to unlock code review, CI analysis, auto-apply, custom automations, and more.

_Gitar

[jaylfc]

BLOCKED. The problem is real, but this PR does not contain a fix. The drift between the out-of-repo helper and the repo copy was worth opening a card about. What landed here is a changelog entry describing something that was done to a filesystem.

Revision card: tsk-cdqsgy. Closing per close-on-block. Branch exec/tsk-iavmeu is kept and stays fetchable.

1. The PR is one changelog fragment and nothing else

$ gh api repos/jaylfc/taosmd/pulls/363/files --jq '.[].filename'
changelog.d/tsk-iavmeu-stale-copy-symlink.md      +3/-0

No code, no test, no gate. After this merges, the repository still contains nothing that makes the fragment's claim true. A CHANGELOG asserts something about the repository, and this asserts something about one machine: it is not reproducible, not reviewable, not portable, and it is undone by any fresh clone.

2. The claim is not true on this box either, which is the part worth reading

The symlinking did work in the sense the fragment means: all three paths resolve to a single file. But that file is the main worktree's working copy, and the main worktree is 15 commits behind master.

$ git show origin/master:scripts/resume_arm_time.py | md5sum
b972d21fff77c283093ec0ceabf19228
$ md5sum scripts/resume_arm_time.py
446505544c462c527ce6df1d18b98710
$ git rev-list --count HEAD..origin/master
15

So "a symlink to the canonical repo copy" currently resolves to a pre-#354 script: one that still hardcodes /home/jay/.taos-fleet-tools/resume_arm_time.py rather than deriving _HELPER_PATH from __file__. The armed resume pair is running that stale script right now. It functions, because the hardcoded path exists and the marker is self-consistent, so nothing is broken today. But the drift this card was opened about was reduced rather than removed, and the fragment claims more than was achieved.

I am flagging this against my own previous work, not just this PR: I performed that symlinking during the last session and reported it as pointing at the canonical copy. Consistency was achieved; canonical content was not. Repointing the box is an operational action on a checkout that has staged work in it, so it is deliberately not part of this card and is going to the bus instead.

3. The fragment has no terminating newline

Its last byte is 0x2e. That is the fifth file in a row across #356, #359, #360 and its README, and now this. tsk-7m6ju5 covers building the gate. This PR simply must not add another instance.

What the revision should contain

The fix has to live in the repository and be true after a fresh clone on a machine that has never had a .taos-fleet-tools directory. Since #354 the script derives its own path, so the durable answer is that scripts/resume_arm_time.py is the only copy and everything invokes it there: update .claude/audit-cron-prompt.md to name the in-repo path in both places it references the helper, and add a test that fails if any doc names an out-of-repo resume_arm_time.py. That test is the part that makes it stick, and it is checkable in CI on a machine with no /home/jay at all. Prove it engages against a fixture before recording it green. Full end state is on tsk-cdqsgy.