CalvinBackup/OBLITERATUS
1
0
Fork 0
mirror of https://github.com/elder-plinius/OBLITERATUS.git synced 2026-08-29 22:20:36 +02:00
Code Issues Packages Projects Releases Wiki Activity

chore(aiwg): refresh workspace to 2026.8.15

Browse Source
This commit is contained in:
Joseph Magly
2026-08-21 18:05:00 -04:00
parent cf3ff738fb
commit 586bad63f3
3 changed files with 12 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.aiwg/AIWG.md
+4 -1
View File
@@ -29,7 +29,8 @@ When a user asks whether AIWG is active or engaged in this project, run or read
### Tracker Authority Protocol
- Source of truth: [.aiwg/aiwg.config](./.aiwg/aiwg.config)
- Canonical tracker: `origin` (github; https://github.com/elder-plinius/OBLITERATUS.git)
- Internal/canonical tracker: `origin` (github; https://github.com/elder-plinius/OBLITERATUS.git)
- Customer issue tracker: not configured
- Primary repo remote: `origin`; CI remote: `origin`
- Secondary/mirror remotes: none configured
- Issue storage mode: not configured
@@ -41,6 +42,8 @@ Tracker access order for issue, PR, release, and CI-sensitive tracker operations
4. Stop and report a blocker.
- Project config decides tracker authority; installed/authenticated CLIs do not.
- Route internal engineering, delivery, and CI-sensitive issue work to the internal tracker.
- Route customer acknowledgements, follow-up, and closure to the customer tracker when configured.
- Git SSH remote access is repository sync, not issue-tracker API access.
- Do not file on mirror or secondary remotes just because their CLI is authenticated.
- Treat an unauthenticated tracker CLI as one failed access path, then continue probing MCP/app/API before blocking.
.aiwg/aiwg.config
+4 -4
View File
@@ -33,14 +33,14 @@
],
"installed": {
"all": {
"version": "2026.8.11",
"version": "2026.8.15",
"source": "bundled",
"installedAt": "2026-08-16T08:24:23.824Z",
"installedAt": "2026-08-21T22:02:07.869Z",
"deployedTo": {
"codex": {
"agents": 0,
"commands": 50,
"skills": 31,
"skills": 32,
"rules": 2
}
},
@@ -49,7 +49,7 @@
"bt6-maintainer": {
"version": "0.3.0",
"source": "project-local",
"installedAt": "2026-08-21T02:05:54.137Z",
"installedAt": "2026-08-21T22:00:58.629Z",
"deployedTo": {
"codex": {
"agents": 5,
AIWG.md
+4 -1
View File
@@ -74,7 +74,8 @@ When a user asks whether AIWG is active or engaged in this project, run or read
### Tracker Authority Protocol
- Source of truth: [.aiwg/aiwg.config](./.aiwg/aiwg.config)
- Canonical tracker: `origin` (github; https://github.com/elder-plinius/OBLITERATUS.git)
- Internal/canonical tracker: `origin` (github; https://github.com/elder-plinius/OBLITERATUS.git)
- Customer issue tracker: not configured
- Primary repo remote: `origin`; CI remote: `origin`
- Secondary/mirror remotes: none configured
- Issue storage mode: not configured
@@ -86,6 +87,8 @@ Tracker access order for issue, PR, release, and CI-sensitive tracker operations
4. Stop and report a blocker.
- Project config decides tracker authority; installed/authenticated CLIs do not.
- Route internal engineering, delivery, and CI-sensitive issue work to the internal tracker.
- Route customer acknowledgements, follow-up, and closure to the customer tracker when configured.
- Git SSH remote access is repository sync, not issue-tracker API access.
- Do not file on mirror or secondary remotes just because their CLI is authenticated.
- Treat an unauthenticated tracker CLI as one failed access path, then continue probing MCP/app/API before blocking.