Oleksandr Bezdieniezhnykh f29897cb3a [meta] Tighten Jira tracker error handling: STOP and ASK on any error
User feedback after a transitionJiraIssue call returned a bare
{"success": true} that I trusted blindly: the rule should require
explicit verification and stop-and-ask on any ambiguous response.

Two targeted clarifications:

- .cursor/rules/tracker.mdc - Tracker Availability Gate now lists
  the full set of failure modes (non-2xx, timeout, empty body,
  opaque success) and bans automatic retries. Adds an explicit
  read-back requirement when the response is minimal, and adds
  "abort" to the user-choice menu.

- .cursor/skills/implement/SKILL.md - Step 5 (In Progress) and
  Step 12 (In Testing) now spell out the STOP-and-ASK rule inline
  instead of just pointing at tracker.mdc. Adds the read-back
  verification step for opaque responses.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-05-13 23:06:48 +03:00

gps-denied-onboard

Companion onboard system for GPS-denied UAV navigation. Detailed design and architecture documentation lives under _docs/.

Local development

python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
pytest -q tests/unit/

For full Tier-1 integration via Docker, see _docs/02_document/deployment/containerization.md.

Build matrix

Four binaries built from this codebase: airborne, research, operator-orchestrator, replay-cli. CMake BUILD_* flags gate component inclusion per binary — see cmake/build_options.cmake and _docs/02_document/module-layout.md § Build-Time Exclusion Map.

S
Description
No description provided
Readme 252 MiB
Languages
Markdown 100%