Generalize defensive design with evidence-driven architecture adaptation - #3
Merged
Merged
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (20)
📝 WalkthroughWalkthroughThis change updates the Defensive Design skill and repository guidance, adds offline package validation, corrects cooperative deadline handling, expands evaluation and evidence documentation, and strengthens CI with pinned actions, artifacts, timeouts, and HTTPX compatibility checks. ChangesDefensive Design 1.2.0
Estimated code review effort: 4 (Complex) | ~45 minutes ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Recheck the event-loop clock after parsing and response cleanup. Preserve the public result contract and distinguish cooperative cancellation from CPU preemption. Add four deterministic deadline regressions; three failed before the repair and all four now pass alongside the 43 existing checks.
…utral Shorten the core and route depth to optional adapters. Preserve security and resilience invariants while correcting blanket local-lock, timeout and pure-computation rules. Add explicit action scope, evidence limits, primary sources, and an optional implementation/verification/rollback template.
…ures Preserve all 32 existing trigger cases and add 16 cases for explicit local audits, numerical correctness, local locks, long-lived streams, cooperative timeouts, offline/UI state, filesystems, devices, infrastructure, data and agents. Keep every case paired with an observable outcome rubric; structure checks do not imply that model behavior has been evaluated.
Add safe YAML, bounded local-link, resource and eval/rubric validation with 30 package regression tests. Preserve four required Python checks; add pinned baseline dependencies and separate minimum/latest HTTPX compatibility jobs. Document architecture-neutral use, maintenance, migration, rollback and unexecuted model/integration evaluation boundaries in the current work ledger.
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
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.
Summary
Upgrade the skill from 1.1.0 to 1.2.0 without prescribing a language, framework, database, deployment topology, or agent provider. Preserve existing reference paths, public HTTP result types, and the original 43 reference checks.
Baseline:
109c36dfe9a8202d93bdd64275d8936951d941d7Final head:
1fa16cfa7f461012e26a3f0c4e82f57d2e6795aeConfirmed findings and repairs
Architecture-neutral design
The shortened core discovers contracts, state ownership, authority, lifecycle, consequences, budgets and existing facilities before choosing controls. Optional adaptation guidance covers libraries, CLIs/filesystems, UI/mobile/offline applications, monoliths, distributed services, streams/batches, infrastructure, embedded systems, ML pipelines and agents.
Review, design, implementation and incident modes have explicit action boundaries. Preserve fail-closed security, distinguish domain-approved physical safe states, keep long-lived work resource-bounded, and require evidence-backed findings and proportional implementation slices. Add an optional assessment template, primary-source map, maintenance guidance, changelog, migration/rollback instructions and current work ledger.
Reviewable commits
8a833541d27af1ecb90dcde1d2dd1fa16cfVerification
Final-head hosted run 33936915044: successful. All six jobs passed: Python 3.11, 3.12, 3.13 and 3.14 reference/package checks, plus HTTPX 0.27.0 and bounded latest-0.x compatibility checks. The four protected-branch check names remain unchanged.
Local final-state verification used Python 3.13.5, HTTPX 0.28.1 and PyYAML 6.0.3:
python scripts/validate_skill.pypython scripts/verify_reference.pypython -m unittest discover -s tests -vpython -O -m unittest discover -s tests -p test_validate_skill.py -vpython -m compileall -q scripts references testsgit diff --checkAll 25 published package files match the locally tested files by Git blob identity. The evaluation corpus has 48 cases, with 40 positive and eight negative triggers and matching behavioral rubrics. Corpus validation is not evidence of successful model runs.
Compatibility, migration and rollback
The text skill has no runtime dependency. Python dependencies apply only to maintainer checks and the optional HTTP example. Install the complete package so new on-demand references remain available. No application schema, infrastructure or durable-data migration is introduced.
Revert the relevant commits or restore the previously reviewed package revision. Keep the deadline repair when rolling back only instructional changes rather than reintroducing the known bug.
Verification limits and publication state
Independent host/model behavioral evaluation was not executed. Ruff and mypy were unavailable locally; no current lint/type-check pass is claimed. Mock-transport/unit tests do not establish real DNS, TLS, proxy, provider, hardware or physical-safety behavior. Generalized guidance is not a guarantee of robustness on every codebase.
Changes are pushed to
improve/universal-defensive-design. Main protection remains unchanged. This PR is not merged; no deployment, release tag or host-wide installation was performed.Summary by CodeRabbit
New Features
Bug Fixes
Documentation
Tests