Complete policy alignment roadmap audit
This commit is contained in:
@@ -1,6 +1,6 @@
|
|||||||
# Implementation Plan: Standard Repository Policy Alignment
|
# Implementation Plan: Standard Repository Policy Alignment
|
||||||
|
|
||||||
Status: In progress.
|
Status: Complete (2026-09-28); release pending.
|
||||||
|
|
||||||
## Scope and execution instructions
|
## Scope and execution instructions
|
||||||
|
|
||||||
@@ -345,7 +345,23 @@ No production CI configuration experiments or network publication are authorized
|
|||||||
|
|
||||||
## Stage 7: Verify final alignment and close the roadmap
|
## Stage 7: Verify final alignment and close the roadmap
|
||||||
|
|
||||||
Status: Pending.
|
Status: Complete (2026-09-28); release pending.
|
||||||
|
|
||||||
|
Verification: Compared all seven policies with pinned upstream Git objects:
|
||||||
|
testing and meta common text match after metadata/template removal; release
|
||||||
|
common text matches with only the selected local validation section; agents,
|
||||||
|
documentation, architecture, and OSS differences are the reviewed local
|
||||||
|
customizations. Confirmed seven per-file source/version/date stamps, no retained
|
||||||
|
template sections, attribution material scope including release policy, local
|
||||||
|
license texts and pinned notices, README navigation, and immutable-tag footer
|
||||||
|
instructions. The retained checker and publication tests cover selected gates,
|
||||||
|
candidate identity, one validation call, exact ref publication, failure
|
||||||
|
uncertainty, and asset safety. `GOWORK=off go test -mod=readonly -race -count=1
|
||||||
|
./...`, `GOWORK=off go vet -mod=readonly ./...`, `GOWORK=off go mod tidy
|
||||||
|
-diff`, tracked Go formatting, shell syntax, documentation checks through the
|
||||||
|
suite, `git diff --check`, and a synthetic three-target asset build with host
|
||||||
|
version smoke all passed. No real publication, tag, push, or historical release
|
||||||
|
rewrite occurred.
|
||||||
|
|
||||||
1. Compare all seven adopted policies against their exact pinned upstream files.
|
1. Compare all seven adopted policies against their exact pinned upstream files.
|
||||||
Confirm removed template instructions, correct source/version/date metadata,
|
Confirm removed template instructions, correct source/version/date metadata,
|
||||||
|
|||||||
@@ -1,6 +1,14 @@
|
|||||||
# Align Narratio With Standard Repository Policies
|
# Align Narratio With Standard Repository Policies
|
||||||
|
|
||||||
Status: Accepted; implementation pending.
|
Status: Implemented (2026-09-28); release pending.
|
||||||
|
|
||||||
|
Implementation evidence: The [implementation plan](implementation.md) records
|
||||||
|
completion and verification of each bounded unit. Seven adopted policies are
|
||||||
|
credited at the pinned source revision; the local release checker, runbook,
|
||||||
|
publication tests, CI references, and OSS notices now follow the selected
|
||||||
|
workflow. The full race-enabled suite, vet, module/format/shell checks, and
|
||||||
|
synthetic release assets passed. No source release or asynchronous asset
|
||||||
|
delivery was initiated by this implementation work.
|
||||||
|
|
||||||
## Goal and Approved Scope
|
## Goal and Approved Scope
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user