chore(governance): auto-seed org templates from Quantum-L9/.github - #233
chore(governance): auto-seed org templates from Quantum-L9/.github#233cryptoxdog wants to merge 1 commit into
Conversation
3460e14 to
7599105
Compare
|
📋 Best Practices for Large Changes
✅ This PR passes the blocking limit but is larger than recommended. |
L9 Audit Harness Report
Step Results
Architecture Audit Findings
See Spec Coverage
See Next StepsAll checks passed. Safe to merge. |
| @@ -0,0 +1,45 @@ | |||
| # Managed by Quantum-L9/.github. Pinned to a tag so main can move safely. | |||
There was a problem hiding this comment.
💡 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".
| 3. Publish **only** with: | ||
|
|
||
| ```bash | ||
| PR_REMEDIATE=0 make pr |
There was a problem hiding this comment.
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 👍 / 👎.
| - 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. |
There was a problem hiding this comment.
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 👍 / 👎.
4ce5b10 to
8bee38a
Compare
bd36c27 to
ea4cfb3
Compare
|
Remediated this PR's five failing checks (pushed on this branch, no history rewrite):
One deliberate trade to flag: SHA-pinning Not merging either PR — both are left for review. Generated by Claude Code |
bf635a5 to
da1ca4b
Compare
|
Update: the remediation pushed here at 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 No further pushes to this branch from me — they would just be clobbered again. Not merging anything. Generated by Claude Code |
da1ca4b to
171af46
Compare
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.
171af46 to
374cd25
Compare
|
|
Closing as superseded — not merged. The entire seed payload is now on Coverage proof. All 18 destinations from this PR's original payload (
The two file sets are disjoint; together they are exactly the 18. Verified file-by-file with Semantic difference, stated explicitly. Of the 14 files this PR currently proposes, 12 are byte-identical to
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 One upstream note worth carrying back. The pin on Because Generated by Claude Code |




Automatically seeds org template files from
Quantum-L9/.github/templates/plus thel9-ci-pack/Core hub.Files in this PR
.github/workflows/governance.ymlCODE_OF_CONDUCT.mdCONTRIBUTING.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.yamlbiome.json.biomeignore.vscode/extensions.jsonExisting files were left untouched (missing-only seed), except a stock ESLint
l9-lint-test-node.ymlwhich is replaced with the Biome SDK caller.Governance caller is advisory (
strictdefaults false).Core pack callers are distributed here;
l9-ci-coreexecutes CI.Opened automatically by Quantum-L9/.github auto-seed.