Skip to content

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

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

chore(governance): auto-seed org templates from Quantum-L9/.github#233
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
  • CODE_OF_CONDUCT.md
  • CONTRIBUTING.md
  • .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/ci-failure.yml
  • .github/ISSUE_TEMPLATE/config.yml
  • .github/ISSUE_TEMPLATE/gov-violation.yml
  • .github/ISSUE_TEMPLATE/seed-ci-failure.yml
  • .github/pull_request_template.md
  • .github/PULL_REQUEST_TEMPLATE/agent.md
  • .github/workflows/l9-lint-test-node.yml
  • .github/governance/semgrep-finding-policy.yaml
  • 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 3460e14 to 7599105 Compare August 23, 2026 20:16
@github-actions

github-actions Bot commented Aug 23, 2026

Copy link
Copy Markdown

⚠️ Large PR Warning
Reviewable lines changed: 830
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.

@github-actions

github-actions Bot commented Aug 23, 2026

Copy link
Copy Markdown

L9 Audit Harness Report

  • Generated: 2026-08-24T00:51:14.177068+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 15
🔵 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,45 @@
# Managed by Quantum-L9/.github. Pinned to a tag so main can move safely.
Comment thread .github/workflows/l9-lint-test-node.yml Fixed
Comment thread .github/workflows/l9-lint-test-node.yml Fixed

@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: 7599105600

ℹ️ 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 thread CONTRIBUTING.md
3. Publish **only** with:

```bash
PR_REMEDIATE=0 make pr

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 Add the advertised make pr target

This is presented as the only permitted publication path, but the repository's Makefile has no pr target (make -n pr returns “No rule to make target 'pr'”), and the document also forbids every direct alternative. Contributors following these instructions therefore cannot publish a change; either provide the target or document a command that exists in this repository.

Useful? React with 👍 / 👎.

Comment thread CODE_OF_CONDUCT.md
- Open [`gov-violation.yml`](.github/ISSUE_TEMPLATE/gov-violation.yml) for a public, routable report.
- Use this repository's Security Advisory form for a confidential / reporter-privacy path (see SECURITY.md).

Do not "mention @platform" in markdown as the enforcement action. The resolvable owner is the CODEOWNERS team `@Quantum-L9/platform` on `.github/`, `SECURITY.md`, and `CODEOWNERS` only.

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 Align the claimed enforcement owner with CODEOWNERS

This says @Quantum-L9/platform is the resolvable CODEOWNERS owner for the listed paths, but the checked-in .github/CODEOWNERS assigns both the repository default and /.github/ solely to @cryptoxdog and never mentions the platform team. Consequently these reports and governance changes do not receive the ownership enforcement promised here; add the team to CODEOWNERS or name the owner that is actually configured.

Useful? React with 👍 / 👎.

@cryptoxdog
cryptoxdog force-pushed the chore/auto-seed-governance branch 3 times, most recently from 4ce5b10 to 8bee38a Compare August 23, 2026 21:44
@cryptoxdog
cryptoxdog force-pushed the chore/auto-seed-governance branch 3 times, most recently from bd36c27 to ea4cfb3 Compare August 23, 2026 23:15
@claude

claude Bot commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

Remediated this PR's five failing checks (pushed on this branch, no history rewrite):

  • Pre-commit / CI Gate — the trailing-whitespace hook was stripping the two-space markdown hard breaks in CODE_OF_CONDUCT.md's enforcement entries; they're now separate paragraphs, rendering the same.
  • Scorecard + Sonar (governance.yml) — added a top-level permissions: contents: read and pinned both reusable-workflow callees to the commit SHA behind the v1 tag (7ed3ab86), verified against the file's own preflight (git ls-remote … refs/tags/v1) before pinning. The header comment now records SHA-bump-on-reseed instead of tag motion, keeping the pin record.
  • Enforce PR Policies (size) — the gate blocks at 1000 reviewable added lines; this seed carried 1213. Per the gate's required action, the four lint/test toolchain files (biome.json, .biomeignore, .vscode/extensions.json, l9-lint-test-node.yml, ~383 lines) moved to sibling PR chore(governance): seed lint/test toolchain configs #236, leaving this PR at ~838. Nothing is dropped — chore(governance): seed lint/test toolchain configs #236 carries them with the Sonar/Scorecard hardening applied (lockfile-required installs, --ignore-scripts, npx --no-install).

One deliberate trade to flag: SHA-pinning governance.yml means future governance releases no longer propagate by force-moving the v1 tag — a re-seed must bump the pinned SHA (preflight retained in the file). This matches the repo's existing convention of full-SHA pins everywhere, but it does diverge from the org pack's tag-motion design; if the pack should stay tag-pinned, that policy call belongs upstream in Quantum-L9/.github.

Not merging either PR — both are left for review.


Generated by Claude Code

@claude

claude Bot commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

Update: the remediation pushed here at bf635a5 was discarded minutes later by the seeding automation force-pushing a fresh identical payload (da1ca4b — tree-identical to the original ea4cfb3; this branch has been force-regenerated every 20–40 minutes today per its workflow-run history). Consumer-side fixes cannot stick on this branch.

The remediation has been re-landed durably on sibling branches the seeder does not control, per the seed's own missing-only doctrine:

Once those two merge, all 18 seeded files exist on main and the missing-only seeder has nothing left to propose — this PR empties or closes on its next regeneration. Until then this PR will stay red on its own regenerated, unfixed payload; the durable fix for the payload itself (and the force-push cadence) lives upstream in Quantum-L9/.github.

No further pushes to this branch from me — they would just be clobbered again. Not merging anything.


Generated by Claude Code

@cryptoxdog
cryptoxdog force-pushed the chore/auto-seed-governance branch from da1ca4b to 171af46 Compare August 23, 2026 23:58
claude Bot added a commit that referenced this pull request Aug 24, 2026
The lint/test toolchain half of the org auto-seed, split out of #233 to fit the
reviewable-size gate. Biome as the single JS/TS/JSON formatter and linter owner,
editor recommendations, and the org Node lint/test workflow — hardened so
installs require a committed lockfile and run with --ignore-scripts, and tsc
runs via npx --no-install (Sonar S6505/S8543, Scorecard Pinned-Dependencies).

Both Node jobs skip on this Python-only repo via the detect-node guard.
@cryptoxdog
cryptoxdog force-pushed the chore/auto-seed-governance branch from 171af46 to 374cd25 Compare August 24, 2026 00:51
@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

@claude

claude Bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Closing as superseded — not merged. The entire seed payload is now on main, landed through branches the seeding automation does not regenerate.

Coverage proof. All 18 destinations from this PR's original payload (ea4cfb3) exist on main at 614c08b:

Delivered by Files Merge commit
#236 biome.json, .biomeignore, .vscode/extensions.json, .github/workflows/l9-lint-test-node.yml 9936954
#237 the 14 governance / template / community files 614c08b

The two file sets are disjoint; together they are exactly the 18. Verified file-by-file with git cat-file -e origin/main:<path> — zero missing.

Semantic difference, stated explicitly. Of the 14 files this PR currently proposes, 12 are byte-identical to main. Two differ, and both differences are deliberate hardening the generated payload lacks:

  • CODE_OF_CONDUCT.md — trailing-whitespace hard breaks removed (they fail the trailing-whitespace pre-commit hook, which is what kept this PR's Pre-commit / CI Gate red).
  • .github/workflows/governance.yml — top-level permissions: contents: read added (Scorecard Token-Permissions), and both reusable-workflow callees pinned to a full commit SHA (Scorecard Pinned-Dependencies, Sonar S7637).

Why this PR could not be fixed in place. Its branch was force-regenerated by the seeding automation roughly every 20–40 minutes; remediation commits pushed here at bf635a5 were discarded within minutes by an identical fresh seed (da1ca4b, then 171af46, then 374cd25). Consumer-side fixes cannot persist on it.

One upstream note worth carrying back. The pin on governance.yml must be the commit that annotated tag v1 peels to (refs/tags/v1^{}3e841ea4…), not the tag object SHA that refs/tags/v1 returns (7ed3ab86…). The tag-object SHA resolves to no commit, and a caller pinned to it fails to start with zero jobs. We hit exactly that on #237 and corrected it there.

Because main now satisfies the seed's missing-only contract, future regenerations should propose nothing — except the two hardened files above, where the org pack's raw content still differs from what this repo needs. Reconciling that belongs upstream in Quantum-L9/.github (payload content, and the tag-motion vs SHA-pin decision).


Generated by Claude Code

@claude claude Bot closed this Aug 24, 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