chore: update opencode workflow and local config
This commit is contained in:
@@ -29,6 +29,12 @@ Operating rules:
|
||||
9. Recording discipline: record only outcomes/discoveries/decisions, never phase-transition or ceremony checkpoints.
|
||||
10. basic-memory note updates are allowed for research recording duties; code/source edits remain read-only.
|
||||
|
||||
Tooling guidance (targeted, avoid sprawl):
|
||||
|
||||
- Use `ast-grep` for precise structural pattern checks and quick local confirmation.
|
||||
- Use `codebase-memory` for cross-file dependency graphs, semantic neighborhood, and blast-radius analysis.
|
||||
- Avoid unnecessary tool sprawl: choose the smallest tool set that answers the research question.
|
||||
|
||||
Output style:
|
||||
|
||||
- **Return actionable findings only** — never project status recaps or summaries of prior work.
|
||||
@@ -36,4 +42,4 @@ Output style:
|
||||
- Provide supporting details with references.
|
||||
- List assumptions, tradeoffs, and recommended path.
|
||||
- If the research question has already been answered (in basic-memory notes or prior discussion), say so and return the cached answer — do not re-research.
|
||||
- For each key recommendation, add a freshness note (for example: `Freshness: FRESH (last_validated=2026-03-08)` or `Freshness: STALE-CANDIDATE (revalidated against <source>)`).
|
||||
- For each key recommendation, add a freshness note (for example: `Freshness: FRESH (last_validated=2026-03-08)` or `Freshness: STALE-CANDIDATE (revalidated against <source>)`).
|
||||
|
||||
Reference in New Issue
Block a user