opc

Keep reportMissingImports at error; suppress only optional imports inline (#200) Adversarial review (round 3) found that globally downgrading reportMissingImports to warning hides real broken first-party imports: this repo has ~15 imports referencing modules that no longer exist (scripts.math_base, scripts.agentica_patterns.*, .memory_service, artifact_query, etc.) that ModuleNotFoundError at runtime. There is no CI gate (no .github), so Pyright/mypy are editor-only -- an earlier comment wrongly claimed mypy runs in CI. Revert reportMissingImports to error (its default) so genuinely-broken imports stay red and visible (tracked in #204). Silence only the guarded/optional import sites (anthropic try/except, z3/pgserver/tldr.api lazy or try-guarded) with targeted '# pyright: ignore[reportMissingImports]' at the import line. Correct the comment to drop the false CI claim. Result: 717 errors to 16, all genuine (15 broken first-party imports + 1 os-undefined bug); optional extras no longer error; no unrecognized-setting config warnings.

Merge pull request #203 from stephenfeather/agent-issue-199

Downgrade reportMissingImports to warning for optional/guarded imports (#200) Adversarial review (round 2, design) found that keeping reportMissingImports at error makes a default 'uv sync' checkout red for intentionally-optional imports: anthropic (try/except ImportError), z3/pgserver/tldr.api (lazy-imported), plus first-party modules that resolve only via runtime sys.path manipulation Pyright can't follow. That reintroduces the very noise issue #200 set out to remove. Downgrade reportMissingImports to warning; leave reportUndefinedVariable at error so genuinely-fatal NameError-at-import bugs stay hard errors. Result: a clean checkout now shows 1 error (the real os-undefined bug in math_router.py, tracked in #204) instead of 717, with no unrecognized-setting config warnings.

Fix invalid Pyright key reportPossiblyUnbound -> reportPossiblyUnboundVariable Adversarial review (round 1) found that Pyright 1.1.410 rejects 'reportPossiblyUnbound' with 'Config contains unrecognized setting', emitting a config error on every run and editor session -- the opposite of the noise-reduction goal. The earlier observed downgrade came from typeCheckingMode=basic, masking the bad key. Use the recognized diagnostic key reportPossiblyUnboundVariable. Verified: 'pyright --project pyproject.toml' emits no unrecognized-setting warnings; full re-audit holds at 24 genuine errors with the rule correctly at warning severity.