mirror of https://github.com/boshu2/agentops.git synced 2026-09-14 15:08:13 +08:00

Files

T

Bo 6d5d111faf feat(skills): land four-vendor skill corpus (#803 )

## Summary
- Lands the AgentOps skill corpus across source and Codex wrappers,
including Gemini image targets.
- Integrates the skill branch onto current origin/main and refreshes
generated manifests/catalogs.
- Normalizes local next-work queue enum drift and fixes shellcheck in
alias-collision validation.

## Validation
- bash scripts/regen-all.sh --check
- bash scripts/validate-skill-schema.sh
- bash tests/skills/test-token-budgets.sh
- bash tests/skills/run-all.sh
- bash scripts/audit-codex-parity.sh && bash
scripts/validate-codex-override-coverage.sh && bash
scripts/validate-codex-generated-artifacts.sh --scope worktree && bash
scripts/validate-codex-api-conformance.sh && bash
scripts/validate-codex-runtime-sections.sh && bash
scripts/lint-codex-native.sh
- bash skills/heal-skill/scripts/heal.sh --strict
- PRE_PUSH_SKIP_MKDOCS=1 bash scripts/pre-push-gate.sh --fast

MkDocs strict remains skipped locally via the documented
PRE_PUSH_SKIP_MKDOCS=1 override because the repo currently emits
repo-wide strict-link warnings unrelated to this landing; CI remains
authoritative.

2026-06-06 23:44:42 -04:00

12-factors-validation-lens.md

feat(docs,skills): rebuild Pages site with MkDocs Material + harden RPI orchestrator delegation contract

2026-04-19 10:37:58 -04:00

convergence-thesis-discussion.md

feat(skills): land four-vendor skill corpus (#803 )

2026-06-06 23:44:42 -04:00

devops-for-vibe-coding.md

docs(positioning): wiki-framing sweep across all surface docs (soc-9xn0) (#262 )

2026-05-07 21:04:47 -04:00

hn-devto-article.md

docs(positioning): prepare HN devto article draft

2026-04-11 22:16:16 -04:00

README.md

fix(docs): rename docs/INDEX.md -> docs/documentation-index.md to resolve case collision with docs/index.md

2026-04-26 19:32:13 -04:00

README.md

Positioning

AgentOps is the operational layer for coding agents. The current public framing lives in PRODUCT.md and README.md: bookkeeping, validation, primitives, and flows so every session starts where the last one left off.

Use DevOps and 12-factor language here as supporting doctrine, lineage, or bridge language for specific audiences. They are no longer the category headline.

The 12-factor doctrine remains a supporting lifecycle/control-plane lens. It explains how the internal proof contract and software-factory control plane work operationally, but it does not define the product.

Use this section as the entry point for positioning work:

DevOps for Vibe-Coding - bridge narrative for readers arriving from DevOps, vibe-coding, or 12-factor language
12 Factors Validation Lens - supporting lifecycle/control-plane lens for the internal proof contract and software-factory control plane
Convergence Thesis Discussion Draft - draft for the pinned GitHub Discussion
HN / dev.to Article Draft - long-form GTM draft for external posting

Back: Docs Index