Skip to content

fix(docker): install git for VCS deps; drop .suite6-config.json from the scaffold - #151

Open
cryptoxdog wants to merge 5 commits into
mainfrom
fix/docker-git-deps-and-proprietary-license
Open

fix(docker): install git for VCS deps; drop .suite6-config.json from the scaffold#151
cryptoxdog wants to merge 5 commits into
mainfrom
fix/docker-git-deps-and-proprietary-license

Conversation

@cryptoxdog

Copy link
Copy Markdown
Collaborator

Three commits that had accumulated on this branch without a PR. The last one (02f6681, Jul 24) had never been pushed.

Summary

  • 9ef51d1 — Docker VCS deps. Installs git in Dockerfile, Dockerfile.prod, and chassis/Dockerfile.chassis so the constellation-node-sdk git dependency resolves during build. Fixes the Poetry prod install and realigns pyproject.toml / poetry.lock / requirements.txt. Also switches LICENSE to the proprietary text.
  • fea9047 — Diagnostics. Adds docs/github-ruleset-diagnostics.md, a command log from the org-ruleset investigation.
  • 02f6681 — Suite-6 cut-over, phase 4. Removes .suite6-config.json and its entry in tools/l9_template_manifest.yaml. SETUP_QUICK_START.md already declares this config stale and CANONICAL_LAW.md is headed "Post-Suite-6", but the manifest still carried it, so every newly scaffolded L9 repo inherited dead configuration. Scoped deliberately to the config removal — the manifest's other pending edits belong to the L9_META injector work.

Test plan

  • CI Docker build succeeds with the git-dependency install
  • Scaffold a fresh repo from the template and confirm no .suite6-config.json appears

Made with Cursor

cryptoxdog and others added 3 commits July 23, 2026 17:00
… deps

- Add git to apt-get install in Dockerfile, chassis/Dockerfile.chassis, and
  Dockerfile.prod build stages so pip/poetry can resolve git+https
  dependencies (previously failed with "Cannot find command 'git'").
- Fix Dockerfile.prod poetry install: --no-dev is deprecated, replaced with
  --only main --no-root (the latter avoids failing on a missing README.md
  before it's copied into the build context). Removed the silent pip
  fallback in favor of failing fast.
- Align requirements.txt with pyproject.toml (redis, numpy versions) and
  add openai/asyncpg/python-multipart to pyproject.toml to remove
  dependency drift between the two manifests. Regenerated poetry.lock.

chore(license): replace MIT LICENSE with Quantum AI Partners proprietary
license, matching the README's existing "proprietary" claim and the
org-wide license standardization applied across other Quantum-L9 repos.
Adds license = "LicenseRef-Proprietary" to pyproject.toml.

Co-authored-by: Cursor <[email protected]>
Records the diagnostic commands run while investigating org-level GitHub
ruleset enforcement for Quantum-L9 (repo/org ruleset state, plan-tier
gating, the CI Gate ruleset's invalid empty ref_name.include, CodeQL
coverage, and the post-Enterprise-upgrade re-check) for future reference.

Co-authored-by: Cursor <[email protected]>
SETUP_QUICK_START.md already declares this config stale and CANONICAL_LAW.md
is headed "Post-Suite-6", but the file stayed in l9_template_manifest.yaml,
so every newly scaffolded L9 repo inherited dead configuration.

Phase 4 of the Suite-6 cut-over. Scoped deliberately to the config removal;
the manifest's other pending edits belong to the L9_META injector work.

Co-authored-by: Cursor <[email protected]>
@github-actions

github-actions Bot commented Jul 27, 2026

Copy link
Copy Markdown

⚠️ Large PR Warning
Reviewable lines changed: 627
Warning threshold: 300 lines
Consider splitting for easier review

📋 Best Practices for Large Changes

  1. Refactoring + Features: Separate into 2 PRs
  2. Multiple Features: One PR per feature
  3. Database + Code: Separate migration from logic
  4. Generated Code: Exclude it from reviewable-size accounting

This PR passes the blocking limit but is larger than recommended.

cryptoxdog and others added 2 commits July 27, 2026 17:06
/v1/health returns 200 while the engine is still warming up, so an
unready container was reported healthy. Also ignores the mypy venv.
The prod image healthcheck only asserted that /v1/health answered, so a
container whose Neo4j driver or domain loader failed to come up still
reported healthy and took traffic. Matches the dev Dockerfile and
Dockerfile.chassis change in this PR.

Co-authored-by: Cursor <[email protected]>
@sonarqubecloud

Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

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

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

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