Skip to content

docs(testing): document epic confidence workflows - #6928

Merged
serrrfirat merged 1 commit into
mainfrom
codex/docs-epic-testing-playbook
Jul 30, 2026
Merged

serrrfirat merged 1 commit into
mainfrom
codex/docs-epic-testing-playbook

Conversation

@serrrfirat

Copy link
Copy Markdown
Collaborator

Summary

  • Explain how local test evidence maps to pull-request, merge-queue, main, scheduled-deep, and release-artifact CI lanes.
  • Document how to extend typed journey evidence, generated lifecycle/state-machine coverage, regression tests, and mutation audits.
  • Add a reproducible local command for the generated product-surface Markdown/JSON matrix so engineers can get a current bird's-eye view without maintaining a second inventory.

Change Type

  • Bug fix
  • New feature
  • Refactor
  • Documentation
  • CI/Infrastructure
  • Security
  • Dependencies

Linked Issue

Related #6524

Validation

  • cargo fmt --all -- --check — Not applicable: Markdown-only change.
  • cargo clippy --all --benches --tests --examples --all-features -- -D warnings — Not applicable: no Rust or production code changed.
  • cargo build — Not applicable: no compiled source changed.
  • Relevant tests pass: journey and generated state-machine coverage gates, 90 passed.
  • cargo test --features integration if database-backed or integration behavior changed — Not applicable: no runtime or database behavior changed.
  • Manual testing: generated the product-surface JSON/Markdown report (123 capabilities, 24 journeys, zero missing rows), checked every relative Markdown link, ran git diff --check, and ran the mutation-harness self-tests.
  • If a coding agent was used and supports it, review-pr or pr-shepherd --fix was run before requesting review — structured Sol 5.6 medium review found one overstated merge-queue guarantee; it was corrected, and the final review returned no actionable findings.

Test Strategy

User behavior:

Engineers can use one playbook to select the correct test seam, understand when evidence runs, extend journey/lifecycle coverage, promote failures into regressions, audit assertion strength, and generate the current product-surface matrix locally.

Risk areas:

  • Model behavior
  • Browser
  • Side effect
  • Persistence
  • Security or permissions
  • External provider
  • Cross-component behavior

Tests added or updated:

  • Unit or contract: Not applicable: documentation-only change.
  • Reborn integration: Not applicable: no product behavior changed.
  • Recorded fixture: Not applicable: no fixture or model behavior changed.
  • Browser E2E: Not applicable: no browser behavior changed.
  • Backend or runtime: Not applicable: no backend/runtime behavior changed.
  • Live canary: Not applicable: no live/provider behavior changed.

What the tests prove:

  • Every registered journey and generated lifecycle claim still points to executable evidence and has zero registry gaps.
  • The documented bird's-eye-view command produces the same product-surface report used by CI.
  • Relative repository links resolve and the documented mutation harness remains fail-loud.

Commands run:

git diff --check
cd tests/e2e
.venv/bin/pytest scenarios/test_journey_coverage.py scenarios/test_state_machine_coverage.py -q
.venv/bin/python product_surface_coverage.py --json ../../artifacts/product-surface-coverage/matrix.json --markdown ../../artifacts/product-surface-coverage/matrix.md
scripts/test-mutation-audit.sh
python3 <relative Markdown link checker>
autoreview --mode local --engine codex --model gpt-5.6-sol --thinking medium

Security Impact

None. This changes engineer-facing documentation only and does not alter permissions, networking, secrets, file access, tool execution, or sandbox policy.

Reborn Trust-Boundary Checklist

  • Public policy/evidence/trust-bearing types: N/A — no types or constructors changed.
  • Untrusted content enters prompts only through an envelope/escaping primitive: N/A — no prompt path changed.
  • Hashes declare purpose; trust/binding/authenticity uses SHA-256/BLAKE3 or separate authenticity check: N/A — no hashing changed.
  • New/changed status, exit, policy, runtime, or error variants: N/A — no variants changed.
  • Security/durability serde(default) fields fail closed or have migration tests: N/A — no serialization changed.
  • Queues/maps/buffers/counters have bounds and overflow-safe arithmetic: N/A — no runtime collections changed.
  • Driver/operator-visible errors have stable class semantics: N/A — no driver/operator behavior changed.
  • Sandbox/native/host names accurately describe trust boundary: N/A — no runtime boundary changed.

Database Impact

None. No schema, migration, PostgreSQL, or libSQL behavior changed.

Blast Radius

Documentation readers selecting Reborn test evidence and interpreting CI lanes. The main risk is a stale or overstated command/guarantee; concrete paths, commands, generated reports, and accepted CI gaps were verified against the PR head.

Pending workstreams #6883, #6884, and #6889 retain ownership of guidance for files and enforcement that have not landed on main; this PR does not create broken links to their branch-only artifacts.

Rollback Plan

Revert commit e0056d5c1. No runtime or data rollback is required.

Review Follow-Through

The first structured review identified an absolute statement that contradicted the CI contract's accepted post-merge-only Windows and benchmark checks. The table now scopes the guarantee to queue-covered checks and explicitly directs engineers to the accepted-gap section. Final structured review was clean.


Review track: A (docs/tests/chore)

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@github-actions github-actions Bot added scope: docs Documentation size: XS < 10 changed lines (excluding docs) labels Jul 30, 2026
@coderabbitai

coderabbitai Bot commented Jul 30, 2026 •

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Summary by CodeRabbit

  • Documentation
    • Expanded testing guidance with mappings between local evidence and CI validation lanes.
    • Added coverage gates and regression/mutation-audit guidance for whole-path testing.
    • Documented commands for generating the product-surface coverage matrix and locating the authoritative CI artifact.

Walkthrough

Updated the testing playbook with CI lane mappings, expanded whole-path journey coverage and mutation guidance, and instructions for generating and retrieving product-surface coverage reports.

Changes

Testing playbook guidance

Layer / File(s) Summary
CI evidence and lane mapping
docs/internal/testing-playbook.md
Maps local evidence types to CI lanes and documents how to re-derive lane behavior from workflow contracts.
Journey coverage workflow
docs/internal/testing-playbook.md
Defines JourneyCase evidence metadata and documents journey, state-machine, regression, and mutation-audit workflows.
Product-surface coverage reporting
docs/internal/testing-playbook.md
Adds local matrix-generation commands and instructions for accessing the authoritative CI coverage artifact.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

Suggested reviewers: ilblackdragon

🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title uses Conventional Commits style and accurately summarizes the documentation-focused change.
Description check ✅ Passed The description matches the template and fills the required sections with concrete validation, test strategy, and impact details.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added risk: low Changes to docs, tests, or low-risk modules contributor: core 20+ merged PRs labels Jul 30, 2026
@railway-app
railway-app Bot temporarily deployed to ironclaw-ci-preview / ironclaw-pr-6928 July 30, 2026 16:56 Destroyed
@railway-app

railway-app Bot commented Jul 30, 2026 •

Copy link
Copy Markdown

🚅 Deployed to the ironclaw-pr-6928 environment in ironclaw-ci-preview

Service Status Web Updated (UTC)
ironclaw ✅ Success (View Logs) Web Jul 30, 2026 at 5:31 pm

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/internal/testing-playbook.md`:
- Around line 180-189: Update the docs validation guidance in the testing
playbook: remove the required docs/mint validation unless a valid docs/mint
project/config is added, and document the repository’s actual docs validation
command instead. Ensure the instructions specify running the command from the
correct directory and align with the authoritative workflow contract.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 9bcf143e-cb16-4086-abd1-18a8e3d972c3

📥 Commits

Reviewing files that changed from the base of the PR and between a643292 and e0056d5.

📒 Files selected for processing (1)
  • docs/internal/testing-playbook.md

Comment on lines +180 to +189
The authoritative workflow contract, required-check names, and scheduling
details live in [`.github/workflows/README.md`](../../.github/workflows/README.md).
Its "Known accepted gaps" section names deterministic and informational checks
that are deliberately not merge-gating. Re-derive the current lanes before
changing CI:

```bash
rg -n "pull_request:|merge_group:|push:|schedule:|workflow_dispatch:" \
.github/workflows
```

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

cd docs
mint dev
mint broken-links

Repository: nearai/ironclaw

Length of output: 233


🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf 'Repo files matching CLAUDE/AGENTS/rules:\n'
git ls-files | rg '(^|/)(CLAUDE\.md|AGENTS\.md|\.claude/)' || true

printf '\nRelevant guideline lines:\n'
for f in CLAUDE.md AGENTS.md .claude/rules; do
  [ -f "$f" ] && { printf '\n-- %s --\n' "$f"; rg -n "docs/\*\*|\*/testing-playbook|mint dev|mint broken-links" "$f" || true; }
done

printf '\nChanged/internal doc file reference:\n'
git diff --name-only 2>/dev/null | rg '^docs/internal/testing-playbook\.md$' || true

Repository: nearai/ironclaw

Length of output: 5407


🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf 'AGENTS.md doc guideline section:\n'
nl -ba AGENTS.md | sed -n '1,120p'

printf '\nCLAUDE.md doc guideline section:\n'
nl -ba CLAUDE.md | sed -n '1,160p'

printf '\nCitation snippets:\n'
rg -n "docs/internal/|docs/\*\*|Test documentation changes|mint dev|mint broken-links|broken-links" AGENTS.md CLAUDE.md .claude/rules -S || true

Repository: nearai/ironclaw

Length of output: 226


🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf 'AGENTS.md doc guideline section:\n'
awk '{printf "%6d\t%s\n", NR, $0}' AGENTS.md | sed -n '1,120p'

printf '\nCLAUDE.md doc guideline section:\n'
awk '{printf "%6d\t%s\n", NR, $0}' CLAUDE.md | sed -n '1,160p'

printf '\nCitation snippets:\n'
rg -n "docs/internal/|docs/\*\*|Test documentation changes|mint dev|mint broken-links|broken-links" AGENTS.md CLAUDE.md .claude/rules -S || true

Repository: nearai/ironclaw

Length of output: 19298


🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf 'AGENTS.md doc guideline lines 150-190:\n'
awk '{printf "%6d\t%s\n", NR, $0}' AGENTS.md | sed -n '150,190p'

printf '\nMint-related files:\n'
git ls-files | rg '(^|/)mint(\.lock|\.json|mintlify\.json)?$|docs/package\.json|docs/mint' || true

Repository: nearai/ironclaw

Length of output: 2714


Run the required docs/mint validation.

docs/**/* requires mint dev and mint broken-links run from docs/. The repository currently has no docs/mint project/config, so this path has failing guardrail contract. Either add the Mint setup or replace this guidance with the actual docs validation command.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/internal/testing-playbook.md` around lines 180 - 189, Update the docs
validation guidance in the testing playbook: remove the required docs/mint
validation unless a valid docs/mint project/config is added, and document the
repository’s actual docs validation command instead. Ensure the instructions
specify running the command from the correct directory and align with the
authoritative workflow contract.

Source: Coding guidelines

@ironloopai

ironloopai Bot commented Jul 30, 2026 •

Copy link
Copy Markdown
Contributor

🔎 Review · PR #6928

🟢 Completed · Review submitted

Submitted review →

Reviewed the complete trusted base-to-head comparison. The documentation additions accurately reflect the repository’s CI lanes, journey/state-machine registries, regression enforcement, mutation tooling, and product-surface report workflow. No actionable issues found.

Automatic · PR opened · attempt 1 of 3 · completed in 1m 29s

Run details
  • Repository: nearai/ironclaw
  • Base: main at 457088c
  • Head: codex/docs-epic-testing-playbook at e0056d5
  • Created: Jul 30, 2026, 5:00 PM UTC
  • Updated: Jul 30, 2026, 5:02 PM UTC
  • Run: 4e73670a-ef1a-4246-86fd-20c864d7e91b
  • Latest attempt: 1 · Completed · d0f90a7f-4a13-4ed8-969e-0ea12a540759

@ironloopai ironloopai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔍 Review complete · PR #6928

✅ No actionable findings

Reviewed the complete trusted base-to-head comparison. The documentation additions accurately reflect the repository’s CI lanes, journey/state-machine registries, regression enforcement, mutation tooling, and product-surface report workflow. No actionable issues found.

Validation and technical details
  • Inspected the full diff from refs/ironloop/base (457088c) to refs/ironloop/head (e0056d5).
  • Cross-checked CI lane claims and accepted gaps against .github/workflows/README.md and relevant workflow definitions.
  • Verified referenced journey, state-machine, regression-check, mutation-audit, and product-surface tooling exists and matches the documented interfaces.
  • Confirmed all relative Markdown links in docs/internal/testing-playbook.md resolve.
  • git diff --check completed successfully.
  • Runtime execution of the Python coverage gates was unavailable because the checkout lacks its E2E virtual environment and dependencies (pytest/httpx); static inspection confirmed the documented commands match CI and script entry points.
  • Base: main
  • Head: codex/docs-epic-testing-playbook at e0056d5
  • Run: 4e73670a-ef1a-4246-86fd-20c864d7e91b

@serrrfirat
serrrfirat merged commit 009d336 into main Jul 30, 2026
42 checks passed
@serrrfirat
serrrfirat deleted the codex/docs-epic-testing-playbook branch July 30, 2026 18:55
l3ocifer pushed a commit to l3ocifer/frick-ironclaw that referenced this pull request Sep 3, 2026

This branch was successfully deployed

No deployments
ironclaw-ci-preview / ironclaw-pr-6928 — e0056d5c Deployed Jul 30, 2026 by railway-app[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

contributor: core 20+ merged PRs risk: low Changes to docs, tests, or low-risk modules scope: docs Documentation size: XS < 10 changed lines (excluding docs)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant