Skip to content

chore(governance): auto-seed org templates from Quantum-L9/.github - #227

Closed
cryptoxdog wants to merge 1 commit into
mainfrom
chore/auto-seed-governance
Closed

chore(governance): auto-seed org templates from Quantum-L9/.github#227
cryptoxdog wants to merge 1 commit into
mainfrom
chore/auto-seed-governance

Conversation

@cryptoxdog

Copy link
Copy Markdown
Collaborator

Automatically seeds org template files from Quantum-L9/.github/templates/ plus the l9-ci-pack/ Core hub.

Files in this PR

  • .github/workflows/governance.yml
  • .github/labels.yml
  • CODE_OF_CONDUCT.md
  • CONTRIBUTING.md
  • SUPPORT.md
  • .github/FUNDING.yml
  • .github/ISSUE_TEMPLATE/1-bug.yml
  • .github/ISSUE_TEMPLATE/2-feature.yml
  • .github/ISSUE_TEMPLATE/3-task.yml
  • .github/ISSUE_TEMPLATE/4-incident.yml
  • .github/ISSUE_TEMPLATE/bug_report.yml
  • .github/ISSUE_TEMPLATE/ci-failure.yml
  • .github/ISSUE_TEMPLATE/config.yml
  • .github/ISSUE_TEMPLATE/feature_request.yml
  • .github/ISSUE_TEMPLATE/gov-violation.yml
  • .github/pull_request_template.md
  • .github/workflows/on-org-update.yml
  • .github/workflows/l9-lint-test-node.yml
  • biome.json
  • .biomeignore
  • .vscode/extensions.json

Existing files were left untouched (missing-only seed), except a stock ESLint l9-lint-test-node.yml which is replaced with the Biome SDK caller.
Governance caller is advisory (strict defaults false).
Core pack callers are distributed here; l9-ci-core executes CI.

Opened automatically by Quantum-L9/.github auto-seed.

@cryptoxdog
cryptoxdog force-pushed the chore/auto-seed-governance branch from 27bbb5d to 0c3a6e7 Compare August 22, 2026 20:18
@github-actions

Copy link
Copy Markdown

PR Too Large
Reviewable additions: 1347
Limit: 1000 added lines
(deletions: 0; total churn 1347 is warn-only)
Action Required: Break into smaller, atomic PRs

📋 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 is blocked until reviewable size limits are met.

@github-actions

github-actions Bot commented Aug 22, 2026

Copy link
Copy Markdown

L9 Audit Harness Report

  • Generated: 2026-08-22T21:15:05.788453+00:00
  • Repo root: /home/runner/work/Cognitive.Engine.Graphs/Cognitive.Engine.Graphs
  • Overall result: ✅ PASSED
  • Exit code: 0

Step Results

Step Status Exit Code Notes
Architecture Audit ✅ Passed 0
Spec Coverage ✅ Passed 0
Contract Wiring ✅ Passed 0

Architecture Audit Findings

Severity Count
🔴 CRITICAL 0
🟠 HIGH 0
🟡 MEDIUM 25
🔵 LOW 0

See artifacts/audit_report.md for full details.

Spec Coverage

  • ✅ Implemented: 37
  • ⚠️ Partial: 9
  • ❌ Missing: 0
  • Total features: 46
Category Implemented Partial Missing Total
gates 10 0 0 10
scoring 7 0 0 7
v1.1_node 2 0 0 2
v1.1_edge 2 0 0 2
v1.1_action 0 2 0 2
v1.1_scoring 1 1 0 2
action_handler 0 6 0 6
gds_algorithm 5 0 0 5
research_pattern 10 0 0 10

See artifacts/coverage_report.md for full details.

Next Steps

All checks passed. Safe to merge.

@@ -0,0 +1,33 @@
# Managed by Quantum-L9/.github. Pinned to a tag so main can move safely.
workflow_dispatch:

permissions:
contents: write
run: |
set -euo pipefail
case "${PACKAGE_MANAGER}" in
npm) if [ -f package-lock.json ]; then npm ci; else npm install; fi ;;
run: |
set -euo pipefail
case "${PACKAGE_MANAGER}" in
npm) if [ -f package-lock.json ]; then npm ci; else npm install; fi ;;

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0c3a6e7672

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +77 to +81
- name: Set up Node
uses: actions/setup-node@a0853c24544627f65ddf259abe73b1d18a591444 # v5.0.0
with:
node-version: ${{ env.NODE_VERSION }}
cache: ${{ env.PACKAGE_MANAGER }}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Do not run the Node preset in this Python-only repository

On every pull request and push to main, both Node jobs enable the npm cache even though a repo-wide search finds no package.json, package-lock.json, npm-shrinkwrap.json, or yarn.lock. The pinned setup-node documentation states that caching searches the repository root for a dependency file, so setup fails with a missing-lockfile error before the later no-tsconfig.json/no-test-script skip logic can run. Remove this Node preset or condition the jobs and caching on an actual Node manifest.

AGENTS.md reference: AGENTS.md:L16-L19

Useful? React with 👍 / 👎.

Comment on lines +29 to +33
if [ -f scripts/sync_ci_from_pack.py ]; then
python scripts/sync_ci_from_pack.py
else
echo "::notice::No sync_ci_from_pack.py found — skipping"
exit 0

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Include the implementation required by the sync receiver

When either org_template_updated or the manual dispatch invokes this workflow, this branch always exits successfully without syncing anything: a repo-wide search confirms that scripts/sync_ci_from_pack.py is not present and there is no other template-sync implementation. Consequently the diff remains empty and the advertised auto-sync PR is never created; include the sync script or fetch and execute the synchronization logic directly.

Useful? React with 👍 / 👎.

Comment thread CONTRIBUTING.md
Comment on lines +65 to +69
## This Repo's Own CI

`Quantum-L9/.github` validates itself on every PR/push to `main` — note that
none of the 12 files under `workflow-templates/` ever run as CI *in this
repo*; they only appear as starter-workflow choices in other repos' Actions

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Replace the org-backbone-specific CI instructions

This section identifies the current repository as Quantum-L9/.github and tells contributors that its CI validates workflow-templates/, l9-ci-pack/, .github/workflows/actionlint.yml, and ops/audit-sha-pins.sh. A repo-wide check shows that none of those paths exists in CEG, whose documented stack and test commands are Python-specific, so contributors following this guide cannot run or inspect the claimed gates. Replace this copied section with the actual CEG workflows and commands.

AGENTS.md reference: AGENTS.md:L16-L29

Useful? React with 👍 / 👎.

@cryptoxdog
cryptoxdog force-pushed the chore/auto-seed-governance branch from 0c3a6e7 to bf1beec Compare August 22, 2026 21:14
@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

@cryptoxdog cryptoxdog closed this Aug 22, 2026
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.

2 participants