Enable working CI lint autofix + remediate pre-existing ruff/mypy/pytest errors by cryptoxdog · Pull Request #125 · Quantum-L9/Cognitive.Engine.Graphs

cryptoxdog · 2026-07-19T21:31:40Z

Summary

Answers "how do we enable autofix on CI tools and remediate the codebase's existing pre-existing errors?" with a working implementation instead of just docs:

Fixed the broken autofix workflow. .github/workflows/auto-fix-adr.yml called ci/auto_fix_adr.py and ci/check_imports.py, but the ci/ directory doesn't exist in this repo — it could never succeed. Replaced it with .github/workflows/lint-autofix.yml, which runs ruff check --fix + ruff format against develop (on push or workflow_dispatch) and opens a PR with the result. It never pushes directly to a protected branch, and it now covers the same class of fixes the old ADR script targeted (sorted __all__, Optional[T] → T | None, datetime.now(UTC), zip(strict=True), unused/unsorted imports, ...).
Added the missing make lint-fix target. AGENTS.md, .cursorrules, and docs/CI_PIPELINE.md all document make lint-fix as the local autofix command, but it never existed in the Makefile. make lint also used to mutate the tree (--fix) and skip mypy, so it didn't actually mirror what CI enforces. Now make lint is a non-mutating check that matches CI (ruff check + ruff format --check + mypy engine/), and make lint-fix is the autofix entry point.
Remediated the pre-existing baseline so the newly-honest make lint (and CI's lint/lint-format jobs) actually pass:
- ruff check .: 129 → 0 errors (100 via --fix, the rest were non-autofixable: renamed shadowed constants, zip(strict=True), ambiguous Unicode in comments/docstrings, dead unused-var removal, one PLR0915 fixed by extracting a helper method, an ASYNC109 false-positive resolved by a parameter rename, etc.)
- ruff format .: 60 files reformatted
- mypy engine/: 19 → 0 errors, including one genuine bug found along the way (GraphSyncClient._build_envelope() was calling build_graph_sync_packet(tenant_tier=..., correlation_id=...), but that factory's real signature only accepts tenant_context/lineage — this dormant, untested class would have raised TypeError on every call)
- pytest.ini was missing the compliance/performance/slow/contract/finding markers that pyproject.toml separately declared (which pytest ignores whenever pytest.ini exists) — any -m-filtered pytest run (including the pytest-unit pre-commit hook) failed at collection as soon as it reached tests/compliance/test_audit.py, before running a single test. Merged the marker lists.

All changes are commited separately by theme; see individual commit messages for the specifics of each rule/file.

Verification

ruff check . / ruff format --check . / mypy engine/ all exit 0
make lint passes end-to-end
Full pre-commit pytest tests/ -m "unit" ... command now collects and passes (previously aborted at collection)
Full pytest tests/ run: identical 39 failed, 1570 passed, 35 skipped, 56 xfailed, 22 errors before and after these changes (confirmed against the pre-change tree) — those pre-existing failures are unrelated full-suite ordering/integration issues (missing Docker/Neo4j, constellation_node_sdk, DomainPackLoader API drift, etc.) and are out of scope here

Out of scope (flagged, not fixed)

Several other workflows (ci.yml, docker-build.yml, k8s-deploy.yml, supply-chain.yml) pin third-party actions with a corrupted ref format (a full SHA immediately concatenated with a version tag, e.g. @c5a7806660adbe173f04e3e038b0ccdcd758773dv6.1.0), which is not a resolvable git ref. Unrelated to lint/autofix; left untouched to keep this PR scoped.
The 39 full-suite test failures / 22 errors noted above (pre-existing, reproduced identically before this branch).

…format errors Mechanical, behavior-preserving fixes (import sorting, unused imports, formatting) generated by 'ruff check --fix' and 'ruff format'. No manual edits in this commit. Co-authored-by: Igor Beylin <cryptoxdog@users.noreply.github.com>

These lint/type violations were flagged by ruff check and mypy but have no mechanical --fix. All are behavior-preserving: - N806/PLR1714/SIM103/SIM108: rename shadowed constants, merge comparisons, simplify boolean returns (engine/auth/capabilities.py, engine/contract_enforcement.py, engine/convergence_controller_patch.py, engine/inference_rule_registry.py, engine/scoring/assembler.py) - RUF002/RUF003: replace ambiguous Unicode (en dash, Greek alpha) in comments/docstrings with ASCII equivalents - B905: add explicit zip(strict=True) where lengths are already guaranteed equal (engine/diagnostics/dissimilarity.py) - ASYNC109: rename the timeout parameter to timeout_seconds on GraphToEnrichReturnChannel.drain() / apply_return_channel_targets() to avoid the async-timeout-param false positive, updating all call sites - DTZ003: replace datetime.utcnow() with datetime.now(UTC) in engine/models/outcomes.py (OutcomeRecord.timestamp + cutoff computation, kept consistent to avoid naive/aware comparison bugs) - F841/RUF059/E402: drop or underscore-prefix unused locals, consolidate imports to the top of tests/test_algorithmic_upgrades.py - PLR0915: extract MultiHopTraverser._execute_hop() from traverse() to reduce statement count (pure extraction, no behavior change) - N818: chassis.errors.FeatureNotEnabled is a stable, serialized error name used by API clients, documented as an intentional per-file ignore instead of a breaking rename - mypy unreachable/arg-type: annotate two intentionally-defensive runtime type checks in capabilities.py, and fix a mypy ignore-comment placement mismatch in multihop.py's pre-existing similarity-mode call All touched unit tests re-verified passing; ruff check/format and mypy both clean on these files. Co-authored-by: Igor Beylin <cryptoxdog@users.noreply.github.com>

While removing an unused local (F841, ruff), found that _build_envelope() called build_graph_sync_packet(tenant_tier=..., correlation_id=...), but that factory's real signature only accepts tenant_context and lineage dicts (engine/contract_enforcement.py). This call would raise TypeError on every invocation. Map the arguments onto the actual factory signature instead. This class has no current callers/tests, so this was previously undetected dormant code (mypy call-arg + F401 unused-import findings). Co-authored-by: Igor Beylin <cryptoxdog@users.noreply.github.com>

ci-quality.yml's lint-format job runs mypy with continue-on-error:false, so these were already CI-blocking on every PR to main/develop: - engine/arbitration/engine.py: ArbitrationEngine.resolve() assigned plain str to ArbitrationResult.final_decision (a Literal[...] field); annotate the local with the same Literal so mypy narrows it correctly. _evaluate()'s comparison operators returned Any (object has no __lt__/__le__/__gt__/__ge__ per typeshed); widen the params to Any (they already accept heterogeneous domain-config values) and wrap each comparison in bool(...). - engine/outcomes/engine.py: OutcomeEngine.process() calls GraphDriver.apply_outcome_edge_update() / ScoringAssembler. apply_outcome_feedback(), neither of which exists. This path is dormant -- tests/unit/test_outcomes.py already skips it because DomainPackLoader.allowed_canonical_labels() "never existed" (see reports/GMP-Report-132-Fix-Residual-PreExisting-Issues.md). Documented with type: ignore[attr-defined] plus a note rather than fabricating an implementation. - engine/security/P2_9_llm_schemas.py: explicit str(...) around the narrowed (non-None) LLM response content, since the untyped SDK response otherwise resolves to Any. - engine/compliance/audit_persistence.py: move the asyncpg import (used only in type annotations under `from __future__ import annotations`) behind TYPE_CHECKING (ruff TC002); no runtime change. `mypy engine/` now exits 0 (previously 19 errors across 7 files). Co-authored-by: Igor Beylin <cryptoxdog@users.noreply.github.com>

pytest.ini is the authoritative config (it takes precedence over pyproject.toml's [tool.pytest.ini_options], which pytest ignores whenever a root pytest.ini exists). Its markers list only had unit/integration/security, while pyproject.toml separately declared compliance/performance/slow/contract/finding, which pytest never actually saw. Effect: any pytest invocation using -m (as the pytest-unit pre-commit hook and CI do) failed at collection with "'compliance' not found in `markers` configuration option" as soon as it reached tests/compliance/test_audit.py, aborting the entire run before any unit test executed. Reproduced and confirmed on the pre-change tree. Merge the full marker set into pytest.ini (the active config) and keep pyproject.toml's copy in sync with a note explaining the precedence, so this doesn't silently drift again. Co-authored-by: Igor Beylin <cryptoxdog@users.noreply.github.com>

AGENTS.md, .cursorrules, and docs/CI_PIPELINE.md all document and instruct agents/contributors to run `make lint-fix` to autofix lint failures, and describe `make lint` as the check-only ruff+mypy gate that mirrors CI. Neither existed: the Makefile only had a `lint` target that already mutated the tree via `ruff check . --fix` + `ruff format .` and never ran mypy, so it did not actually match what CI enforces, and `make lint-fix` didn't exist at all. - `make lint` now runs `ruff check .` (no --fix) + `ruff format --check .` + `mypy engine/` -- the same non-mutating checks CI runs, so a clean `make lint` locally is a reliable predictor of a passing CI lint job. - `make lint-fix` is the new autofix entry point: `ruff check . --fix` + `ruff format .` (matches the long-documented but missing command). - `make check` (full local gate) keeps its previous autofix-then-verify behavior for convenience, just relabeled for clarity. Co-authored-by: Igor Beylin <cryptoxdog@users.noreply.github.com>

…workflow .github/workflows/auto-fix-adr.yml (triggered on push to develop / workflow_dispatch) called `python ci/auto_fix_adr.py` and `python ci/check_imports.py`, but the ci/ directory does not exist anywhere in this repo, so the workflow could never run successfully. Ruff already mechanically enforces (and can --fix) the same class of issues that workflow targeted: sorted __all__ (RUF022), Optional[T] -> T | None (UP045), datetime.now() -> datetime.now(UTC) (UP017/DTZ003), zip(strict=True) (B905), unused/unsorted imports (F401/I001), etc. -- see [tool.ruff.lint] in pyproject.toml. Add .github/workflows/lint-autofix.yml: same trigger/safety model (develop push + workflow_dispatch, never pushes directly to a protected branch, opens a PR via peter-evans/create-pull-request instead), but running `ruff check . --fix` + `ruff format .`, with a syntax-validation step and a check that ruff has no remaining autofixable violations before opening the PR. Skips opening a PR when there is nothing to fix. Document both the new workflow and `make lint-fix` as the two ways to autofix lint violations in docs/CI_PIPELINE.md. Co-authored-by: Igor Beylin <cryptoxdog@users.noreply.github.com>

github-actions · 2026-07-19T21:31:54Z

❌ Too Many Files Changed
Changed: 79 files
Limit: 50 files
Action Required: Split into multiple focused PRs

❌ PR Too Large
Lines changed: 1669
Limit: 1000 lines
Action Required: Break into smaller, atomic PRs

📋 Best Practices for Large Changes

Refactoring + Features: Separate into 2 PRs
Multiple Features: One PR per feature
Database + Code: Separate migration from logic
Generated Code: Separate from manual changes

🚫 This PR is blocked from merging until size limits are met.

cursor · 2026-07-19T21:41:17Z

    import engine.gates.compiler as gc
-    import engine.sync.generator as sg
    import engine.scoring.assembler as sa
+    import engine.sync.generator as sg


Reviewed — not applying this one. The two imports serve genuinely different purposes and aren't interchangeable here:

test_sync_generator_uses_parameterized_query (line 37) needs the SyncGenerator class to instantiate it: from engine.sync.generator import SyncGenerator.

test_eval_exec_not_importable_from_engine (line 74) needs the module object engine.sync.generator itself, so it can call dir(mod) and walk its module-level names looking for an eval-like function: import engine.sync.generator as sg.

The suggested fix (from engine.sync.generator import SyncGenerator as sg) would alias the class to sg, not the module — dir(sg) would then return the class's methods/attributes instead of the module's top-level names, silently changing what test_eval_exec_not_importable_from_engine actually checks (defeating its stated purpose: "Engine modules must not expose eval/exec at module level"). Different scopes (separate function bodies), each importing exactly what that test needs, is intentional here rather than an inconsistency to fix.

DomainPackLoader.__init__() takes config_path, not domains_dir (see engine/config/loader.py:53). Both call sites in this file passed domains_dir=..., which raised TypeError before either test could reach the assertions it exists to check. Confirmed pre-existing (reproduced identically on the unmodified main branch, unrelated to this PR). Flagged by github-code-quality[bot] on PR #125; fixing here since it directly blocks two security tests that must run in CI. Note: with the constructor fixed, both tests now progress further but still fail on a separate, pre-existing issue -- domains/plasticos fails DomainSpec validation (scoring.dimensions[].source/computation/ weightkey/defaultweight, sync.endpoints) -- a domain-spec/schema drift issue unrelated to this argument-name bug and out of scope here. Co-authored-by: Igor Beylin <cryptoxdog@users.noreply.github.com>

github-actions · 2026-07-19T21:40:32Z

❌ Too Many Files Changed
Changed: 79 files
Limit: 50 files
Action Required: Split into multiple focused PRs

❌ PR Too Large
Lines changed: 1669
Limit: 1000 lines
Action Required: Break into smaller, atomic PRs

📋 Best Practices for Large Changes

Refactoring + Features: Separate into 2 PRs
Multiple Features: One PR per feature
Database + Code: Separate migration from logic
Generated Code: Separate from manual changes

🚫 This PR is blocked from merging until size limits are met.

cursor · 2026-07-19T21:41:28Z

Re: the PR-size policy comment above — agreed, this PR grew too large by trying to fix the whole pre-existing lint/mypy/pytest baseline in one shot. Going forward, new CI-pipeline work (wiring pre-commit run into CI, fixing fail-fast/non-blocking gaps so PRs are reliably blocked on real errors) is being split into a separate, narrowly-scoped PR rather than added here. This PR is being left as the (already-applied) lint/type/pytest-config remediation batch plus the review-comment fixes above.

… contract scanner false-positive fix, pytest.ini Applied from cognitive-engine-graphs-open-pr-remediation-v2 125/apply.sh (transactional transformer). - Converge 8 workflows: triggers that never ran, gates that never blocked, autofix wiring - tools/contract_scanner.py: resolve inherited false positives (absorbs PR #124 scope) - pytest.ini: align test discovery with CI Post-checks passed: git diff --check, contract scanner AST parse + clean scan, changed-path allowlist.

github-actions · 2026-07-22T02:09:11Z

❌ Too Many Files Changed
Changed: 88 files
Limit: 50 files
Action Required: Split into multiple focused PRs

❌ PR Too Large
Lines changed: 1785
Limit: 1000 lines
Action Required: Break into smaller, atomic PRs

📋 Best Practices for Large Changes

Refactoring + Features: Separate into 2 PRs
Multiple Features: One PR per feature
Database + Code: Separate migration from logic
Generated Code: Separate from manual changes

🚫 This PR is blocked from merging until size limits are met.

github-advanced-security · 2026-07-22T02:10:18Z

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

…de-sync, pr-review-enforcement, terminology-guard Applied from cognitive-engine-graphs-open-pr-remediation-v2 126/apply.sh on the rebased #125 baseline. Post-checks passed: git apply --check, git diff --check, YAML validation on all four workflows, changed-path allowlist.

- Add hypothesis>=6.100,<7 to requirements-ci.txt: tests/property/ requires hypothesis, declared only in the Poetry dev group; CI installs via requirements files, so Contract Enforcement test collection fails on main. - Remove dead link docs/DEPLOYMENT.md -> ../iac/README.md (no iac/ directory exists), which fails Docs-Code Sync 'Check Markdown Links' on main. Both defects pre-date the PR #125/#126 CI-foundation remediation and were exposed once the gates began running. Verified locally: tests/property/ passes (11 tests), docs relative-link check clean. Co-authored-by: Manus PR Remediator <pr-remediator@manus.bot>

github-actions · 2026-07-22T20:09:25Z

❌ Too Many Files Changed
Changed: 88 files
Limit: 50 files
Action Required: Split into multiple focused PRs

❌ PR Too Large
Lines changed: 1785
Limit: 1000 lines
Action Required: Break into smaller, atomic PRs

📋 Best Practices for Large Changes

Refactoring + Features: Separate into 2 PRs
Multiple Features: One PR per feature
Database + Code: Separate migration from logic
Generated Code: Separate from manual changes

🚫 This PR is blocked from merging until size limits are met.

sonarqubecloud · 2026-07-22T20:09:28Z

Quality Gate failed

Failed conditions
C Security Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

💡 Need a hand with PR review? Try Gitar by Sonar!

…de-sync, pr-review-enforcement, terminology-guard Applied from cognitive-engine-graphs-open-pr-remediation-v2 126/apply.sh on the rebased #125 baseline. Post-checks passed: git apply --check, git diff --check, YAML validation on all four workflows, changed-path allowlist.

cryptoxdog · 2026-07-22T20:36:53Z

Closing as superseded by the split series #130–#135 (plus #129 for the scanner hunk):

Split	PR	Content from this branch
1/6	#130	mechanical `ruff --fix` + `ruff format` for engine/, l9_core/, tools/ (from `bb92eb8`)
2/6	#131	mechanical `ruff --fix` + `ruff format` for tests/ (from `bb92eb8`)
3/6	#132	manual ruff/mypy corrections (`f4cca2f`, `a539a17`, `0916321`, `eb5e8af`) + N818 per-file-ignore
4/6	#133	pytest marker registration + pytest.ini/pyproject config repair (`42fdbd1` + pytest.ini hunk of `9b0d03c`)
5/6	#134	Makefile `lint-fix` target + working lint-autofix workflow (`77c5dd4`, `9cd837d`)
6/6	#135	workflow trigger fixes (literal `on:` branches) + quality-gate `needs['...']` bracket expressions (filtered `9b0d03c`)

Deliberately excluded (per maintainer decision): the coverage --ignore suppressions and -m unit narrowing, the Semgrep runner replacement, and the fail-open GitGuardian change. These should be re-proposed separately with justification if still wanted.

#126 has been restacked onto #135's branch and will auto-retarget to main when #135 merges.

Mechanical-only remediation of pre-existing lint/format debt. Extracted from #125 (commit bb92eb8), split to satisfy the 50-file PR policy limit. No behavior changes. Part 1 of 2 (companion: tests/ formatting PR).

Mechanical-only remediation of pre-existing lint/format debt. Extracted from #125 (commit bb92eb8), split to satisfy the 50-file PR policy limit. No behavior changes. Part 2 of 2 (companion: engine/l9_core/tools formatting PR).

Non-autofixable remediation extracted from #125 (commits f4cca2f, a539a17, 0916321, eb5e8af): - manual Ruff fixes across engine/ and affected tests - mypy errors blocking the ci-quality lint gate (outcomes engine, P2_9_llm_schemas, and related modules) - wrong keyword arguments in GraphSyncClient envelope builder - wrong DomainPackLoader keyword argument in test_injection.py - pyproject: per-file N818 ignore for chassis/errors.py (stable serialized error-type name; renaming would break wire format) Local verification: ruff format --check (20 files pass), ruff check (all pass), mypy engine/ --config-file=pyproject.toml --ignore-missing-imports --exclude chassis (no issues, 131 files).

Extracted from #125 (commit 42fdbd1 + pytest.ini hunk of 9b0d03c): - pytest.ini: register compliance/performance/slow/contract/finding markers so --strict-markers no longer rejects marked tests - pytest.ini: drop global -x (stop-on-first-failure hid the true failure count in CI); add -ra for skip/xfail reporting - pyproject.toml: sync the [tool.pytest.ini_options] marker list and document that pytest.ini is the authoritative config Local verification: pytest --collect-only completes with zero collection errors (previously interrupted by strict-marker rejections).

Filtered extraction from #125 (commit 9b0d03c), workflows only: - ci.yml / codeql.yml / docker-build.yml / supply-chain.yml / release-drafter.yml: replace ${{ vars.* }} branch triggers with literal main/develop — GitHub never evaluates expressions in the 'on:' block, so these workflows never triggered - ci.yml: install lint deps from requirements-ci.txt (canonical set) and make mypy consistent + blocking (was || echo non-blocking) - compliance.yml: delegate Cypher injection check to the canonical tools/contract_scanner.py instead of a second divergent regex; align mypy invocation with the CI gate (drop --strict divergence) - refactoring-validation.yml: gate the deep validation to refactor/ branches or manual dispatch; align mypy invocation - ci-quality.yml: fix needs.lint-format / needs.secrets-scan / needs.yaml-validate expressions to bracket syntax (hyphenated job ids resolve to empty string with dot syntax, so gates never fired); add missing semgrep failure branch to the quality-gate summary Deliberately excluded per review: replacement Semgrep runner, GitGuardian fail-open gating, coverage -m unit narrowing and the five --ignore test exclusions, tools/contract_scanner.py hunk (#129). All 8 workflow YAMLs parse cleanly.

style: mechanical ruff --fix + format for engine/, l9_core/, tools/ (split 1/6 of #125)

style: mechanical ruff --fix + format for tests/ (split 2/6 of #125)

fix: manual ruff/mypy corrections (split 3/6 of #125)

fix: pytest marker registration + config repair (split 4/6 of #125)

feat: make lint-fix target + working lint-autofix workflow (split 5/6 of #125)

fix(ci): workflow trigger + quality-gate expression repair (split 6/6 of #125)

cursoragent and others added 7 commits July 19, 2026 21:04

github-code-quality Bot found potential problems Jul 19, 2026

View reviewed changes

This was referenced Jul 22, 2026

feat: GRAPH-side Redis Streams adapter — closes bidirectional ENRICH↔GRAPH loop #95

Closed

ci: add recursive pass validation gates #114

Open

fix(ci): FIXES PREEXISTING CI FAILURES IN MAIN — hypothesis dep + dead docs link #128

Merged

chore(ci): trigger CI re-run against updated main

9c9b3bf

This was referenced Jul 22, 2026

style: mechanical ruff --fix + format for engine/, l9_core/, tools/ (split 1/6 of #125) #130

Merged

style: mechanical ruff --fix + format for tests/ (split 2/6 of #125) #131

Merged

fix: manual ruff/mypy corrections (split 3/6 of #125) #132

Merged

This was referenced Jul 22, 2026

fix: pytest marker registration + config repair (split 4/6 of #125) #133

Merged

feat: make lint-fix target + working lint-autofix workflow (split 5/6 of #125) #134

Merged

fix(ci): workflow trigger + quality-gate expression repair (split 6/6 of #125) #135

Merged

cryptoxdog mentioned this pull request Jul 22, 2026

fix(ci): resolve inherited contract scanner false positives blocking all PRs #124

Closed

cryptoxdog closed this Jul 22, 2026

cryptoxdog added a commit that referenced this pull request Jul 23, 2026

Merge pull request #130 from Quantum-L9/style/ruff-mechanical-engine

2018ca1

style: mechanical ruff --fix + format for engine/, l9_core/, tools/ (split 1/6 of #125)

cryptoxdog added a commit that referenced this pull request Jul 23, 2026

Merge pull request #131 from Quantum-L9/style/ruff-mechanical-tests

1d6b8d9

style: mechanical ruff --fix + format for tests/ (split 2/6 of #125)

cryptoxdog added a commit that referenced this pull request Jul 23, 2026

Merge pull request #132 from Quantum-L9/fix/ruff-mypy-manual

ecfab67

fix: manual ruff/mypy corrections (split 3/6 of #125)

cryptoxdog added a commit that referenced this pull request Jul 23, 2026

Merge pull request #133 from Quantum-L9/fix/pytest-config

3a17aa9

fix: pytest marker registration + config repair (split 4/6 of #125)

cryptoxdog added a commit that referenced this pull request Jul 23, 2026

Merge pull request #134 from Quantum-L9/feat/lint-autofix-workflow

95b59ff

feat: make lint-fix target + working lint-autofix workflow (split 5/6 of #125)

cryptoxdog added a commit that referenced this pull request Jul 23, 2026

Merge pull request #135 from Quantum-L9/fix/workflow-triggers-gates

eaff985

fix(ci): workflow trigger + quality-gate expression repair (split 6/6 of #125)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Enable working CI lint autofix + remediate pre-existing ruff/mypy/pytest errors#125

Enable working CI lint autofix + remediate pre-existing ruff/mypy/pytest errors#125
cryptoxdog wants to merge 10 commits into
mainfrom
cursor/enable-ci-autofix-ddaf

cryptoxdog commented Jul 19, 2026

Uh oh!

github-actions Bot commented Jul 19, 2026

Uh oh!

Uh oh!

Uh oh!

cursor Bot Jul 19, 2026

Uh oh!

github-actions Bot commented Jul 19, 2026

Uh oh!

cursor Bot commented Jul 19, 2026

Uh oh!

github-actions Bot commented Jul 22, 2026

Uh oh!

github-advanced-security AI commented Jul 22, 2026

Uh oh!

github-actions Bot commented Jul 22, 2026

Uh oh!

sonarqubecloud Bot commented Jul 22, 2026

Uh oh!

cryptoxdog commented Jul 22, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

cryptoxdog commented Jul 19, 2026

Summary

Verification

Out of scope (flagged, not fixed)

Uh oh!

github-actions Bot commented Jul 19, 2026

Uh oh!

Uh oh!

Uh oh!

cursor Bot Jul 19, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot commented Jul 19, 2026

Uh oh!

cursor Bot commented Jul 19, 2026

Uh oh!

github-actions Bot commented Jul 22, 2026

Uh oh!

github-advanced-security AI commented Jul 22, 2026

What Enabling Code Scanning Means:

Uh oh!

github-actions Bot commented Jul 22, 2026

Uh oh!

sonarqubecloud Bot commented Jul 22, 2026

Quality Gate failed

Uh oh!

cryptoxdog commented Jul 22, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants