Skip to content

Security assurance hardening (stacked on #48) - #49

Merged
dbowm91 merged 3 commits into
feat/auto-20261117-7451c367from
feat/security-assurance-hardening-20261118
Nov 18, 2026
Merged

dbowm91 merged 3 commits into
feat/auto-20261117-7451c367from
feat/security-assurance-hardening-20261118

Conversation

@dbowm91

@dbowm91 dbowm91 commented Nov 18, 2026

Copy link
Copy Markdown
Contributor

Stacked on PR #48; this PR targets feat/auto-20261117-7451c367 to keep the security-assurance hardening separate from the dependency-fix scope.

Summary

  • Tighten enforcement and canonical dispatch boundaries across CLI, daemon, MCP, and tool routes.
  • Harden daemon HTTP handling, TUI task lifetimes, credential/secret handling, Python buffer safety, and output sanitization.
  • Add focused regression coverage and update dependency, Docker-context, architecture, and milestone-closure documentation.

Validation

  • make check — passed locally, including its dependency policy checks.
  • make check-python — passed: 4,437 passed, 1,728 skipped, 23 deselected, 16 xfailed; capability/architecture guards, stub parity, mypy, and pyright passed.
  • git diff --check — passed.
  • Docker image/runtime and Compose checks were not run locally because Docker/Compose are unavailable.

The regular PR workflow is filtered to main; manual Deep Checks will be dispatched for this head after the PR is created.

@dbowm91
dbowm91 merged commit 869ea1c into feat/auto-20261117-7451c367 Nov 18, 2026
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant