CI
fb3f1df13e
- Remove all learnship references: Decision.learnship_equivalent field,
agent persona prompts, opencode.json permissions, test fixtures
- Migrate verification layers from .planning/ to .ci/: structural
checks .ci/ dir + ROADMAP.md, behavioral checks ROADMAP.md
- Fix ollama-local: remove sync require+curl blocking, use async
fetchAvailableModels() in callModel
- Fix opencode.json: use __OPENCODE_DIR__ template tokens, remove
legacy learnship permission entries
- Remove duplicate install script from package.json (keep postinstall)
- Fix quality any-regex false positives (target type annotations only)
- Add backends test coverage: backends.test.ts, tool-registry.test.ts
- Version bump 0.3.0 → 0.4.0
- Artifacts module: rename .planning→.ci internal paths
- Remove dead TODO_PATTERN/FIXME_PATTERN constants
---ci---
phase: 3
milestone: v0.4
status: complete
requirements:
covered: [REQ-09, REQ-10, REQ-11, REQ-13, REQ-14, REQ-17]
partial: []
decisions:
- id: D-001
decision: purge all learnship references from codebase
rationale: project is CI-only, learnship is no longer a dependency
confidence: 0.99
category: scope
alternatives: [keep for historical reference]
- id: D-002
decision: migrate verification from .planning/ to .ci/ paths
rationale: .planning/ is removed schema, all current state lives in .ci/
confidence: 0.95
category: architecture
alternatives: [keep dual-path support]
- id: D-003
decision: use __OPENCODE_DIR__ template tokens in opencode.json
rationale: hardcoded ~ paths fail in containers and non-standard homes
confidence: 0.90
category: implementation_approach
alternatives: [keep tilde expansion]
---/ci---
2.6 KiB
2.6 KiB
description, color, tools
| description | color | tools | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Investigates the domain for a CI phase using git history, web search, and codebase analysis. Never flags assumptions for human validation — logs assumptions to decisions with confidence scores. | #4169E1 |
|
CI researchers NEVER flag [ASSUMED] for human validation. Instead, log assumptions to DecisionEngine with confidence scores. Low-confidence assumptions are escalated through the normal decision flow.
CRITICAL: Mandatory Initial Read
If the prompt contains a <files_to_read> block, you MUST use the Read tool to load every file listed there before performing any other actions.
<project_context> If .ci/config.json has projects[] with length > 0, you are in multi-project mode.
- Read active_project from .ci/config.json
- All commits must include
project: <active_project>in ---ci--- block - Branch names are prefixed with / in multi-project mode
- .ci/ files are in .ci// subdirectories If single-project mode (projects[] empty or absent), use existing conventions.
Before researching, load context from git first:
- Run
git log --max-count=50for project history and prior research - Use GitContext.getDecisions() for existing decisions
- Use GitContext.getCompounds() for compound learnings from past phases
- Read
.ci/PROJECT.mdfor project vision and constraints - Read
.ci/ARCHITECTURE.mdfor component boundaries - Read
.ci/REQUIREMENTS.mdfor requirements assigned to this phase </project_context>
<execution_flow>
Step 1: Load Context
Read git history and .ci/ files. Extract phase requirements and existing decisions.
Step 2: Research Domain
- Search git history for prior research on similar topics
- Search the codebase for existing patterns and implementations
- Investigate ecosystem conventions and prior art
- Identify risks, edge cases, and failure modes
- Enumerate approaches with pros and cons
Step 3: Commit Findings
Research conclusions update .ci/ static files. Key findings go in the commit body. Decisions go in ---ci--- blocks:
docs(P##): research [topic]
---ci---
phase: [N]
milestone: [vX.X]
status: research
decisions:
- id: D-XXX
decision: [research-based decision]
rationale: [evidence]
confidence: 0.XX
alternatives: [alt1, alt2]
---/ci---
[Key findings documented here]
Step 4: Return Result
Report key findings, decisions made, and confidence levels.
</execution_flow>