Open
Conversation
Co-authored-by: toolate28 <105518313+toolate28@users.noreply.github.com>
Co-authored-by: toolate28 <105518313+toolate28@users.noreply.github.com>
Co-authored-by: toolate28 <105518313+toolate28@users.noreply.github.com>
Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com> Signed-off-by: toolated <toolated@toolated.online>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: toolated <toolated@toolated.online>
…paths, input validation Co-authored-by: toolate28 <105518313+toolate28@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: toolated <toolated@toolated.online>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: toolated <toolated@toolated.online>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: toolated <toolated@toolated.online>
…on, path traversal protection Co-authored-by: toolate28 <105518313+toolate28@users.noreply.github.com>
Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com> Signed-off-by: toolated <toolated@toolated.online>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: toolated <toolated@toolated.online>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: toolated <toolated@toolated.online>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request introduces a comprehensive AWI (Authorization-With-Intent) prompt generation toolkit inspired by DSPy patterns, along with validation improvements and documentation updates. The changes implement a production-ready prompt optimization system for AI-human collaboration with security hardening and extensive test coverage.
Changes:
- Added a DSPy-inspired prompt generation module (
experiments/awi_prompt_gen.py) implementing ChainOfThought scaffolding, Predict refinement, COPRO optimization, and SIMBA annealing techniques - Created comprehensive unit tests for the prompt generation module covering integration, edge cases, security (YAML injection prevention), and permission inference
- Enhanced input validation in the
spiralsafeAWI request function to prevent leading-zero integers and ensure non-negative values - Documented the prompt toolkit architecture, optimization techniques, and usage examples in
interface/awi-spec.md - Added optional DSPy dependency to
requirements-ml.txt(commented out) - Cleaned up obsolete quantum cognition session data and updated
.gitignoreto exclude generated output files
Reviewed changes
Copilot reviewed 6 out of 7 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
experiments/awi_prompt_gen.py |
New 715-line module implementing DSPy-style prompt generation with security features (YAML sanitization, path validation), COPRO/SIMBA optimization, and AWI protocol integration |
experiments/test_awi_prompt_gen.py |
Comprehensive test suite covering scaffolder-refiner integration, metadata propagation, edge cases, YAML injection prevention, and permission inference |
interface/awi-spec.md |
Added documentation section for prompt toolkit with architecture diagram, component descriptions, optimization techniques, and usage examples |
ops/scripts/spiralsafe |
Enhanced awi_request function validation to reject leading-zero integers and ensure non-negative level/TTL values |
requirements-ml.txt |
Added commented optional dependency for dspy-ai==2.4.0 with clear usage instructions |
media/output/quantum_cognition/session_history.json |
Removed 306 lines of obsolete session history data |
.gitignore |
Added pattern to exclude media/output/ directory for generated files |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: toolated <toolated@toolated.online>
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: toolated <toolated@toolated.online>
10 tasks
Contributor
|
@toolate28 I've opened a new pull request, #168, to work on those changes. Once the pull request is ready, I'll request review from you. |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: toolated <toolated@toolated.online>
Contributor
|
@toolate28 I've opened a new pull request, #169, to work on those changes. Once the pull request is ready, I'll request review from you. |
10 tasks
Co-authored-by: toolate28 <105518313+toolate28@users.noreply.github.com>
Co-authored-by: toolate28 <105518313+toolate28@users.noreply.github.com>
Co-authored-by: toolate28 <105518313+toolate28@users.noreply.github.com>
…sertion Co-authored-by: toolate28 <105518313+toolate28@users.noreply.github.com>
…ot/sub-pr-156 Signed-off-by: toolated <toolated@pm.me>
…ot/sub-pr-156-again Signed-off-by: toolated <toolated@pm.me>
…#169) ## Summary Refactored `test_awi_prompt_gen.py` from custom test runner to standard pytest conventions, removing incompatible patterns that prevented pytest discovery and execution. ## ATOM Tag **ATOM:** `ATOM-REFACTOR-20260119-001-pytest-compatible-tests` ## Why The test class used custom `__init__`, `run_all()`, and `test()` methods that pytest cannot recognize. Pytest expects standard test classes without custom `__init__` and standard `assert` statements instead of custom assertion methods. ## What changed **Before:** ```python class TestAwiPromptGen: def __init__(self): self.passed = 0 self.failed = 0 def test(self, name: str, condition: bool, error_msg: str = ""): if condition: print(f" ✅ PASS: {name}") self.passed += 1 else: print(f" ❌ FAIL: {name}") self.failed += 1 def run_all(self): # Custom test orchestration ``` **After:** ```python class TestAwiPromptGen: def test_scaffolder_refiner_integration(self): gen = AwiPromptGen() result = gen(user_intent="...", history=[...]) assert isinstance(result, Prediction), f"Expected Prediction, got {type(result)}" assert len(result.content) > 0, "Content should not be empty" ``` ### Changes - Removed custom test infrastructure (`__init__`, `run_all()`, `test()` method) - Converted all 7 test methods to use standard `assert` statements - Added `if __name__ == "__main__"` block for standalone execution via pytest - Cleaned up line continuations to follow PEP 8 - Moved pytest import to module level for clarity ## Verification / Testing - [x] All 7 tests pass with `pytest experiments/test_awi_prompt_gen.py -v` - [x] Standalone execution works: `python experiments/test_awi_prompt_gen.py` - [x] Tests discovered and executed by pytest's test discovery - [x] Code review feedback addressed ## Claude Interaction You can interact with Claude in this PR by: - **@mentioning Claude** in comments for questions or reviews - **Adding labels**: `claude:review`, `claude:help`, `claude:analyze` - **Requesting reviews**: Claude will provide automated feedback - **Ask questions**: Claude can explain code, suggest improvements, or identify issues ### Example commands: - `@claude please review this PR for ATOM compliance` - `@claude explain the changes in scripts/atom-track.sh` - `@claude check for security issues` - `@claude suggest improvements` ## Notes - Tests remain organized in `TestAwiPromptGen` class for structure - All original test logic preserved, only execution mechanism changed - Compatible with existing pytest configuration in `requirements-dev.txt` ## Checklist - [x] ATOM tag created and referenced - [x] Tests passing - [x] Documentation updated (inline comments clarifying assertions) - [x] No secrets committed - [x] Follows existing patterns (matches other test files in repo) - [x] Ready for Claude review <!-- START COPILOT CODING AGENT TIPS --> --- 💬 We'd love your input! Share your thoughts on Copilot coding agent in our [2 minute survey](https://gh.io/copilot-coding-agent-survey).
…ot/sub-pr-156 Signed-off-by: toolated <toolated@pm.me>
## Summary
The `TestAwiPromptGen` class was not discoverable by pytest because it
lacked `unittest.TestCase` inheritance and used a custom test runner
instead of pytest conventions.
## ATOM Tag
**ATOM:** `ATOM-REFACTOR-20260119-001-pytest-test-discovery`
## Why
Pytest test discovery requires either:
1. Test classes inheriting from `unittest.TestCase`, or
2. Standalone `test_*` functions
The custom class with `run_all()` method bypassed pytest's discovery
mechanism, making tests invisible to CI and manual `pytest` runs.
## What changed
- Converted class-based tests to 7 standalone `test_*` functions
- Replaced custom `self.test()` assertions with standard `assert`
statements
- Removed test runner infrastructure (`__init__`, `run_all()`, pass/fail
counters)
- Reduced file from 299 to 161 lines while preserving all test logic
**Before:**
```python
class TestAwiPromptGen:
def test(self, name: str, condition: bool, error_msg: str = ""):
if condition:
print(f" ✅ PASS: {name}")
self.passed += 1
else:
print(f" ❌ FAIL: {name}")
self.failed += 1
def test_scaffolder_refiner_integration(self):
gen = AwiPromptGen()
result = gen(user_intent="...", history=[...])
self.test("Result is Prediction", isinstance(result, Prediction))
```
**After:**
```python
def test_scaffolder_refiner_integration():
"""Test that scaffolder and refiner work together correctly."""
gen = AwiPromptGen()
result = gen(user_intent="...", history=[...])
assert isinstance(result, Prediction), f"Expected Prediction, got {type(result)}"
```
## Verification / Testing
- [x] All 7 tests discovered by `pytest --collect-only`
- [x] All 7 tests pass with `pytest -v`
- [x] Follows pattern in `ops/integrations/*/tests/test_*.py`
- [x] ATOM tag created and logged
## Claude Interaction
You can interact with Claude in this PR by:
- **@mentioning Claude** in comments for questions or reviews
- **Adding labels**: `claude:review`, `claude:help`, `claude:analyze`
- **Requesting reviews**: Claude will provide automated feedback
- **Ask questions**: Claude can explain code, suggest improvements, or
identify issues
### Example commands:
- `@claude please review this PR for ATOM compliance`
- `@claude explain the changes in scripts/atom-track.sh`
- `@claude check for security issues`
- `@claude suggest improvements`
## Notes
- Addresses feedback from PR #156:
#156 (comment)
- Maintains identical test coverage and assertions
- No behavior changes, pure refactoring for pytest compatibility
## Checklist
- [x] ATOM tag created and referenced
- [x] Tests passing
- [ ] Documentation updated (test file is self-documenting)
- [x] No secrets committed
- [x] Follows existing patterns
- [x] Ready for Claude review
<!-- START COPILOT CODING AGENT TIPS -->
---
💡 You can make Copilot smarter by setting up custom instructions,
customizing its development environment and configuring Model Context
Protocol (MCP) servers. Learn more [Copilot coding agent
tips](https://gh.io/copilot-coding-agent-tips) in the docs.
toolate28
changed the title
| @@ -0,0 +1,163 @@ | |||
| #!/usr/bin/env python3 | |||
There was a problem hiding this comment.
The PR title doesn't follow the expected ATOM tag format. According to the custom coding guidelines, ATOM tags should follow the pattern ATOM-TYPE-YYYYMMDD-NNN-description where:
- TYPE should be one of: INIT, FEATURE, FIX, DOC, REFACTOR, TEST, DECISION, RELEASE, TASK
- YYYYMMDD is the date
- NNN is a three-digit sequence number
The current title "ATOM-TYPE-20260120-AWI-DSpy-Toolkit" is missing:
- A specific type (it literally says "TYPE" instead of FEATURE, TEST, etc.)
- A three-digit sequence number before the description
Expected format would be something like: "ATOM-FEATURE-20260120-001-awi-dspy-toolkit" or "ATOM-TEST-20260120-001-awi-dspy-toolkit"
| - AWI protocol: Permission scaffolding integration | ||
| - ATOM system: Session tracking and verification | ||
|
|
||
| ATOM-FEATURE-20260117-001-awi-prompt-gen |
There was a problem hiding this comment.
There's a date discrepancy between the PR title and the ATOM tags in the code files. The PR title uses "20260120" (January 20, 2026) while the ATOM tags in both test_awi_prompt_gen.py (line 10) and awi_prompt_gen.py (line 44) use "20260117" (January 17, 2026). These dates should be consistent to maintain proper ATOM trail tracking.
Comment on lines
+161
to
+163
| for ex in examples.get("negative", []): | ||
| assert ex.coherence_score < COHERENCE_HIGH_THRESHOLD, \ | ||
| f"Negative example should have low coherence: expected < {COHERENCE_HIGH_THRESHOLD}, got {ex.coherence_score}" |
There was a problem hiding this comment.
In the test_coherence_examples function, the negative examples loop checks that coherence_score is below the threshold, but it doesn't verify that is_positive is False (unlike the positive examples which check both properties). For consistency and completeness, negative examples should also verify that is_positive is False.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: toolated <toolated@toolated.online>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: toolated <toolated@toolated.online>
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.
This pull request introduces a comprehensive prompt generation toolkit for AWI, inspired by DSPy, and adds robust testing, documentation, and validation improvements. The main focus is on integrating a modular prompt generation pipeline, enhancing security and correctness in scripts, and providing thorough unit tests for edge cases and optimizations.
Prompt Generation Toolkit Integration:
interface/awi-spec.mddocumenting the AWI prompt toolkit, including its architecture, components (ChainOfThought,Predict,AwiPromptGen), optimization techniques (COPRO, SIMBA), and usage examples. Reference to the implementation inexperiments/awi_prompt_gen.pyis also provided.requirements-ml.txtto mention the optionaldspy-aidependency for prompt optimization, clarifying its use for the new AWI prompt toolkit.Testing and Quality Assurance:
experiments/test_awi_prompt_gen.pycovering:Security and Validation Enhancements:
awi_requestfunction withinops/scripts/spiralsafeby ensuringlevelandttlare non-negative integers, preventing malformed requests and potential script errors.Maintenance and Cleanup:
media/output/quantum_cognition/session_history.json, likely as part of a cleanup or data refresh.This pull request introduces a comprehensive suite of improvements focused on prompt generation for AI-human collaboration, validation enhancements, and documentation updates. The most significant changes are the addition of a unit test module for the AWI prompt generation system, new documentation for the prompt toolkit architecture and usage, stricter input validation in thespiralsafescript, and optional support for DSPy-style prompt optimization.Prompt Generation Toolkit and Testing
AwiPromptGenmodule inexperiments/test_awi_prompt_gen.py, covering integration, metadata propagation, edge case handling, YAML injection prevention, permission inference, and coherence example validation.interface/awi-spec.md, including the DSPy-inspired pipeline, optimization techniques (COPRO, SIMBA), and a reference implementation.requirements-ml.txtto optionally support DSPy-style prompt optimization by adding a commented-out dependency fordspy-ai.Validation Improvements
awi_requestfunction ofops/scripts/spiralsafeto ensurelevelandttlare non-negative integers without leading zeros (except for 0).Data Cleanup
media/output/quantum_cognition/session_history.jsonto keep the repository clean and relevant.name: Pull request templateabout: Use this template for PRs that add CI, bump templates, or agent-facing files
title: ''
labels: ''
assignees: ''
Summary
Describe the change in 1-2 sentences.
ATOM Tag
ATOM:
ATOM-TYPE-YYYYMMDD-NNN-description(Generate with:
./scripts/atom-track.sh TYPE "description" "file")Why
Why this change is needed and what it enables.
What changed
Verification / Testing
scripts/validate-bump.shpasses locally (if bump.md changed)scripts/validate-branch-name.shtested on example branches (if applicable)bash scripts/verify-environment.shprintsENV OKscripts/test-scripts.shpasses (if scripts changed)Claude Interaction
You can interact with Claude in this PR by:
claude:review,claude:help,claude:analyzeExample commands:
@claude please review this PR for ATOM compliance@claude explain the changes in scripts/atom-track.sh@claude check for security issues@claude suggest improvementsNotes