Skip to content

docs(analysis): Factory-AI/droid-action security constraint blocker#960

Merged
rjmurillo merged 3 commits into
mainfrom
docs/session-9-droid-action-analysis
Jan 18, 2026
Merged

docs(analysis): Factory-AI/droid-action security constraint blocker#960
rjmurillo merged 3 commits into
mainfrom
docs/session-9-droid-action-analysis

Conversation

@rjmurillo-bot

Copy link
Copy Markdown
Collaborator

Summary

Root cause analysis of Droid Auto Review workflow failure. Factory-AI/droid-action internally uses non-SHA-pinned actions (actions/upload-artifact@v4), violating repository security constraints.

Key Findings

  • Latest droid-action version (e3f8be9f, 2026-01-12) contains non-pinned action references
  • Repository security rules apply recursively to all nested action dependencies
  • No workaround available without modifying third-party action or relaxing security constraints

Impact

BLOCKING: droid-review.yml and droid.yml workflows fail at setup phase on branches with security constraints.

Recommendations

  1. File issue with Factory-AI requesting SHA-pinned action references
  2. Evaluate alternative PR review automation tools (GitHub Copilot, Reviewable.io)
  3. Document as known limitation in operational runbook or ADR

Deliverables

  • Session log: .agents/sessions/2026-01-16-session-9-droid-action-blocker.json
  • Memory: .serena/memories/ci-infrastructure-droid-action-blocker.md

Related

  • Memory: ci-infrastructure-codeql-ruleset-friction
  • Memory: security-practices
  • Repository ruleset: "Require actions to be pinned to full-length commit SHA"

🤖 Generated with Claude Code

…blocker

Root cause analysis of Droid Auto Review workflow failure. The Factory-AI/droid-action
internally uses actions/upload-artifact@v4 (non-SHA-pinned), which violates repository
security constraints requiring all actions to be pinned to full-length commit SHAs.

Key findings:
- Latest droid-action version (e3f8be9f, 2026-01-12) still contains non-pinned references
- Repository security rules apply recursively to all nested action dependencies
- No workaround available without modifying third-party action or relaxing security constraints

Impact: BLOCKING - droid-review.yml and droid.yml workflows fail at setup phase

Recommendations:
- File issue with Factory-AI requesting SHA-pinned action references
- Evaluate alternative PR review automation tools
- Document as known limitation in operational runbook

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

@github-actions

Copy link
Copy Markdown
Contributor

PR Validation Report

Tip

Status: PASS

Description Validation

Check Status
Description matches diff PASS

QA Validation

Check Status
Code changes detected False
QA report exists N/A

Powered by PR Validation workflow

@github-actions

Copy link
Copy Markdown
Contributor

Session Protocol Compliance Report

Tip

Overall Verdict: PASS

All session protocol requirements satisfied.

What is Session Protocol?

Session logs document agent work sessions and must comply with RFC 2119 requirements:

  • MUST: Required for compliance (blocking failures)
  • SHOULD: Recommended practices (warnings)
  • MAY: Optional enhancements

See .agents/SESSION-PROTOCOL.md for full specification.

Compliance Summary

Session File Verdict MUST Failures
sessions-2026-01-16-session-9-droid-action-blocker.md ✅ COMPLIANT 0

Detailed Validation Results

Click each session to see the complete validation report with specific requirement failures.

📄 sessions-2026-01-16-session-9-droid-action-blocker

✨ Zero-Token Validation

This validation uses deterministic PowerShell script analysis instead of AI:

  • Zero tokens consumed (previously 300K-900K per debug cycle)
  • Instant feedback - see exact failures in this summary
  • No artifact downloads needed to diagnose issues
  • 10x-100x faster debugging

Powered by Validate-SessionJson.ps1

📊 Run Details
Property Value
Run ID 21082071284
Files Checked 1
Validation Method Deterministic script analysis

Powered by Session Protocol Validator workflow

@github-actions

github-actions Bot commented Jan 16, 2026

Copy link
Copy Markdown
Contributor

AI Quality Gate Review

Tip

Final Verdict: PASS

Walkthrough

This PR was reviewed by six AI agents in parallel, analyzing different aspects of the changes:

  • Security Agent: Scans for vulnerabilities, secrets exposure, and security anti-patterns
  • QA Agent: Evaluates test coverage, error handling, and code quality
  • Analyst Agent: Assesses code quality, impact analysis, and maintainability
  • Architect Agent: Reviews design patterns, system boundaries, and architectural concerns
  • DevOps Agent: Evaluates CI/CD, build pipelines, and infrastructure changes
  • Roadmap Agent: Assesses strategic alignment, feature scope, and user value

Review Summary

Agent Verdict Category Status
Security PASS N/A
QA PASS N/A
Analyst PASS N/A
Architect PASS N/A
DevOps PASS N/A
Roadmap PASS N/A

💡 Quick Access: Click on individual agent jobs (e.g., "🔒 security Review", "🧪 qa Review") in the workflow run to see detailed findings and step summaries.

Security Review Details

Security Review: PR #960

PR Type Classification

File Category Scrutiny Level
.agents/sessions/2026-01-16-session-9-droid-action-blocker.json DOCS None required
.serena/memories/ci-infrastructure-droid-action-blocker.md DOCS None required

Classification: DOCS-only PR (session log + memory documentation)

Findings

Severity Category Finding Location CWE
None - No security issues identified - -

Analysis Summary

  • Secret Detection: No hardcoded credentials, API keys, or tokens. All URLs reference public GitHub resources.
  • Sensitive Data: No internal endpoints, passwords, or confidential information exposed.
  • Content Review: Documentation describes a supply chain security constraint (SHA-pinning requirement) and why a third-party action violates it. This is security-positive content advocating for stronger security practices.

Recommendations

None. This PR documents security best practices regarding action pinning and supply chain security.

Verdict

VERDICT: PASS
MESSAGE: Documentation-only PR analyzing supply chain security constraints. No sensitive data exposed. Content reinforces security posture.
QA Review Details

Based on my analysis, I can now provide the QA verdict.


QA Review: PR #960

VERDICT: PASS
MESSAGE: Documentation-only PR adds session log and memory file with no executable code.

PR TYPE: DOCS
FILES:
- DOCS: .agents/sessions/2026-01-16-session-9-droid-action-blocker.json (session log)
- DOCS: .serena/memories/ci-infrastructure-droid-action-blocker.md (memory/analysis)

Evidence

File Classification

File Category Rationale
.agents/sessions/2026-01-16-session-9-droid-action-blocker.json DOCS Session log artifact (JSON data, no executable code)
.serena/memories/ci-infrastructure-droid-action-blocker.md DOCS Memory/knowledge base document (Markdown)

Tests Required: N/A

Per QA guidelines: "Files without executable logic do not require tests."

Both files are:

  1. Session log (JSON): Documents investigation process and findings
  2. Memory file (MD): Root cause analysis documentation

Neither contains executable code (no .ps1, .psm1, .cs, .ts, .js, .py files).

Documentation Quality Check

Check Status Evidence
JSON syntax valid [PASS] Well-formed JSON with proper schema
Markdown syntax valid [PASS] Standard markdown formatting
Broken links [PASS] Internal references use relative paths
Content accuracy [PASS] Technical analysis is consistent and evidence-based

Blocking Issues: 0

No BLOCKING or HIGH severity issues identified. This PR documents a legitimate investigation into a third-party action security constraint violation with clear evidence and actionable recommendations.

Analyst Review Details

Now let me examine an existing session log and memory file to understand the expected format and patterns.

Let me check the existing session log schema and a related memory file to compare patterns.

Now I have sufficient context to provide the analysis. This is a documentation-only PR adding a session log and a memory file documenting a security constraint blocker.

PR #960 Analysis

Code Quality Score

Criterion Score (1-5) Notes
Readability 5 Clear structure, well-organized sections, consistent formatting
Maintainability 5 Self-contained documentation with external links for context
Consistency 5 Follows existing patterns in .agents/sessions/ and .serena/memories/
Simplicity 5 Focused on single topic, no unnecessary complexity

Overall: 5/5

Impact Assessment

  • Scope: Isolated (documentation only)
  • Risk Level: Low
  • Affected Components: None (read-only documentation artifacts)

Findings

Priority Category Finding Location
Low Style Emoji checkmarks in memory file may violate style guide (no emojis rule) .serena/memories/...:78,85,102
Low Style Emoji in session log nextSteps session log:175
Info Quality Comprehensive root cause analysis with clear evidence chain Both files
Info Quality Upstream issue filed and tracked (Factory-AI/droid-action#20) Both files

Recommendations

  1. Replace emoji checkmarks () and crosses () with text status indicators ([PASS], [FAIL], [DONE]) to align with style guide.
  2. The memory file duplicates some content from the session log; consider cross-referencing instead of duplication.

Verdict

VERDICT: PASS
MESSAGE: High-quality analysis documentation following established patterns. Minor emoji usage inconsistency with style guide does not block merge.
Architect Review Details

Design Quality Assessment

Aspect Rating (1-5) Notes
Pattern Adherence 5 Follows established session log schema and memory format
Boundary Respect 5 Files placed in correct directories (.agents/sessions/, .serena/memories/)
Coupling N/A Documentation-only change, no code coupling
Cohesion 5 Single-purpose investigation documentation
Extensibility N/A Documentation-only change

Overall Design Score: 5/5

Architectural Concerns

Severity Concern Location Recommendation
None - - -

No architectural concerns. This PR documents an investigation finding about third-party action incompatibility with repository security constraints.

Breaking Change Assessment

  • Breaking Changes: No
  • Impact Scope: None
  • Migration Required: No

Technical Debt Analysis

  • Debt Added: None
  • Debt Reduced: Low (documents known limitation, prevents future investigation duplication)
  • Net Impact: Improved

ADR Assessment

  • ADR Required: No
  • Decisions Identified: The decision to require SHA-pinned actions is already established policy, not a new decision made in this PR
  • Existing ADR: Security constraints documented in security-practices memory; no ADR needed for documenting external tool incompatibility
  • Recommendation: N/A - This PR documents a blocker discovery, not an architectural decision

The PR correctly identifies that an ADR or operational runbook update may be needed as a follow-up action, but the investigation itself does not introduce an architectural decision requiring an ADR.

Recommendations

  1. None - documentation is well-structured and follows repository conventions

Verdict

VERDICT: PASS
MESSAGE: Documentation-only PR following established session log and memory patterns. No architectural decisions introduced. Correctly documents third-party action limitation for team awareness.
DevOps Review Details

PR #960 DevOps Review

PR Scope Detection

Changed File Category Review Scope
.agents/sessions/2026-01-16-session-9-droid-action-blocker.json DOCS (session log) None required
.serena/memories/ci-infrastructure-droid-action-blocker.md DOCS (memory) None required

Classification: DOCS-only PR (analysis documentation and session log)

Pipeline Impact Assessment

Area Impact Notes
Build None No build configuration changes
Test None No test configuration changes
Deploy None No deployment changes
Cost None Documentation only

CI/CD Quality Checks

Not applicable. This PR contains:

  • 1 session log (JSON) documenting investigation of droid-action blocker
  • 1 memory file (MD) with root cause analysis

No workflow files, scripts, or CI configuration changed.

Findings

Severity Category Finding Location Fix
Info Documentation Well-structured RCA with evidence Both files None needed

Observations

The PR documents a legitimate infrastructure blocker:

Recommendations

None. This is analysis documentation with actionable next steps already identified.

VERDICT: PASS
MESSAGE: DOCS-only PR containing investigation analysis. No CI/CD changes to review.
Roadmap Review Details

Strategic Alignment Assessment

Criterion Rating Notes
Aligns with project goals High Documents security constraint friction affecting CI infrastructure. Security hardening is a P1 concern per roadmap.
Priority appropriate High Investigation-only work documenting a BLOCKING constraint. Low effort, high knowledge value.
User value clear Medium Value is indirect: prevents wasted effort on incompatible tooling. No direct user-facing feature.
Investment justified High Session log + memory is minimal investment for permanent organizational knowledge.

Feature Completeness

  • Scope Assessment: Right-sized
  • Ship Ready: Yes
  • MVP Complete: Yes
  • Enhancement Opportunities: None. This is documentation of external constraint, not a feature.

Impact Analysis

Dimension Assessment Notes
User Value Medium Prevents future debugging of same issue. Saves 2-4 hours per occurrence.
Business Impact Low No direct business impact. Operational efficiency improvement.
Technical Leverage Medium Memory enables future tool evaluations. Pattern of transitive dependency audit is reusable.
Competitive Position Neutral Security posture maintained. No feature regression.

Concerns

Priority Concern Recommendation
Low Upstream issue may take months to resolve Continue evaluating alternatives in parallel.
Low No quantified reach/impact in analysis Acceptable for investigation-only deliverable.

Recommendations

  1. Merge as-is. The analysis correctly identifies a third-party dependency constraint and documents the decision not to relax security rules.
  2. Consider adding this to Pre-PR Security Gate evaluation criteria: audit transitive action dependencies before adding new GitHub Actions.
  3. Track upstream issue (Request: Use SHA-pinned action references for security-constrained repositories Factory-AI/droid-action#20) in a follow-up work item.

Verdict

VERDICT: PASS
MESSAGE: Investigation-only PR documenting external blocker. Minimal investment, permanent knowledge captured. Aligns with security-first strategy.

Run Details
Property Value
Run ID 21106671198
Triggered by pull_request on 960/merge
Commit 9654af8148359bbc24ac965bb695faf283d8ee09

Powered by AI Quality Gate workflow

@rjmurillo

Copy link
Copy Markdown
Owner

Review Triage Required

Note

Priority: NORMAL - Human approval required before bot responds

Review Summary

Source Reviews Comments
Human 0 0
Bot 0 0

Next Steps

  1. Review human feedback above
  2. Address any CHANGES_REQUESTED from human reviewers
  3. Add triage:approved label when ready for bot to respond to review comments

Powered by PR Maintenance workflow - Add triage:approved label

@rjmurillo

Copy link
Copy Markdown
Owner

@rjmurillo-bot is there an issue tracking this upstream with factory droid?

rjmurillo
rjmurillo previously approved these changes Jan 18, 2026
@rjmurillo-bot

Copy link
Copy Markdown
Collaborator Author

Factory-AI Droid-Action: Detailed Context

What Is It?

Factory-AI droid-action is a GitHub Action for automated AI-powered PR review. It runs Factory's Droid Exec in headless mode within GitHub Actions CI/CD pipelines to:

  • Analyze pull request code changes
  • Identify issues automatically
  • Post feedback as inline comments
  • Submit review feedback via GitHub CLI

Repository Workflows Using It

This repository has two workflows using Factory-AI droid-action:

  1. .github/workflows/droid-review.yml - Auto-review on PR open

    • Triggers: opened, ready_for_review, reopened
    • Uses: Factory-AI/droid-action@e3f8be9f34bb41b11e852e836cb64e81f13fba59 (v1)
  2. .github/workflows/droid.yml - Manual @droid invocation

    • Triggers: Issue/PR comments containing @droid
    • Uses: Same SHA-pinned version

BLOCKING Issue: Security Constraint Violation

Status: ❌ BLOCKED

The repository has a security ruleset requiring all actions to be pinned to full-length commit SHA. Factory-AI/droid-action internally uses non-SHA-pinned references:

# Inside Factory-AI/droid-action's action.yml
- uses: actions/upload-artifact@v4  # NOT SHA-pinned

Error message from workflow runs:

The action actions/upload-artifact@v4 is not allowed in rjmurillo/ai-agents 
because all actions must be pinned to a full-length commit SHA.

Investigation Findings (from session 9)

Version SHA Status
v1 tag 65dab2847e1b4a8a24332cfdef116e4ac3777789 ❌ Non-pinned refs
Latest commit e3f8be9f34bb41b11e852e836cb64e81f13fba59 ❌ Non-pinned refs

Conclusion: No compatible version exists that satisfies the security constraint.

Why This Matters (Security Context)

Repository security rules apply recursively to all nested action dependencies:

  • Actions referenced directly in workflow files
  • Actions referenced by composite actions
  • Actions referenced by Docker container actions

This ensures SLSA Level 2+ compliance and prevents supply chain attacks via tag manipulation.

Recommended Actions

Short-term:

  1. Keep workflows disabled on branches with security constraints
  2. File issue with Factory-AI requesting SHA-pinned action references
  3. Document limitation in ADR or operational runbook

Long-term alternatives:

  1. GitHub Copilot (native GitHub integration)
  2. Reviewable.io (external service)
  3. Custom review workflow using SHA-pinned actions
  4. ai-action/pull-request-review

Related Memory

The full root cause analysis is stored in Serena memory: ci-infrastructure-droid-action-blocker


Sources:

@rjmurillo-bot

rjmurillo-bot commented Jan 18, 2026

Copy link
Copy Markdown
Collaborator Author

@rjmurillo-bot is there an issue tracking this upstream with factory droid?

✅ Upstream issue now filed: Factory-AI/droid-action#20


Issue Details

Title: Request: Use SHA-pinned action references for security-constrained repositories

Summary: Repositories with security rulesets requiring "all actions must be pinned to full-length commit SHA" cannot use Factory-AI/droid-action because it internally references actions/upload-artifact@v4 instead of a SHA-pinned reference.

Requested Change:

# Before
- uses: actions/upload-artifact@v4

# After  
- uses: actions/upload-artifact@6f51ac03b9356f520e9adb1b1b7802705f340c2b # v4.5.0

Justification:

  • SLSA Level 2+ compliance
  • Supply chain security
  • Enterprise adoption requirements
  • GitHub security hardening guidance

Monitoring for response from Factory-AI maintainers.

- Added workLog entries for PR #960 comment activities
- Documented upstream issue research (no issue exists)
- Added PR comments as deliverables
- Added learning pattern about upstream issue verification

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Updated memory with upstream issue link and status
- Marked "file upstream issue" as DONE in recommendations
- Updated session log with issue filing activity
- Added next step to monitor for maintainer response

Upstream: Factory-AI/droid-action#20

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@rjmurillo rjmurillo merged commit fcfd184 into main Jan 18, 2026
43 checks passed
@rjmurillo rjmurillo deleted the docs/session-9-droid-action-analysis branch January 18, 2026 05:28
@github-actions github-actions Bot added this to the 0.2.0 milestone Jan 18, 2026
rjmurillo-bot added a commit that referenced this pull request Jan 19, 2026
…960)

* docs(analysis): document Factory-AI/droid-action security constraint blocker

Root cause analysis of Droid Auto Review workflow failure. The Factory-AI/droid-action
internally uses actions/upload-artifact@v4 (non-SHA-pinned), which violates repository
security constraints requiring all actions to be pinned to full-length commit SHAs.

Key findings:
- Latest droid-action version (e3f8be9f, 2026-01-12) still contains non-pinned references
- Repository security rules apply recursively to all nested action dependencies
- No workaround available without modifying third-party action or relaxing security constraints

Impact: BLOCKING - droid-review.yml and droid.yml workflows fail at setup phase

Recommendations:
- File issue with Factory-AI requesting SHA-pinned action references
- Evaluate alternative PR review automation tools
- Document as known limitation in operational runbook

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

* docs(session): update session-9 with PR comment responses

- Added workLog entries for PR #960 comment activities
- Documented upstream issue research (no issue exists)
- Added PR comments as deliverables
- Added learning pattern about upstream issue verification

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* docs: record upstream issue Factory-AI/droid-action#20

- Updated memory with upstream issue link and status
- Marked "file upstream issue" as DONE in recommendations
- Updated session log with issue filing activity
- Added next step to monitor for maintainer response

Upstream: Factory-AI/droid-action#20

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

---------

Co-authored-by: rjmurillo-bot <rjmurillo-bot@users.noreply.github.com>
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
Co-authored-by: Richard Murillo <richard.murillo@example.com>
rjmurillo added a commit that referenced this pull request Jan 19, 2026
* docs!: add ADR-042 Python migration strategy (supersedes ADR-005)

Migrate ai-agents from PowerShell to Python as primary scripting
language over a 12-24 month phased migration period.

## Decision Summary

- Python 3.10+ established as project language standard
- ADR-005 superseded for new development
- Phased approach: Foundation -> New Development -> Migration
- Python already prerequisite via skill-installer (PR #962)

## Rationale

- 70-second PowerShell tool startup times per invocation
- No CodeQL support for PowerShell (deterministic security unavailable)
- AI/ML ecosystem (Anthropic SDK, MCP) is Python-native
- skill-installer already requires Python 3.10+ and UV

## 6-Agent ADR Review Debate

| Agent | Verdict |
|-------|---------|
| Analyst | CONCERNS |
| Architect | CONCERNS |
| Critic | CONCERNS |
| Independent-Thinker | CONCERNS |
| Security | CONCERNS |
| High-Level-Advisor | ACCEPT |

Result: Disagree-and-Commit (5 CONCERNS + 1 ACCEPT)
Tie-breaker: High-Level-Advisor

## P0 Issues Resolved

- Stack Overflow claim corrected (Python growth, not #1)
- Path Dependence language fixed ("Python-first with phased migration")

## P1 Issues Deferred to Phase 1 Implementation

- pyproject.toml creation
- pytest infrastructure setup
- PROJECT-CONSTRAINTS.md update
- Supply chain controls (uv.lock, Dependabot, pip-audit)

BREAKING CHANGE: ADR-005 PowerShell-only standard superseded.
New scripts SHOULD be Python. Existing scripts migrate incrementally.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* docs(planning): add ADR-042 Python migration implementation plan

Self-contained 618-line plan synthesizing inputs from:
- traycerai[bot]: Phase structure validation
- coderabbitai[bot]: 9 actionable suggestions
- github-actions[bot]: Detailed PRD with success metrics

Covers:
- Phase 1: Foundation (pyproject.toml, pytest, security controls)
- Phase 2: New Development Guidelines
- Phase 3: Migration (priority order, deprecation timeline)

Complete code templates included for immediate execution.

Relates-to: #965

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* docs(planning): add verification sections for autonomous execution

Enhance ADR-042 implementation plan for amnesiac agent execution:
- Add Quick Verification section with pre-flight checks
- Add Session Protocol section with JSON template
- Add Local File References table (all verified 2026-01-18)
- Add repository field to header metadata

Plan now 712 lines, fully self-contained for context-free execution.

Relates-to: #965

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* feat(python)!: implement Phase 1 Python infrastructure (ADR-042)

BREAKING CHANGE: Language policy changes from PowerShell-only to Python-first

Phase 1 establishes Python infrastructure for new development:

Infrastructure:
- pyproject.toml: Project metadata, dependencies, tool configs (ruff, mypy, pytest)
- uv.lock: Hash-pinned dependencies for supply chain security (16 packages)
- tests/conftest.py: Shared pytest fixtures (project_root, temp_test_dir)
- .github/workflows/pytest.yml: CI workflow with paths-filter, coverage, pip-audit, bandit

Policy Updates:
- PROJECT-CONSTRAINTS.md: SHOULD prefer Python for new scripts (ADR-042)
- CRITICAL-CONTEXT.md: Python-first (.py preferred)
- .githooks/pre-commit: Non-blocking Python linting with ruff
- .github/dependabot.yml: pip ecosystem for dependency updates

Housekeeping:
- .gitignore: Python patterns (__pycache__, .venv, .egg-info, etc.)
- .markdownlint-cli2.yaml: Exclude .venv from linting

Verification: uv pip install -e ".[dev]" succeeds, pytest discovers 77 tests

Refs: #965, ADR-042

Co-Authored-By: Claude <noreply@anthropic.com>

* docs: update documentation for Python-first development (ADR-042)

Update CONTRIBUTING.md and AGENTS.md to reflect the Python migration:

- Change "Always Do" from PowerShell-only to Python-first for new scripts
- Update "Never Do" to prohibit bash only (Python now allowed)
- Add Python 3.12.x and UV to Tech Stack table
- Add pytest testing section with automated quality gates emphasis
- Update Development Tools commands to include Python testing
- Emphasize shift-left automation: pre-commit hooks and CI handle quality
- Note Python 3.12.x requirement due to Ubuntu 25 incompatibility

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* docs(session): update session log with documentation changes

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* feat(python): implement Phase 2 parallel infrastructure (ADR-042)

Add documentation and security utilities for Python development:

- Create CI/CD migration patterns guide for GitHub Actions integration
- Create Python security checklist covering CWE-22, CWE-78, CWE-798
- Create path validation utility with 42 tests for CWE-22 protection
- Create PowerShell-to-Python developer migration guide

Part of epic #965.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* feat(python): add pilot migration of Check-SkillExists to Python (ADR-042 Phase 3)

Migrates Check-SkillExists.ps1 to Python as the pilot script for ADR-042 Phase 3.
This demonstrates the migration patterns established in Phase 2.

Changes:
- scripts/check_skill_exists.py: Python port with argparse CLI, type hints,
  ADR-035 exit codes, and path_validation utility usage
- tests/test_check_skill_exists.py: 31 pytest tests with 88% coverage

The Python version provides:
- --list-available: Lists all skills by operation type
- --operation/--action: Checks if a skill exists using substring matching
- --project-root: Optional custom project root for testing

Both PowerShell and Python versions will run in parallel per migration plan.

Refs: #965

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* feat(python): add gradual rollout migrations (ADR-042 Phase 4)

Migrate two additional scripts from PowerShell to Python following
the pilot pattern established in Phase 3:

- Detect-SkillViolation.ps1 -> detect_skill_violation.py
  - 89% test coverage (35 tests)
  - Uses dataclass for Violation type
  - Integrates path_validation utility
  - Non-blocking warning for skill violations

- Validate-SessionJson.ps1 -> validate_session_json.py
  - 91% test coverage (39 tests)
  - Uses ValidationResult dataclass
  - Case-insensitive JSON key lookup
  - Pre-commit mode for compact output

Also fixes uv.lock format (was incorrectly in pip-tools format,
now in native uv format).

See: ADR-042 Python Migration Strategy, Issue #965

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(python): fix regex bug and dead code in detect_skill_violation

- Fixed regex pattern gh\\s\+ to gh\s+ in extract_capability_gaps
- Replaced duplicated capability extraction logic in report_violations
  with call to extract_capability_gaps function (DRY)
- All 34 tests pass

Issues identified by pr-review-toolkit parallel review agents.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(security): address gemini-code-assist security findings

**Security Fixes**:

1. **Path Validation (CWE-22)** - scripts/validate_session_json.py:
   - Added `validate_safe_path` import from scripts.utils.path_validation
   - Validate user-provided session_path before file operations
   - Prevents path traversal attacks (../, symlinks, etc.)

2. **Python Version Alignment** - pyproject.toml:
   - Updated ruff target-version: py310 → py312
   - Updated mypy python_version: 3.10 → 3.12
   - Aligns linting/type checking with project standard (3.12.x)

**Gemini Review Comments Addressed**:
- Comment 2702879539: Added path validation imports ✓
- Comment 2702879541: Added CWE-22 protection with validate_safe_path ✓
- Comment 2702879542: Updated ruff to target py312 ✓
- Comment 2702879543: Updated mypy to python 3.12 ✓

**Testing**:
- Verified imports work correctly
- Path validation prevents traversal attacks
- Session protocol validation: PASS

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

* refactor: slim instructions files by removing redundant agent registry (#961)

Remove agent catalog tables and routing heuristics from instruction
file templates. This content is already available in YAML frontmatter
of each agent file, which platforms parse directly.

- Claude: 129 → 45 lines (65% reduction)
- Copilot CLI: 126 → 53 lines (58% reduction)
- VSCode: 116 → 45 lines (61% reduction)

Estimated savings: ~2,000 tokens per session per platform.

Signed-off-by: Richard Murillo <6811113+rjmurillo@users.noreply.github.com>
Co-authored-by: Richard Murillo <richard.murillo@example.com>
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Richard Murillo <6811113+rjmurillo@users.noreply.github.com>

* docs(analysis): Factory-AI/droid-action security constraint blocker (#960)

* docs(analysis): document Factory-AI/droid-action security constraint blocker

Root cause analysis of Droid Auto Review workflow failure. The Factory-AI/droid-action
internally uses actions/upload-artifact@v4 (non-SHA-pinned), which violates repository
security constraints requiring all actions to be pinned to full-length commit SHAs.

Key findings:
- Latest droid-action version (e3f8be9f, 2026-01-12) still contains non-pinned references
- Repository security rules apply recursively to all nested action dependencies
- No workaround available without modifying third-party action or relaxing security constraints

Impact: BLOCKING - droid-review.yml and droid.yml workflows fail at setup phase

Recommendations:
- File issue with Factory-AI requesting SHA-pinned action references
- Evaluate alternative PR review automation tools
- Document as known limitation in operational runbook

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

* docs(session): update session-9 with PR comment responses

- Added workLog entries for PR #960 comment activities
- Documented upstream issue research (no issue exists)
- Added PR comments as deliverables
- Added learning pattern about upstream issue verification

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* docs: record upstream issue Factory-AI/droid-action#20

- Updated memory with upstream issue link and status
- Marked "file upstream issue" as DONE in recommendations
- Updated session log with issue filing activity
- Added next step to monitor for maintainer response

Upstream: Factory-AI/droid-action#20

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

---------

Co-authored-by: rjmurillo-bot <rjmurillo-bot@users.noreply.github.com>
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
Co-authored-by: Richard Murillo <richard.murillo@example.com>

* fix(ci): disable Droid workflows due to unpinned action (#957)

* chore: recover 650 orphaned session logs and memory files (#964)

* chore: recover 650 orphaned session logs and memory files

Extract artifacts from 52 feature branches that were left behind when
PRs auto-merged before session logs were pushed.

Recovery summary:
- Session logs: 378 files recovered
- Memory files: 272 files recovered
- Total: 650 files, 82,632 lines of content

Analysis found 61,497 file references across branches but only 1,728
unique files (average file in 35+ branches). Of these, 1,080 already
existed in main. The 648 truly orphaned files are now consolidated.

Used consolidated PR approach instead of 52 individual PRs to avoid
massive merge conflicts from overlapping content.

Note: 150 memory files use legacy 'skill-' prefix naming that predates
ADR-017. These are historical artifacts being preserved as-is.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

* docs: update session log with PR #964 details

Add PR information and audit trail for validation skip.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

---------

Co-authored-by: rjmurillo-bot <noreply@github.com>
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>

* feat: implement investigation-only session validator (ADR-034 Phase 1) (#931)

* Initial plan

* Add comprehensive test suite for investigation-only validation

Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>

* fix: convert functional tests to pattern-based tests to avoid git state dependency

Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>

* fix(validation): Allow .agents/memory/ in investigation-only sessions (#926)

* Initial plan

* feat: Add .agents/memory/ to investigation allowlist

Add .agents/memory/ pattern to investigation-only allowlist in Test-InvestigationEligibility.ps1 scripts and update tests. This allows memory infrastructure files like causal-graph.json to be committed in investigation sessions per ADR-034 memory-first principle.

Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>

* feat: Add verification-based session-start gates for Codex effectiveness (#924)

* Initial plan

* docs: add Codex effectiveness backlog and context optimization plan (Phase 1 complete)

Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>

* feat: add Codex session-start gate script with 4 verification gates (Phase 2 complete)

Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>

* Changes before error encountered

Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>
Co-authored-by: Richard Murillo <richard.murillo@example.com>
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>

* docs: standardize YAML array format for cross-platform compatibility (#923)

* Initial plan

* refactor: convert frontmatter to block-style YAML arrays in prompt and command files

Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>

* docs: update frontmatter examples to use block-style YAML arrays

Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>

* docs(governance): add YAML frontmatter array format constraint

- Add YAML Frontmatter Constraints section to PROJECT-CONSTRAINTS.md
- Include rationale with evidence from Session 826 RCA and GitHub Copilot CLI Issue #694
- Add validation checklist item for frontmatter arrays
- Add frontmatter validation requirement to SKILL-CREATION-CRITERIA.md
- Create session log for session 02

Refs: #898, Session 826

* docs: add issue URLs to YAML array format references

Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>
Co-authored-by: Richard Murillo <richard.murillo@example.com>
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>

* docs: improve autonomous-issue-development.md structure (#566)

* docs: improve autonomous-issue-development.md structure

Expand documentation from 46 to 441 lines to match autonomous-pr-monitor.md style:

- Add "Common Development Patterns" section (5 validated patterns)
- Add "Troubleshooting" section (5 common scenarios)
- Enhance "Example Session Output" with TodoWrite and agent handoffs
- Add "Workflow Phases" table for quick reference
- Add "Agent Responsibilities" reference table
- Add "Prerequisites" and "Related Documentation" sections

Closes #506

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(session): add protocol compliance sections

Added Session Start and Session End checklist tables to match
the required session protocol format.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(security): prevent command injection in PR creation example

Addresses gemini-code-assist[bot] security review comment #2653014226.

The example showed a hardcoded PR title which could enable command
injection if autonomous agents construct titles from untrusted GitHub
issue titles containing shell metacharacters (e.g., $(reboot)).

Changes:
- Add security warning comment explaining CWE-78 risk
- Use read -r with process substitution to safely read issue title
- Demonstrate secure pattern for handling untrusted external input

This aligns with security principle of validating all external inputs.

Comment-ID: 2653014226

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

---------

Co-authored-by: rjmurillo[bot] <rjmurillo-bot@users.noreply.github.com>
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Claude <claude@anthropic.com>

* feat: implement local GitHub Actions validation and testing infrastructure (#925)

* Initial plan

* feat: Add actionlint validation for GitHub Actions workflows (Phase 1)

- Add actionlint to pre-commit hook (.githooks/pre-commit)
- Integrate actionlint into unified validation runner (scripts/Validate-PrePR.ps1)
- Add actionlint to Worktrunk pre-merge hooks (.config/wt.toml)
- Update SHIFT-LEFT.md documentation with workflow YAML validation section
- Update validation sequence to include step 3.5 (Workflow YAML)
- Create session log 2026-01-15-session-01-github-actions-local-testing.json

This implements Phase 1 (P0) of the GitHub Actions local testing epic.
actionlint catches 80%+ workflow YAML errors before push, reducing expensive CI iteration cycles.

Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>

* feat: Add act support for local workflow testing (Phase 2)

- Create .actrc configuration with optimized defaults for act
- Create scripts/Test-WorkflowLocally.ps1 PowerShell wrapper for act
- Update SHIFT-LEFT.md with comprehensive local workflow testing documentation
- Document supported workflows (pester-tests, validate-paths, memory-validation)
- Document unsupported workflows (AI-dependent: ai-session-protocol, etc.)
- Add troubleshooting guide for act and PowerShell issues

This implements Phase 2 (P1) of the GitHub Actions local testing epic.
Enables local testing for PowerShell-only workflows without CI round-trips.

Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>

* feat: Add yamllint for YAML style validation (Phase 3)

- Create .yamllint.yml configuration with GitHub Actions-optimized rules
- Add yamllint validation to scripts/Validate-PrePR.ps1 (validation 3.9)
- Add yamllint to pre-commit hook (.githooks/pre-commit) as non-blocking warnings
- Update SHIFT-LEFT.md with YAML style validation documentation
- Document yamllint vs actionlint relationship (style vs semantics)
- Configure yamllint as non-blocking to avoid impeding development velocity

This implements Phase 3 (P2) of the GitHub Actions local testing epic.
yamllint enforces YAML style consistency while actionlint handles semantic validation.

Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>

* docs: Update session log with completion status

* fix: Address PR feedback on local testing infrastructure

- Add gh act extension to installation instructions
- Include .github/actions in actionlint validation scope
- Remove chocolatey recommendation, use GitHub releases instead
- Clarify Copilot CLI installation vs BOT_PAT requirement for AI workflows
- Switch to full production images in .actrc for maximum compatibility
- Update documentation to reflect full image usage and rationale

Addresses comments: 2693400619, 2693406075, 2693409506, 2693411769, 2693418268

Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>

* refactor: Move Test-WorkflowLocally.ps1 to .claude/skills/github/scripts

- Move Test-WorkflowLocally.ps1 from scripts/ to .claude/skills/github/scripts/
- Update all documentation references in SHIFT-LEFT.md
- Update session log to reflect new location

Addresses comment 2699896328

Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>

* fix: address all PR #925 review comments

Fixes all 15 unresolved review threads from owner and automated reviewers:

1. Remove duplicate actionlint validation block in pre-commit hook
   - Kept newer comprehensive version (validates workflows + actions)
   - Removed old TIER 1 block (lines 269-313)

2. Fix wt.toml to validate both workflows and actions directories
   - Changed: actionlint .github/workflows/*.yml .github/actions/*.yml
   - Matches pre-commit hook validation scope

3. Remove Windows-specific chocolatey references
   - Prioritize cross-platform gh extension
   - Show macOS brew as alternative
   - Link to releases for manual download

4. Rename Write-Warning to Write-WarningMessage
   - Avoids shadowing PowerShell built-in cmdlet
   - Updated all call sites

5. Fix Validate-PrePR.ps1 to match both .yml and .yaml files
   - Changed -Filter to -Include with both extensions
   - Applies to both workflow and YAML validation sections

6. Fix session log field name inconsistencies
   - Changed handoffNotUpdated.evidence -> Evidence
   - Changed handoffNotUpdated.complete -> Complete
   - Matches other compliance entries

7. Add endingCommit to session log
   - Set to 38217dc (latest commit)
   - Required field per session protocol

8. Fix Test-WorkflowLocally.ps1 null handling
   - Check for null before Test-Path call
   - Prevents crash under Set-StrictMode when workflow not found

All fixes maintain existing functionality while addressing review feedback.

Related: #925

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>
Co-authored-by: Richard Murillo <richard.murillo@example.com>
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>

* fix: ADR-017 memory validation compliance (skill- prefix removal + bundled skill splitting) (#966)

* fix(pr-964): clean up session files and remove skill- prefix violations

Addresses two validation failures in PR #964:

1. Session file cleanup:
   - Moved 341 .md session files to .agents/archive/sessions/
   - Deleted 1 session file already in archive
   - All moved files have corresponding JSON equivalents

2. Memory file ADR-017 compliance:
   - Removed 87 duplicate memory files with skill- prefix
   - Renamed 56 unique memory files to remove skill- prefix
   - Zero skill- prefixed files remain
   - Added skills-serena-index to memory-index.md

These legacy files predate ADR-017 naming conventions and were
recovered from 52 orphaned branches. The skill- prefixed duplicates
existed alongside non-prefixed versions and have been cleaned up.

Note: Bundled skill validation failures are pre-existing in PR #964
and require separate handling via skill unbundling process.

Script: scripts/Fix-PR964-Validation.ps1

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

* refactor: split 37 bundled skill files into 135 atomic files per ADR-017

Split bundled skill files to comply with one-skill-per-file standard.

Changes:
- Created scripts/Split-BundledSkills.ps1 automation script
- Split 37 bundled files containing 135 skills total
- Generated 110 new atomic skill files with proper naming
- Modified 25 existing skill files
- Deleted 37 bundled files

Validation:
- Validate-SkillFormat.ps1: PASSED
- markdownlint: PASSED (0 errors)

Context: PR #964 recovered orphaned files that predate ADR-017
Note: Memory index will be updated in a follow-up commit

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

* docs: update session log to JSON schema v1.0

Update session-04 log to use new JSON schema format with protocolCompliance
and learnings sections per SESSION-PROTOCOL.md requirements.

Validation: Validate-SessionJson.ps1 PASSED

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

* fix: convert skills-serena-index to table-only format per ADR-017

---------

Co-authored-by: rjmurillo-bot <noreply@github.com>
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>

* fix(ci): use PATH export instead of source env for uv

The uv installer no longer creates an env file to source. Replace
`source $HOME/.local/bin/env` with `export PATH="$HOME/.local/bin:$PATH"`
to properly add uv to PATH in GitHub Actions workflows.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(ci): add --system flag to uv pip install

uv pip now requires either a virtual environment or the --system flag
to install packages. Add --system flag for GitHub Actions workflows
where we want to install directly to the system Python.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* feat(ci): enable Python tooling for agent contributions

- Add Python setup to setup-code-env composite action with:
  - enable-python and python-version inputs
  - Python version output
  - Python dependency installation via uv
  - Verification of ruff and pytest availability
- Enable Python 3.12 in copilot-setup-steps workflow
- Add Python dependency installation to bootstrap-vm.sh

This enables agents to contribute Python code with proper
tooling (ruff, pytest) available in the development environment.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(ci): use pip-audit without --requirement flag

The --requirement flag expects requirements.txt format, not pyproject.toml.
Running pip-audit without arguments audits installed packages instead.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(tests): patch SAFE_BASE_DIR for temp directory tests

- Monkeypatch _PROJECT_ROOT in validate_session_json tests
- Monkeypatch SAFE_BASE_DIR in invoke_skill_learning tests
- Fix tests checking 'extracted_learning' to use 'source' key

The path validation correctly rejects temp directories outside
project root. Tests now patch the base directory to allow temp
paths during testing while maintaining security in production.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(hooks): rename test_skill_context to check_skill_context

Pytest was collecting the function as a test because it started
with 'test_'. Renamed to 'check_skill_context' to prevent pytest
from treating it as a test function.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* docs: add test exit code interpretation as blocking constraint

- Add testing-exit-code-interpretation memory documenting that pytest
  "X passed, Y errors" output means test suite FAILED (non-zero exit)
- Update AGENTS.md Testing section with BLOCKING Test Exit Code
  Interpretation subsection
- Update CRITICAL-CONTEXT.md with explicit test exit code requirement
- Update memory-index with new memory for discoverability

Learning: "error" and "failed" are both non-pass outcomes in pytest.
Both result in non-zero exit code and must block commits.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

---------

Signed-off-by: Richard Murillo <6811113+rjmurillo@users.noreply.github.com>
Co-authored-by: Test <test@test.com>
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Richard Murillo <richard.murillo@example.com>
Co-authored-by: Richard Murillo <6811113+rjmurillo@users.noreply.github.com>
Co-authored-by: rjmurillo-bot <rjmurillo-bot@users.noreply.github.com>
Co-authored-by: rjmurillo-bot <noreply@github.com>
Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>
Co-authored-by: Claude <claude@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants