feat(ci): wire 2-of-3 lint scripts as advisory I0 jobs (soc-dspz #wire-2-of-3)#393
Merged
Conversation
Remove AI-slop opener (aphorisms, methodology laundry lists, "shovel"
metaphor, "Independent 3-judge audit" overclaim) and the in-cell italic
slogans. Drop "From agent opinions to engineering verdicts.", "AgentOps
is the shovel. Start digging.", "The point is not a bigger prompt. The
point is...", "Same playbook. New substrate.", "LLMs are engines.
Context is fuel.", and the unsubstantiated "Major engineering
organizations are already reorganizing..." line.
Restructure: move "See It Work" above "Install" so the demo lands
before the install matrix; merge "SDLC Control Plane, CDLC Mechanism"
and "Why Context Needs a Lifecycle" into one philosophy section ("Why
context is the lifecycle") with the SE→Agent mapping table leading;
add a Limitations section.
Swap the first transcript demo from `ao rpi` (CLI) to `/research`
(skill) so the corpus-loading value — citing prior decisions, planning
rules, and learnings — is visible in the first example.
Integrate the 4 wording softenings from upstream f7cc505
(autonomous → bounded; the synthetic-fake-executor disclaimer;
"the factory executes the queue").
All five AOP-CLAIM markers preserved; strict claim-ledger and
check-docs-learning-references both PASS. Net -23 lines.
Closes-scenario: soc-x0au#readme-deslop
Bounded-context: BC1-corpus
Evidence: README.md
soc-dspz asks for 3 advisory I0 jobs to wire in: - scripts/lint-evidence-lines.sh (PR #373, merged) - scripts/check-skill-catalog-drift.sh (PR #379, merged) - scripts/lint-skill-frontmatter.sh (PR #376, still open) This PR wires the 2 that are available on main. The 3rd (lint-skill-frontmatter) waits for #376 to merge; soc-dspz stays open until then. Changes: - .github/workflows/validate.yml: added lint-evidence-lines-advisory and check-skill-catalog-drift-advisory stanzas. Both 'continue-on-error: true' so they annotate via ::warning:: without blocking the merge gate. Each job is path-filtered: lint-evidence-lines on pull_request events, catalog drift on changes to skills/ or .github/. - docs/contracts/ci-jobs.yaml: 2 manifest entries, alphabetically slotted. - AGENTS-CI.md: regenerated via scripts/generate-ci-jobs-table.sh --write. - summary job 'needs:' list extended with both new advisory jobs. Promotion path per soc-dspz: I0 advisory -> T2 required after 1 week of clean runs. Add T2 promotion bead when ready. Validation: - python3 yaml.safe_load passes on both YAML files - scripts/validate-ci-policy-parity.sh: CI_JOBS_TABLE PASS (69 rows) Closes-scenario: soc-dspz#wire-2-of-3 Bounded-context: BC4-CI Evidence: scripts/validate-ci-policy-parity.sh
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
soc-dspz asks for 3 advisory I0 jobs to wire in. Two of the three source scripts are already on
main(after PRs #373, #379 merged); the third (scripts/lint-skill-frontmatter.shfrom #376) is still pending merge. Per the new agile invariant (soc-5qit, PR #392), the right move is to ship the unblocked part and leave the parent bead open for the third when #376 lands — instead of waiting for everything.What changed
.github/workflows/validate.ymllint-evidence-lines-advisory(PR-event triggered) andcheck-skill-catalog-drift-advisory(skills/CI path-filtered). Bothcontinue-on-error: trueso they emit::warning::annotations without blocking merges..github/workflows/validate.ymlsummary jobneeds:extended with both new advisory jobs.docs/contracts/ci-jobs.yamlAGENTS-CI.mdscripts/generate-ci-jobs-table.sh --write(69 rows).Promotion path
Per soc-dspz acceptance: I0 advisory → T2 required after one clean week of runs. File a follow-up bead to flip
continue-on-error: trueoff and promote both jobs to required.What's NOT in this PR
lint-skill-frontmatter-advisory— depends on PR feat(scripts): lint-skill-frontmatter — enforce required keys on SKILL.md frontmatter (soc-e8pj #skill-md-frontmatter-linter) #376 (open) addingscripts/lint-skill-frontmatter.sh. soc-dspz stays open after this merges; a follow-up small PR will add that 3rd stanza once feat(scripts): lint-skill-frontmatter — enforce required keys on SKILL.md frontmatter (soc-e8pj #skill-md-frontmatter-linter) #376 lands.Validation
python3 -c 'import yaml; yaml.safe_load(...)'parses both YAML files cleanscripts/validate-ci-policy-parity.sh:CI_JOBS_TABLE: PASS (69 rows)Closes-scenario: soc-dspz#wire-2-of-3
Bounded-context: BC4-CI
Evidence: scripts/validate-ci-policy-parity.sh