mercury-agent 0.5.2 → 0.5.6

package/docs/templates/TEMPLATE-BUG.md

@@ -1,71 +0,0 @@
-# Bug: {Title}
-
-**Status**: Open | In-Progress | Fixed
-**Severity**: minor | moderate | major
-**Slug**: {slug}
-**Reported**: {YYYY-MM-DD}
-**Last updated**: {YYYY-MM-DD}
-
----
-
-## Summary
-
-{One-sentence description of what's broken and where.}
-
-## Steps to Reproduce
-
-1. 
-2. 
-3. 
-
-## Expected Behavior
-
-{What should happen.}
-
-## Actual Behavior
-
-{What actually happens. Include any error messages or observable symptoms.}
-
-## Impact
-
-- {Who or what is affected, and how severely.}
-
-## Suspected Location
-
-- {File path(s) or component(s) most likely responsible.}
-
-## Notes
-
-- {Workarounds, related issues, env var context, etc.}
-
----
-
-## Implementation Checklist
-
-- [ ] Root cause identified
-- [ ] Fix implemented
-- [ ] `{your check command}` passes
-- [ ] No secrets or `.env` files committed
-- [ ] No unrelated files modified
-
----
-
-## Post-Mortem
-
-> Fill in after the fix is complete.
-
-### Investigation
-
-{How you traced the bug — files read, code paths followed, assumptions tested.}
-
-### Root Cause
-
-{Precise explanation of the defective code and why it caused the symptom.}
-
-### Fix
-
-{What changed and why. Include file paths and key line references.}
-
-### Lessons
-
-- {Takeaways applicable to future work — patterns to avoid, checks to add, etc.}

package/docs/templates/TEMPLATE-CI.yml

@@ -1,25 +0,0 @@
-name: CI
-
-on:
-  push:
-    branches: [main]
-  pull_request:
-    branches: [main]
-
-jobs:
-  check:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      # TODO: Add stack setup steps, e.g.:
-      # - uses: actions/setup-node@v4
-      #   with: { node-version: 20 }
-      # - run: npm ci
-
-      - name: Run checks
-        run: |
-          # TODO: Paste your check command from .claude/project-checks.md
-          # Example: npm run typecheck && npm run lint && npm test
-          echo "CI not configured — fill in the check command above"
-          exit 1

package/docs/templates/TEMPLATE-DECISIONS.md

@@ -1,11 +0,0 @@
-# Decisions: {Goal Title}
-
-**Goal**: [{goal-slug}](goal.md)
-
-## D-001: {Decision title}
-- **Category:** tech-stack | architecture | scope | pattern | trade-off
-- **Decided:** {what was chosen}
-- **Alternatives considered:** {list}
-- **Reasoning:** {why this choice}
-- **Revisit if:** {condition that would invalidate this decision}
-- **Used by:** {feature-slug-1}, {feature-slug-2}

package/docs/templates/TEMPLATE-FEATURE.md

@@ -1,127 +0,0 @@
-# {Feature Name}
-
-**Status**: Proposed | Backlog | In-Progress | Done
-**Slug**: {slug}
-**Created**: {YYYY-MM-DD}
-**Last updated**: {YYYY-MM-DD}
-
----
-
-## Goal
-
-> One paragraph. Why does this feature exist? What problem does it solve, for whom, and why now?
-
-## User Stories
-
-- As a {role}, I want {action} so that {outcome}.
-
-## MVP Scope
-
-**In scope:** what ships in v1.
-
-**Out of scope:** what is explicitly deferred — each item with a one-line reason.
-
----
-
-## Context for Claude
-
-> Key files to read before touching anything. 2-5 pointers — the exact paths and what lives there.
-
-- `{path/to/file}` — relevant pattern / existing logic
-
----
-
-## Architecture & Data
-
-### Data Models
-
-Schema definitions, column types, relationships, migrations required.
-
-```
-// exact table/type definitions here
-```
-
-### API Contracts
-
-Endpoints — HTTP method, URL, auth, request body, response shapes, error codes.
-
-### File & Folder Structure
-
-| Path | New / Modified | Purpose |
-|------|---------------|---------|
-| `{path}` | New | … |
-
-### Implementation Sequence
-
-Ordered steps. Call out blockers explicitly ("Step 3 must precede Step 4 because…").
-Each step must include `Read first:` (files to load before starting) and `Verify:` (how to confirm the step is done).
-
-1. {Description}
-   - Read first: `{path}`
-   - Verify: {observable outcome or command}
-
----
-
-## Non-Negotiable Rules
-
-> Hard constraints that must not be violated. Security invariants, data-loss rules, API contracts other systems depend on.
-
-- Rule 1
-- Rule 2
-
----
-
-## Edge Cases & Risks
-
-| Scenario | Handling |
-|----------|---------|
-| … | … |
-
----
-
-## Implementation Checklist
-
-### Phase 1 — Goal (fill before asking for approval)
-- [ ] Goal, User Stories, and MVP Scope written and reviewed
-
-### Phase 2 — Architecture (fill after Goal approved)
-- [ ] Architecture & Data section complete
-- [ ] Non-Negotiable Rules defined
-- [ ] Edge Cases covered
-- [ ] Context for Claude pointers filled in
-
-### Implementation (tick off as you go)
-- [ ] Step 1 …
-- [ ] Step 2 …
-- [ ] `{your check command}` passes
-- [ ] No secrets or `.env` files committed
-- [ ] No unrelated files modified
-- [ ] All user stories verifiably met
-
----
-
-## Open Questions
-
-- [ ] Question 1 — owner: TBD
-
----
-
-## Retrospective
-
-> Fill this section when archiving. 3–5 bullets max. Focus on surprises and decisions — not a summary of what was built (the code is the record of that).
-
-**Residual risks / follow-ups:**
-> Every known limitation or deferred risk must be tracked or accepted — `/f-feature-dev` hard-blocks archival otherwise. Each bullet must be one of: `<desc> → ideas/<slug>.md`, `<desc> → backlog/<slug>.md`, `<desc> — accepted`, or exactly `- none` if there are no residual risks.
-- none
-
-**What changed from the plan:**
-- …
-
-**Key decisions made during implementation:**
-- …
-
-**Architecture impact** (update `docs/ARCHITECTURE.md` if any of these apply):
-- [ ] New package/module added
-- [ ] New data model or schema change
-- [ ] New inter-package interaction
-- [ ] Deployment topology changed

package/docs/templates/TEMPLATE-GOAL.md

@@ -1,31 +0,0 @@
-# {Goal Title}
-
-**Status**: Proposed | Active | Paused | Complete | Abandoned
-**Slug**: {goal-slug}
-**Created**: {YYYY-MM-DD}
-**Last updated**: {YYYY-MM-DD}
-
----
-
-## Goal Statement
-
-{The user's original goal, captured verbatim or lightly edited for clarity}
-
-## Constraints
-
-{Hard constraints: budget, timeline, must-integrate-with, regulatory, etc.
-"None stated" if the user had none.}
-
-## Preferences
-
-{User preferences: "use Vue.js", "keep it simple", "no ORMs", etc.
-Each preference is labeled (required) or (preferred) or (you decide).
-"None stated" if the user left all decisions to AI.}
-
-## Target Users
-
-{Who uses this product and how. If not stated, AI's best inference marked as "(inferred)".}
-
-## Success Criteria
-
-{What "done" looks like — observable, testable outcomes. 3-5 bullets max.}

package/docs/templates/TEMPLATE-IDEA.md

@@ -1,31 +0,0 @@
-# {Idea Title}
-
-**Status**: Idea | Considering | Promoted | Dropped
-**Slug**: {slug}
-**Created**: {YYYY-MM-DD}
-
----
-
-## Problem
-
-> What pain or opportunity does this address? For whom?
-
-## Idea
-
-> One paragraph. What's the rough solution or approach?
-
-## How It Might Work
-
-> Optional rough sketch — not architecture, just enough to evaluate feasibility.
-
-| What | Where |
-|------|-------|
-| … | … |
-
-## Why Now
-
-> What makes this worth capturing? Urgency, dependencies, strategic fit.
-
-## Open Questions
-
-- [ ] …

package/docs/templates/TEMPLATE-NOTE.md

@@ -1,27 +0,0 @@
-# {Title}
-
-**Date**: {YYYY-MM-DD}
-**Context**: {What triggered this note — a question, comparison, research session, or discussion.}
-
----
-
-## Summary
-
-> 2–3 sentences. What was explored and what's the takeaway?
-
-## Findings
-
-> Main content. Structure freely — tables, sections, bullet lists, whatever fits the topic.
-
-## Decisions
-
-> Optional. Concrete decisions made during or after this session. Omit if the note is purely informational.
-
-- {Decision 1}
-- {Decision 2}
-
-## Open Questions
-
-> Optional. Unresolved items worth revisiting. Omit if none.
-
-- [ ] {Question 1}

package/docs/templates/TEMPLATE-ROADMAP.md

@@ -1,21 +0,0 @@
-# Roadmap: {Goal Title}
-
-**Goal**: [{goal-slug}](goal.md)
-**Last updated**: {YYYY-MM-DD}
-
-## Milestones
-
-### Milestone 1: {name}
-> {One-line description of what's testable after this milestone}
-
-| ID | Story | Slug | Depends on | Status |
-|----|-------|------|------------|--------|
-| M1.1 | {story title} | {feature-slug} | — | backlog |
-| M1.2 | {story title} | {feature-slug} | M1.1 | blocked |
-
-**Checkpoint:** {What the human should test after this milestone completes}
-
-## Dependency Graph
-
-{ASCII or text description of which stories block which. Can be as simple as
-"1 → 2 → 3, 1 → 4" for linear + parallel branches.}