OperationalError: unable to open database file

[gisce-ti-sentry]

Sentry Issue: GAB-3

OperationalError: unable to open database file
  File "threading.py", line 1024, in run
    self._target(*self._args, **self._kwargs)
  File "github_agent_bridge/executor.py", line 181, in _loop
    did = self.work_one(worker_id)
  File "github_agent_bridge/executor.py", line 58, in work_one
    job = self.queue.claim_next(worker_id)
  File "github_agent_bridge/queue.py", line 147, in claim_next
    with self.connect() as con:
  File "github_agent_bridge/queue.py", line 36, in connect
    con = sqlite3.connect(self.path, timeout=30, isolation_level=None)

This issue was automatically created by Sentry via Github Issue

[giscebot]

Fix proposed in #7.

Summary: JobQueue now expands literal ~ DB paths and recreates the SQLite parent directory before every connection, covering the Sentry failure point in claim_next().

Validation: pytest -q tests/test_queue.py and full pytest -q both pass (157 tests).

[giscebot]

Rechecked the proposed fix in #7 from a clean dedicated worktree.

Validation passed locally:

• .venv/bin/pytest -q tests/test_queue.py -> 16 passed
• .venv/bin/pytest -q -> 157 passed, 1 existing Starlette/httpx deprecation warning

GitHub reports no checks for the PR branch at the moment, so this is ready to review/merge from the local test side. I also rechecked the ERP task prerequisite rule: this runtime has pygisceclient installed but no ERP connection configuration, so I still cannot create the missing task from here.