You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ec3399e
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: AGENTS.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -414,6 +414,7 @@ For changes outside existing owner authorization, obtain direction before changi
414
414
- Repeated permission questions for already authorized work.
415
415
- GitHub Actions MUST expose exactly three plainly named workflows: CI combines build and ordinary project tests for PR/push/manual checks; Benchmarks runs all load/comparison suites, produces complete authenticated measurements and then qualifies/publishes the website; Release builds the solution, real database images/distribution and packages, then creates a GitHub Release and immutable version tag. Do not split Tests or Website into additional workflows (explicit owner correction 2026-10-03 supersedes the earlier five-workflow layout).
416
416
- Release tags MUST be `v<major>.<minor>.<yyMMdd>.<daily-build>`: major/minor are configured in source, the third component is the UTC date and the fourth starts at 1 each day and increases without tag reuse or overwrite. Build/package/image/manifest identities MUST agree; reruns recover their original reservation. Release automation is authorized to create the corresponding Git tag, GitHub Release and versioned database image/package assets; preserve protections and qualification gates (owner direction 2026-10-03).
417
+
- KeyLoad product release packaging and publication are deferred until the owner explicitly requests a release or confirms product readiness. Keep Release prepared and manual; do not dispatch package/image builds, create release tags or publish releases merely to prove this workflow while the product is unfinished (owner correction 2026-10-03).
417
418
- Repository-rule checks MUST always run inside the standard CI pipeline, never as a separate governance workflow (owner correction 2026-10-03).
418
419
- All comparative performance tests, including TimeSeries image checks, MUST run in one separate Benchmarks pipeline; do not name it Comparisons or create feature-specific comparison workflows. Preserve isolated Linux runners, real native topology, complete workloads and authenticated artifacts (owner clarification 2026-10-03).
419
420
- Fake production readiness, power-loss claims from process-kill tests, or unsupported performance supremacy.
| TASK-REL-TOOLS | REL-001/002/003 | capable script worker | scripts/Features/ReleaseDelivery helpers only | approved feature/ADR | syntax, actual source outputs through GitHub; no local tests |
12
12
| TASK-PIPE-TESTS | PIPE-001/002/004, REL-001/002 | capable C# worker | named workflow tests and new Features/ReleaseDelivery TUnit files | approved contracts | compiled unit/source/version cases in CI; no local tests |
13
13
| TASK-PIPE-LEAD | all | lead | workflows, central version, policies/docs, RF3 release distribution, source closure, delivery | serialized integration | inspect all diffs, static checks, scoped commit/push, GitHub evidence |
14
+
| TASK-REL-PACK-STAGE | REL-001/002 | script worker | version/CLI/context/asset helpers only | real run37116935776 NU5104; amended package-stage contract | freeze derived -dev package version; no suppression or local tests; lead owns workflow |
15
+
| TASK-REL-PACK-TEST | REL-001/002 | C# worker | ReleaseDelivery TUnit and role tests only | amended package-stage contract and agreed schema | real tool positive/tamper/retry assertions; GitHub CI |
14
16
15
17
-[x] Read policies/architecture; record exact owner correction first.
16
18
-[x] Read-only parallel provenance/release discovery and explicit safe write scopes.
0 commit comments