fix(ci): repair Linear sync syntax gate blocker

[timerloggedout-spec]

Summary\n\nRepairs two accidental ture/sentry-linear-integration fragments in archwiz/linear_sync.py. One fragment made the CLI entrypoint syntactically invalid; the other would execute as an undefined expression during module import. This is intentionally a one-file, behavior-preserving repair.\n\nFixes #287\n\n## Validation\n\n- python3 -m py_compile archwiz/linear_sync.py — passed.\n- python3 archwiz/linear_sync.py --dry-run — passed in report-only mode without external calls.\n- python3 scripts/ci/repo_gate.py — passed after staging the repair, confirming the index-based gate evaluates valid source.\n- python3 scripts/ci/termux_smoke.py — passed.\n- git diff --cached --check — passed.\n\n## Scope boundary\n\nNo Linear credentials, transport behavior, GitHub Actions workflow, proposal registry, or governance policy is changed.\n\nRelated: #274 and #286.\n\n

[blocksorg]

Mention Blocks like a regular teammate with your question or request:

@blocks review this pull request
@blocks make the following changes ...
@blocks create an issue from what was mentioned in the following comment ...
@blocks explain the following code ...
@blocks are there any security or performance concerns?

Run @blocks /help for more information.

Workspace settings | Disable this message

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
termux-monorepo	Ready	Preview, v0	Aug 21, 2026 6:50pm

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 8 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: bda35b31-f1d2-4793-82e2-f1486a38d0fc

📥 Commits

Reviewing files that changed from the base of the PR and between 21ac9e3 and 717cb99.

📒 Files selected for processing (1)

• archwiz/linear_sync.py

---

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

[github-actions]

context_key: pr-288-fixlinear-sync-syntax
source_id: 5373953900
source_revision: 5373953900:2026-08-21T18:50:03Z
@jules Auto-resolve (heyVern lane / GHA agent-review-auto-jules) — do not wait for a human ping.
New work-context pr-288-fixlinear-sync-syntax — create session if none exists, then prefer continue thereafter.
Bot feedback from qodo-code-review[bot] on PR #288 (branch fix/linear-sync-syntax).

Feedback excerpt

<h3>Qodo is busy working</h3>

Check back in a few minutes. Qodo's code review agents are on it.



<img src="https://www.qodo.ai/wp-content/uploads/2025/11/light-grey-line.svg" height="10%" alt="Grey Divider">




<img src="https://www.qodo.ai/wp-content/uploads/2026/01/anteater-looking-at-ants-01-transparent-bg-croped-ezgif.com-optimize-1.gif" width="30%">

Instructions

1. Address open review disposition / threads (CodeRabbit, Devin, Copilot). Ignore pure analysis-chain dumps.
2. Prefer minimal diffs; preserve Sentinel 0o600/0o700 if those files are touched.
3. Push commits to branch fix/linear-sync-syntax. Do not retarget away from the PR base without cause.
4. If conflicts with base exist, resolve them.
5. Skip pure nits only if they conflict with security/gates; otherwise apply autofixes.
6. Non-empty diff required — empty commits are rejected.
   Monikers: docs/ops/AGENT-MONIKERS.md
   Agent: Grok (archW1z) orchestration · Profile: https://x.com/grok
   Signed-off-by: Grok (OPERATOR) session-auto-jules / context_key=pr-288-fixlinear-sync-syntax

[qodo-code-review]

PR Summary by Qodo

Fix Linear sync module syntax to unblock CI gate

🐞 Bug fix 🕐 Less than 10 minutes

AI Description

• Remove stray ture/sentry-linear-integration fragments that broke module parsing.
• Restore valid CLI entrypoint so sync_to_linear() executes correctly.
• Unblock index-based CI syntax gating on archwiz/linear_sync.py.

Diagram

graph TD
  CI["CI gate"] --> Gate["scripts/ci/repo_gate.py"] --> Compile["Python syntax check"] --> Linear["archwiz/linear_sync.py"]
  Dev["Developer/CLI"] --> Linear
  subgraph Legend
    direction LR
    _usr["Actor"] ~~~ _job["Job/Script"] ~~~ _mod["Python module"]
  end

Loading

High-Level Assessment

Best approach is a minimal, behavior-preserving removal of the accidental fragments. Alternatives (refactoring the script or adding new gating mechanisms) would add risk and scope without improving the immediate CI-blocking failure mode.

Files changed (1) +2 / -2

Bug fix (1) +2 / -2

linear_sync.pyRemove stray fragments that broke import and CLI execution +2/-2

Remove stray fragments that broke import and CLI execution

• Deletes two accidental 'ture/sentry-linear-integration' text fragments: one at module scope (would error during import) and one appended to the '__main__' call (made the entrypoint invalid). This restores syntactically valid parsing and keeps runtime behavior unchanged aside from no longer crashing.

archwiz/linear_sync.py

[github-actions]

context_key: pr-288-fixlinear-sync-syntax
source_id: 5373959040
source_revision: 5373959040:2026-08-21T18:50:35Z
@jules Auto-resolve (heyVern lane / GHA agent-review-auto-jules) — do not wait for a human ping.
New work-context pr-288-fixlinear-sync-syntax — create session if none exists, then prefer continue thereafter.
Bot feedback from qodo-code-review[bot] on PR #288 (branch fix/linear-sync-syntax).

Feedback excerpt

<h3>PR Summary by Qodo</h3>

Fix Linear sync module syntax to unblock CI gate

<code>🐞 Bug fix</code> <code>🕐 Less than 10 minutes</code>

<img src="https://www.qodo.ai/wp-content/uploads/2025/11/light-grey-line.svg" height="10%" alt="Grey Divider">

<details>
<summary>AI Description</summary>

<dl>
<dd>
<br/>

><pre>
>• Remove stray <b><i>ture/sentry-linear-integration</i></b> fragments that broke module parsing.
>• Restore valid CLI entrypoint so <b><i>sync_to_linear()</i></b> executes correctly.
>• Unblock index-based CI syntax gating on <b><i>archwiz/linear_sync.py</i></b>.
></pre>

</dd>
</dl>

</details>

<details>
<summary>Diagram</summary>

<dl>
<dd>

<br/>

```mermaid
graph TD
  CI["CI gate"] --> Gate["scripts/ci/repo_gate.py"] --> Compile["Python syntax check"] --> Linear["archwiz/linear_sync.py"]
  Dev["Developer/CLI"] --> Linear
  subgraph Legend
    direction LR
    _usr["Actor"] ~~~ _job["Job/Script"] ~~~ _mod["Python module"]
  end

High-Level Assessment

Best approach is a minimal, behavior-preserving removal of the accidental fragments. Alternatives (refactoring the script or adding n

### Instructions
1. Address **open review disposition / threads** (CodeRabbit, Devin, Copilot). Ignore pure analysis-chain dumps.
2. Prefer minimal diffs; preserve Sentinel 0o600/0o700 if those files are touched.
3. Push commits to branch `fix/linear-sync-syntax`. Do not retarget away from the PR base without cause.
4. If conflicts with base exist, resolve them.
5. Skip pure nits only if they conflict with security/gates; otherwise apply autofixes.
6. **Non-empty diff required** — empty commits are rejected.
Monikers: docs/ops/AGENT-MONIKERS.md
Agent: Grok (archW1z) orchestration · Profile: https://x.com/grok
Signed-off-by: Grok (OPERATOR) session-auto-jules / context_key=pr-288-fixlinear-sync-syntax

[timerloggedout-spec]

cycle_id: pr-288-717cb99f51a3
head_sha: 717cb99
cycle_started_at: 2026-08-21T18:50:35.000Z
state: provider_cooldown
ready: false
required_providers: coderabbit
enforce_provider_completion: false

Agent peer response gate

Provider state:

• coderabbit: provider_cooldown; cooldown=8 minutes; source=fix(ci): repair Linear sync syntax gate blocker #288 (comment)

Pending:
coderabbit:provider_cooldown

Authorized interactive controls:

• none observed

A provider-owned checkbox/button requires an authorized Operator Action Executor.
Do not copy control markup into a relay comment. After a permitted UI action, post:

<!-- operator-action-ack:v1 -->
cycle_id: pr-288-717cb99f51a3
provider: <provider>
control_id: <provider-control-id>
action: <allowed-action>

The second-pass reviewer remains blocked until matching provider completion evidence is ingested for this SHA.
A checked [x] control means the provider UI action occurred; it is not a completed review.
A provider cooldown is also non-completing: wait for the stated retry window, then retrigger through the authorized provider path.
Pending provider evidence is advisory unless PEER_ENFORCE_PROVIDER_COMPLETION is deliberately set to true for branch protection.

[timerloggedout-spec]

@coderabbitai full review

cycle_id: pr-288-717cb99f51a3
head_sha: 717cb99
provider: coderabbit
action: trigger_review
request_actor: OPERATOR

Autonomous OPERATOR-token request for a current-SHA provider review. A command request is not review completion; await provider evidence.

[gitar-bot]

Important

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

_Gitar

[coderabbitai]

@timerloggedout-spec The full review has been triggered for the current PR revision.

⚠️ Action not completed

Review rate limited.

---

Your included review limit is currently reached under our Fair Usage Limits Policy. This review may still proceed through usage-based billing if eligible. Your next included review will be available in 8 minutes.

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can tweak Display preferences with a live preview to see your comment before it ships

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[github-actions]

context_key: pr-288-fixlinear-sync-syntax
source_id: 5373991634
source_revision: 5373991634:2026-08-21T18:54:02Z
@jules Auto-resolve (heyVern lane / GHA agent-review-auto-jules) — do not wait for a human ping.
New work-context pr-288-fixlinear-sync-syntax — create session if none exists, then prefer continue thereafter.
Bot feedback from qodo-code-review[bot] on PR #288 (branch fix/linear-sync-syntax).

Feedback excerpt

<h3>Code Review by Qodo</h3>
<code>🐞 Bugs (0)</code>  <code>📘 Rule violations (0)</code>  <code>📎 Requirement gaps (0)</code>

<img src="https://www.qodo.ai/wp-content/uploads/2025/11/light-grey-line.svg" height="10%" alt="Grey Divider">

<img src="https://www.qodo.ai/wp-content/uploads/2025/06/qodo-anteater.svg" width="20%">

<h3>Great, no issues found!</h3>
Qodo reviewed your code and found no material issues that require review

<img src="https://www.qodo.ai/wp-content/uploads/2025/11/light-grey-line.svg" height="10%" alt="Grey Divider">



<!-- qodo-daily-tip:start -->

<details>
<summary><strong>Tip of the day</strong></summary>

<br/>

<pre>💡 Did you know, you can tweak Display preferences with a live preview to see your comment before it ships</pre>

<a href="https://docs.qodo.ai/tips-and-tricks">More tips ↗</a> | <a href="https://app.qodo.ai/configurations?tab=display-preferences">Customize Qodo ↗</a> | <a href="https://docs.qodo.ai">Qodo docs ↗</a>

</details>

<img src="https://www.qodo.ai/wp-content/uploads/2025/11/light-grey-line.svg" height="10%" alt="Grey Divider">
<!-- qodo-daily-tip:end -->


<!-- https://github.com/timerloggedout-spec/termux-monorepo/commit/71

Instructions

1. Address open review disposition / threads (CodeRabbit, Devin, Copilot). Ignore pure analysis-chain dumps.
2. Prefer minimal diffs; preserve Sentinel 0o600/0o700 if those files are touched.
3. Push commits to branch fix/linear-sync-syntax. Do not retarget away from the PR base without cause.
4. If conflicts with base exist, resolve them.
5. Skip pure nits only if they conflict with security/gates; otherwise apply autofixes.
6. Non-empty diff required — empty commits are rejected.
   Monikers: docs/ops/AGENT-MONIKERS.md
   Agent: Grok (archW1z) orchestration · Profile: https://x.com/grok
   Signed-off-by: Grok (OPERATOR) session-auto-jules / context_key=pr-288-fixlinear-sync-syntax