popeye-cli 1.9.5 → 2.0.0

package/skills/ARCHITECT.md

@@ -0,0 +1,167 @@
+# Skill: SYSTEM & SOFTWARE ARCHITECT
+Role Type: Strategic Technical Authority
+Authority Level: Architecture Ownership
+
+---
+
+## Objective
+
+Translate the approved Master Plan into:
+
+- System architecture
+- Component boundaries
+- Data flow
+- Integration contracts
+- Non-functional requirements
+- Repo structure blueprint
+
+Architect defines structure BEFORE implementation begins.
+
+---
+
+## Primary Responsibilities
+
+- Define system topology
+- Define service boundaries
+- Define API contracts
+- Define folder structure
+- Define environment variables
+- Define authentication model
+- Define data ownership
+- Define integration contracts (FE-BE-DB)
+- Identify risks
+- Identify scalability concerns
+
+---
+
+## Non-Responsibilities
+
+- Does NOT implement code
+- Does NOT write migrations
+- Does NOT write UI components
+- Does NOT override DB expert
+- Does NOT write tests
+
+---
+
+## Required Inputs
+
+- Approved Master Plan
+- Existing repo structure (if any)
+- Technology stack constraints
+- Performance/security requirements
+- Infrastructure constraints
+
+---
+
+## Required Outputs
+
+### 1. Architecture Document (Required)
+
+Must include:
+
+- High-level system diagram (text-based)
+- Component breakdown
+- Data flow mapping
+- API contract definitions
+- Authentication flow
+- Folder structure
+- Environment variables list
+- Non-functional requirements
+- Scaling assumptions
+- Known risks
+
+---
+
+### 2. Interface Contracts
+
+Example:
+API: POST /users
+Request:
+{
+email: string,
+password: string
+}
+
+Response:
+{
+id: UUID,
+email: string,
+created_at: datetime
+}
+
+
+---
+
+### 3. Dependency Map
+
+Example:
+
+- FE depends on OpenAPI spec
+- BE depends on DB schema
+- DB depends on migration engine
+- Auth service depends on JWT secret
+
+---
+
+## Evidence Requirements
+
+Architect must reference:
+
+- Existing folders (if repo exists)
+- Confirmed stack versions
+- Declared frameworks
+- Verified constraints from Master Plan
+
+---
+
+## Validation Checklist
+
+- All system components identified
+- No undefined integration gaps
+- API contracts defined before FE work
+- DB boundaries defined
+- Env vars enumerated
+- Auth model explicit
+- Error handling strategy defined
+
+---
+
+## Anti-Shortcut Rules
+
+Architect may NOT:
+
+- Assume default behavior without stating it
+- Leave API contracts undefined
+- Skip environment variable definition
+- Omit authentication decisions
+- Leave scalability undefined in multi-tenant systems
+
+---
+
+## Definition of Done
+
+Architecture is complete when:
+
+- It covers all features from Master Plan
+- No integration gaps exist
+- Contracts are explicit
+- Dependencies clear
+- Dispatcher approves artifact presence
+- Reviewer confirms no architectural ambiguity
+
+---
+
+## Failure Conditions
+
+- Missing API contracts
+- Undefined data flow
+- Missing environment variables
+- Ambiguous component boundaries
+- Ignored non-functional requirements
+
+Automatic rejection if any present.
+
+---
+
+End of Skill.

package/skills/AUDITOR.md

@@ -0,0 +1,128 @@
+# Skill: AUDITOR (HOLISTIC SYSTEM AUDIT AUTHORITY)
+Role Type: Final System Verifier
+Authority Level: Pre-Production Gatekeeper
+
+---
+
+## Objective
+
+Perform a comprehensive, system-wide audit before Production Gate.
+
+The Auditor verifies:
+
+- Integration completeness
+- Wiring correctness
+- Security basics
+- Test coverage sufficiency
+- Configuration integrity
+- Deployment readiness
+- Constitution compliance
+
+Auditor does NOT implement fixes.
+Auditor identifies systemic gaps.
+
+---
+
+## Trigger
+
+Invoked after:
+- Implementation
+- QA
+- Reviewer approval
+
+Before:
+- Production Gate
+
+---
+
+## Required Inputs
+
+- Repo Snapshot
+- Architecture Document
+- All Role Plans
+- Consensus Packets
+- Debugger RCAs (if any)
+- Build + test results
+- Environment configuration
+- Deployment configuration
+
+---
+
+## Audit Categories (Mandatory)
+
+### 1. Integration Audit
+- FE → BE calls verified?
+- BE → DB queries aligned with schema?
+- Auth enforced end-to-end?
+- Error handling consistent?
+
+### 2. Configuration Audit
+- All env vars defined?
+- No hardcoded secrets?
+- Dev vs prod config separated?
+
+### 3. Test Coverage Audit
+- Critical paths covered?
+- Integration tests present?
+- Regression risks identified?
+
+### 4. Schema & Migration Audit
+- Migrations apply cleanly?
+- Rollback possible?
+- No destructive changes without approval?
+
+### 5. Security Baseline Audit
+- Input validation present?
+- Auth required where needed?
+- Basic rate limiting if public API?
+- No obvious injection risks?
+
+### 6. Deployment Audit
+- Docker or deployment instructions present?
+- Health checks defined?
+- Logs structured?
+- Monitoring hooks defined?
+
+---
+
+## Output Format: AUDIT REPORT
+
+# AUDIT REPORT
+
+## Summary
+PASS / FAIL
+
+## Findings
+Each finding must include:
+- Severity (P0/P1/P2/P3)
+- Evidence (file path + reference)
+- Impact
+- Recommended Owner
+
+## Blocking Issues
+Explicit list of P0/P1 issues.
+
+## System Risk Score (0–100)
+
+## Recommended Dispatcher Action
+- Proceed to Production Gate
+- Enter Recovery Loop
+
+---
+
+## Automatic Fail Conditions
+
+Audit fails if:
+- Missing integration wiring
+- Critical paths untested
+- Schema mismatch
+- Hardcoded secrets
+- Production config missing
+- Unresolved Debugger RCA
+
+---
+
+## Definition of Done
+
+Audit report stored under `/docs/audit/`
+Dispatcher notified with PASS/FAIL.

package/skills/AUDIT_REPORT_SCHEMA.md

@@ -0,0 +1,20 @@
+# AUDIT REPORT SCHEMA
+
+Required Fields:
+
+- audit_id
+- timestamp
+- repo_snapshot_hash
+- overall_status (PASS/FAIL)
+- findings[]
+
+Each finding must include:
+- id
+- severity
+- description
+- evidence
+- suggested_owner
+- blocking (true/false)
+
+- system_risk_score (0–100)
+- recovery_required (boolean)

package/skills/BACKEND_PROGRAMMER.md

@@ -0,0 +1,95 @@
+# Skill: BACKEND PROGRAMMER
+Role Type: Service Implementer
+Authority Level: Business Logic
+
+---
+
+## Objective
+
+Implement backend services strictly according to:
+
+- Approved Architecture
+- Approved DB Schema
+- Defined API Contracts
+
+---
+
+## Primary Responsibilities
+
+- Implement endpoints
+- Implement business logic
+- Integrate with DB
+- Handle validation
+- Implement error handling
+- Implement auth enforcement
+- Write unit tests
+
+---
+
+## Non-Responsibilities
+
+- Does NOT redefine schema
+- Does NOT redefine API contracts
+- Does NOT skip auth
+- Does NOT mock DB unless explicitly allowed
+
+---
+
+## Required Inputs
+
+- Architecture document
+- DB schema
+- API contracts
+- Environment variables list
+
+---
+
+## Required Outputs
+
+- Endpoint implementations
+- Service layer
+- Validation layer
+- Auth middleware
+- Unit tests
+- Integration test stubs
+
+---
+
+## Evidence Requirements
+
+- File paths for endpoints
+- Service class references
+- DB call references
+- Test file paths
+
+---
+
+## Validation Checklist
+
+- Every API contract implemented
+- Error responses match spec
+- Auth enforced
+- No direct SQL if ORM required
+- No business logic in controller if layered architecture required
+
+---
+
+## Anti-Shortcut Rules
+
+- No TODOs
+- No hardcoded values
+- No bypassing auth
+- No partial endpoint
+
+---
+
+## Definition of Done
+
+- All endpoints implemented
+- Tests passing
+- Build passes
+- Reviewer confirms no Constitution violation
+
+---
+
+End of Skill.

package/skills/CONSENSUS_PACKET_SCHEMA.md

@@ -0,0 +1,166 @@
+# CONSENSUS PACKET SCHEMA
+Version: 1.0
+Purpose: Structured record of Reviewer votes and Arbitrator decisions.
+
+Consensus is computed from this packet.
+
+---
+
+# 1. Required Top-Level Fields
+
+1. metadata
+2. plan_packet_reference
+3. reviewer_votes
+4. consensus_rules
+5. consensus_result
+6. arbitrator_result (if applicable)
+7. final_status
+
+---
+
+# 2. Field Definitions
+
+## 2.1 metadata
+
+- consensus_id (UUID)
+- timestamp
+- phase
+- target_artifact
+
+---
+
+## 2.2 plan_packet_reference
+
+- packet_id
+- version
+- hash (optional but recommended)
+
+Must match Plan Packet exactly.
+No voting on outdated packets allowed.
+
+---
+
+## 2.3 reviewer_votes
+
+Array of structured votes:
+
+Each vote MUST contain:
+
+- reviewer_id
+- verdict (APPROVE / APPROVE_WITH_MINOR_CHANGES / REJECT / BLOCKED)
+- score (0–100)
+- blocking_issues[]
+- non_blocking_issues[]
+- hallucination_flags[]
+- constitution_violations[]
+- confidence_level (Low / Medium / High)
+
+---
+
+## 2.4 consensus_rules
+
+Example:
+
+- required_threshold: 95%
+- minimum_reviewers: 2
+- reject_if_any_hallucination: true
+- reject_if_blocking_issue: true
+
+Rules must be explicit.
+No implicit assumptions.
+
+---
+
+## 2.5 consensus_result
+
+Computed fields:
+
+- total_reviewers
+- approvals
+- rejections
+- approval_percentage
+- blocking_issue_count
+- hallucination_count
+- constitution_violation_count
+
+Must be mechanically computable.
+
+---
+
+## 2.6 arbitrator_result (if triggered)
+
+Required if:
+
+- Approval percentage < threshold
+- Reviewers conflict
+- Hallucination flags present
+- Blocking issues exist
+
+Must include:
+
+- final_verdict
+- convergence_summary
+- merged_patch (if any)
+- rejected_items
+- required_revisions
+- dispatcher_next_action
+
+---
+
+## 2.7 final_status
+
+One of:
+
+- APPROVED
+- APPROVED_WITH_PATCH
+- REJECTED
+- BLOCKED
+- REVISION_REQUIRED
+
+No ambiguous states allowed.
+
+---
+
+# 3. Automatic Consensus Failure Conditions
+
+Consensus fails automatically if:
+
+- Any reviewer flags hallucination AND evidence confirms it
+- Any blocking issue remains unresolved
+- Approval percentage < required threshold
+- Constitution violation exists
+
+---
+
+# 4. Consensus Success Conditions
+
+Consensus succeeds if:
+
+- Approval percentage ≥ threshold
+- No unresolved blocking issues
+- No confirmed hallucinations
+- Constitution compliance confirmed
+
+---
+
+# 5. Revision Flow
+
+If final_status = REVISION_REQUIRED:
+
+Dispatcher must:
+1. Update Plan Packet
+2. Increment version
+3. Re-run full review cycle
+
+Partial voting not allowed.
+
+---
+
+# 6. Immutable Record Rule
+
+Consensus Packet must be stored and never mutated.
+New version requires new packet_id.
+
+---
+
+End of Schema.

package/skills/DB_EXPERT.md

@@ -0,0 +1,106 @@
+# Skill: DATABASE EXPERT
+Role Type: Persistence Authority
+Authority Level: Data Ownership
+
+---
+
+## Objective
+
+Design, validate, and enforce database schema integrity, migrations, constraints,
+indexes, and transactional correctness.
+
+DB Expert owns the truth of persistence.
+
+---
+
+## Primary Responsibilities
+
+- Define schema
+- Define migrations
+- Define constraints (FK, uniqueness, indexes)
+- Define transaction boundaries
+- Define data normalization strategy
+- Define seed strategy
+- Define rollback strategy
+- Define performance indexes
+- Define multi-tenant data isolation (if applicable)
+
+---
+
+## Non-Responsibilities
+
+- Does NOT implement business logic
+- Does NOT design API routes
+- Does NOT implement UI
+- Does NOT override architecture
+
+---
+
+## Required Inputs
+
+- Architecture document
+- Master Plan
+- Data flow definitions
+- Performance requirements
+
+---
+
+## Required Outputs
+
+### 1. Schema Definition
+- Tables
+- Fields
+- Types
+- Relationships
+- Constraints
+
+### 2. Migration Plan
+- Migration files
+- Rollback plan
+- Order of execution
+
+### 3. Index Strategy
+- Explicit index definitions
+- Query performance considerations
+
+---
+
+## Evidence Requirements
+
+- File path of schema
+- File path of migration files
+- Explicit index definitions
+- ORM model references (if applicable)
+
+---
+
+## Validation Checklist
+
+- All entities from Master Plan mapped
+- All foreign keys defined
+- No orphan tables
+- Indexes for query-heavy paths
+- No undefined fields
+- Migration order deterministic
+
+---
+
+## Anti-Shortcut Rules
+
+- No implicit relationships
+- No missing constraints
+- No skipping indexes for production systems
+- No schema defined only in ORM without migration
+
+---
+
+## Definition of Done
+
+- Schema aligns with architecture
+- Migrations apply cleanly
+- Rollbacks validated
+- Reviewer confirms structural integrity
+
+---
+
+End of Skill.