[wesley-dean]

Adopts coding_standards@v1.0.9 as repository governance and records the verified released snapshot under doc/standards/.

This PR also normalizes every repository ADR to the Accepted status convention, preserves supersession/deprecation as decision lineage rather than status, updates the ADR template so PR merge is the normal acceptance event, removes duplicate local documentation standards where the managed snapshot provides the governing equivalent, and maintains doc/decisions.md as the project decision summary.

Requested selector: coding_standards@v1.0.9
Resolved release: coding_standards@v1.0.9
Previous release: none
Source: https://github.com/wesley-dean/coding_standards.git
Archive SHA-256: 86e91725f30dc5d91a3c7f7158e17d6a8538519b3be10709440e179027c37a03
Destination: doc/standards
Release tag commit: 22e42d2583cc98d4a7db8c48e1ab0c459f76946e
Operation: initial adoption

[github-actions]

✅MegaLinter analysis: Success

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ BASH	shellcheck	25		0	0	1.16s
✅ PYTHON	bandit	1		0	0	1.6s
✅ REPOSITORY	betterleaks	yes		no	no	1.78s
✅ REPOSITORY	checkov	yes		no	no	26.59s
✅ REPOSITORY	gitleaks	yes		no	no	0.4s
✅ REPOSITORY	grype	yes		no	no	76.64s
✅ REPOSITORY	kingfisher	yes		no	no	8.48s
✅ REPOSITORY	secretlint	yes		no	no	2.1s
✅ REPOSITORY	semgrep	yes		no	no	29.19s
✅ REPOSITORY	syft	yes		no	no	2.15s
✅ REPOSITORY	trivy	yes		no	no	12.18s
✅ REPOSITORY	trivy-sbom	yes		no	no	0.27s
✅ REPOSITORY	trufflehog	yes		no	no	6.07s

Notices

📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining SECURITY_SUGGESTIONS: false)

See detailed reports in MegaLinter artifacts

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

• Documentation: Custom Flavors
• Command: npx mega-linter-runner@9.6.0 --custom-flavor-setup --custom-flavor-linters PYTHON_BANDIT,BASH_SHELLCHECK,REPOSITORY_CHECKOV,REPOSITORY_GITLEAKS,REPOSITORY_BETTERLEAKS,REPOSITORY_GRYPE,REPOSITORY_SECRETLINT,REPOSITORY_SEMGREP,REPOSITORY_SYFT,REPOSITORY_TRIVY,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,REPOSITORY_KINGFISHER

Show us your support by starring ⭐ the repository

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.