create-anpunkit 2.1.0 → 2.3.0

package/template/.cursor/commands/store-wisdom.md

@@ -1,191 +0,0 @@
-Caveman ULTRA mode. You are the ORCHESTRATOR.
-
-Purpose: share what this project learned with all future projects.
-Only resolved issues and completed research qualify. Open issues do NOT.
-
----
-
-## PRE-FLIGHT
-
-1. Read `.claude/kb-config.json`.
-   - Not found -> STOP. Tell me: "KB not configured. Run setup.sh to set up the
-     shared KB repo, then retry /store-wisdom."
-   - Found -> extract `kb_path` and `kb_remote`.
-
-2. Expand `kb_path` (resolve `~` to home directory).
-   Verify the path exists and is a git repo (`git -C <path> status`).
-   - Fails -> STOP. Tell me the path is broken and to re-run setup.sh.
-
----
-
-## STEP 1 — PULL LATEST KB
-
-Run: `git -C <kb_path> pull --ff-only`
-
-- Success -> continue.
-- Conflict or diverged -> STOP. Tell me:
-  "KB has a conflict. Resolve manually in <kb_path>, then retry /store-wisdom."
-- Offline (no network) -> WARN me, ask: "KB pull failed (offline?). Continue
-  with local KB copy, or abort?" Wait for answer.
-
----
-
-## STEP 2 — ANALYZE LOCAL PROJECT
-
-Scan this project for promotion candidates:
-
-### From docs/ISSUES.md — resolved issues only
-- Read all entries marked `- [x] resolved`.
-- Exclude: entries with no root cause filled in, entries without a solution.
-- For each qualifying entry, note: title, symptom, root cause, solution,
-  failed attempts.
-
-### From docs/research/ — completed research files
-- Read docs/research/INDEX.md. For each entry:
-  - Read the corresponding file.
-  - A research entry qualifies if: it documents an external service behavior,
-    API contract, SDK gotcha, architectural constraint, or cost finding that
-    would be useful in a different project.
-  - A research entry does NOT qualify if: it is a project-specific config
-    finding, a one-off trace with no generalizable conclusion, or a debug
-    trace (`debug-*.md`).
-- Note: research entries get a `created:` timestamp (today's date if not
-  already present in the file). Staleness is measured from this date.
-
-### Cross-check against KB
-- Read `<kb_path>/INDEX.md` (if it exists).
-- For each candidate: does a matching slug already exist in the KB?
-  - YES, fresh entry: skip (already in KB, not stale).
-  - YES, stale entry (marked [STALE] in the snapshot): flag as REWRITE candidate.
-  - NO: flag as NEW candidate.
-
----
-
-## STEP 3 — PROPOSE CANDIDATES
-
-Present candidates one at a time. For each:
-```
-
-[N of M] <type: NEW | REWRITE> — <slug>
-Domain: <inferred path, e.g. azure/auth.md or databricks/sdk.md>
-Tags: <tag1, tag2, tag3>
-Action: <“new entry” | “replaces stale entry from YYYY-MM-DD”>
-
-## Preview:
-
-## [<slug>]
-
-## created: <YYYY-MM-DD>
-tags: <tags>
-symptom/context: <…>
-root-cause / finding: <…>
-fix / recommendation: <…>
-
-[APPROVE / EDIT / SKIP]
-
-```
-- APPROVE: add to approved list.
-- EDIT: ask me for the edit, apply it, re-show, wait for APPROVE or SKIP.
-- SKIP: discard this candidate.
-
-After all candidates: show me the summary:
-```
-
-Approved: <N> entries
-Skipped: <M> entries
-Domains to write: <list>
-New domain folders to create: <list or “none”>
-Proceed? [yes / abort]
-
-```
-Wait for "yes" before writing anything.
-
----
-
-## STEP 4 — WRITE TO KB
-
-For each approved entry:
-
-1. Determine the domain file path: `<kb_path>/<domain>/<file>.md`
-   - If the directory does not exist: create it.
-   - If the file does not exist: create it with a `# <domain> — <file>` header.
-
-2. REWRITE candidates: find the existing `## [<slug>]` block in the file and
-   replace it entirely with the new entry.
-
-3. NEW candidates: append the entry to the end of the domain file.
-
-4. Update `<kb_path>/INDEX.md`:
-   - For NEW entries: append a line:
-     `YYYY-MM-DD | <domain>/<file> | <slug> | <one-sentence summary>`
-   - For REWRITE entries: update the existing line in-place (new date, same slug).
-
-5. If this is the first `/store-wisdom` run (no INDEX.md existed):
-   Also create `<kb_path>/KB_GUIDE.md` with the entry format reference:
-
-   ```markdown
-   # anpunkit-kb — guide
-
-   This repo accumulates resolved issues and research findings from anpunkit projects.
-   Populated by `/store-wisdom`. Read by the anpunkit `researcher` agent at session start.
-
-   ## Entry format — issues
-   ## [slug]
-   created: YYYY-MM-DD
-   tags: tag1, tag2
-   symptom: what was observed
-   root-cause: the real underlying cause
-   fix: exact solution
-   failed-attempts: what did not work
-
-   ## Entry format — research
-   ## [slug]
-   created: YYYY-MM-DD
-   tags: tag1, tag2
-   symptom/context: what prompted the research
-   finding: what was discovered
-   recommendation: what to do
-
-   ## INDEX.md format
-   YYYY-MM-DD | domain/file | slug | one-sentence summary
-
-   ## Staleness
-   Research entries older than 6 months are flagged [STALE] at session load.
-   Stale entries are re-researched locally and rewritten via /store-wisdom.
-   Issue entries never go stale.
-```
-
------
-
-## STEP 5 — COMMIT AND PUSH
-
-Run from `<kb_path>`:
-
-```bash
-git add -A
-git commit -m "store-wisdom: <N> entries from <project-name> (<YYYY-MM-DD>)"
-git push
-```
-
-- Push success -> tell me:
-  
-  ```
-  KB updated.
-  - entries written: <N> (<list of slugs>)
-  - domains touched: <list>
-  - new domains created: <list or "none">
-  - pushed to: <kb_remote>
-  ```
-- Push fails -> tell me the push failed, show the git error.
-  The entries ARE written locally — tell me to push manually:
-  `git -C <kb_path> push`
-
------
-
-## NOTES
-
-- `/store-wisdom` never modifies docs/ISSUES.md or docs/research/ in this project.
-  It reads them; it does not change them.
-- If there are no qualifying candidates, tell me so and stop. Do not push an empty commit.
-- The KB is append-only except for REWRITE of stale research entries.
-  Issue entries are never deleted or overwritten — they are facts.

package/template/.cursor/commands/synthesize.md

@@ -1,22 +0,0 @@
-Caveman ULTRA mode.
-
-Trigger: end of a phase, or any time STATE.md / ISSUES.md feel bloated.
-
-Dispatch the `synthesizer` subagent.
-
-For a normal phase: it rewrites STATE.md, dedups ISSUES.md, prunes snapshots,
-appends to HISTORY.md.
-
-For the FINAL phase (no further pending phases): also pass the signal
-"FINAL PHASE" so the synthesizer runs the extended pass — updating OVERVIEW.md
-and README.md to reflect the completed project state.
-
-To determine if this is the final phase: read docs/PLAN.md. If no phases remain
-with status "pending" after the current one, it is the final phase.
-
-When synthesizer returns "safe to /clear: yes", tell me:
-- before/after line counts
-- whether the final-pass ran
-- that I can now run /clear (or proceed to the endpoint summary if final phase)
-
-If it returns anything unsafe, show me what and stop.

package/template/.cursor/commands/unstuck.md

@@ -1,36 +0,0 @@
-Caveman ULTRA mode.
-
-Trigger: I chose "re-research" at a circuit breaker (see /phase step 5).
-
-Steps:
-
-1. WRITE IT DOWN. Append to docs/ISSUES.md as OPEN:
-```
-
-### <error title>
-
-- [ ] open - stuck after 3 attempts
-- symptom: <…>
-- attempts that FAILED: <hypothesis 1>, <2>, <3>
-
-```
-Reference the existing debug-<slug>.md.
-
-2. RESET FRAME. The 3 failed hypotheses are probably all wrong. Discard them.
-
-3. DEEP RESEARCH. Dispatch `researcher` in IMPL mode WIDE:
-- Read existing debug-<slug>.md and ISSUES.md failed-attempts FIRST.
-- Re-read the actual error from scratch.
-- Check real external service contract / docs.
-- Look one layer below: config? env? version? data shape?
-- Return fresh HYPOTHESIS backed by NEW evidence.
-
-4. RE-PLAN if needed. Research shows phase design was wrong -> dispatch planner.
-
-5. RESUME. Hand fresh hypothesis to `debugger`. It reads the prior debug file
-(already knows what's ruled out). Budget = 3, NEW hypotheses only.
-
-6. This counts as the path chosen at the first breaker. If STUCK again ->
-/phase step 5 SECOND STUCK. Do not loop further.
-
-Report each step.

package/template/.cursor/hooks.json

@@ -1,14 +0,0 @@
-{
-  "version": 1,
-  "hooks": {
-    "sessionStart": [
-      { "command": "bash .claude/hooks/cursor-session-start.sh" }
-    ],
-    "preCompact": [
-      { "command": "bash .claude/hooks/pre-compact.sh" }
-    ],
-    "subagentStop": [
-      { "command": "bash .claude/hooks/subagent-stop.sh" }
-    ]
-  }
-}

package/template/.cursor/rules/anpunkit.md

@@ -1,11 +0,0 @@
----
-description: anpunkit methodology — load on every session.
-alwaysApply: true
----
-
-# anpunkit
-
-Methodology, roles, procedures, rituals, and hard rules live in `@AGENTS.md`
-at the repo root. Read it and follow it for all work in this repository.
-
-@AGENTS.md

package/template/docker-compose.test.yml

@@ -1,34 +0,0 @@
-# docker-compose.test.yml — E2E test stack (local-docker mode).
-# TEMPLATE — adjust build contexts and ports for your project layout.
-services:
-  backend:
-    build:
-      context: ./backend          # <-- adjust
-    environment:
-      SQL_SERVER: ${E2E_SQL_SERVER}
-      SQL_DB: ${E2E_SQL_DB}
-      SQL_USER: ${E2E_SQL_USER}
-      SQL_PASSWORD: ${E2E_SQL_PASSWORD}
-      TENANT_ID: ${E2E_TENANT_ID}
-      CLIENT_ID: ${E2E_CLIENT_ID}
-      STORAGE_CONN: ${E2E_STORAGE_CONN:-}
-    ports:
-      - "8081:8081"
-    healthcheck:
-      test: ["CMD", "curl", "-fs", "http://localhost:8081/health"]
-      interval: 5s
-      timeout: 3s
-      retries: 12
-
-  webapp:
-    build:
-      context: ./frontend         # <-- adjust
-    environment:
-      API_BASE_URL: http://backend:8081
-      TENANT_ID: ${E2E_TENANT_ID}
-      CLIENT_ID: ${E2E_CLIENT_ID}
-    ports:
-      - "8080:80"
-    depends_on:
-      backend:
-        condition: service_healthy

package/template/e2e/global-setup.ts

@@ -1,57 +0,0 @@
-// e2e/global-setup.ts
-import { chromium } from '@playwright/test';
-import * as fs from 'fs';
-import * as path from 'path';
-
-const AUTH_DIR = path.join(__dirname, '.auth');
-const STATE = path.join(AUTH_DIR, 'state.json');
-
-async function fetchRopcToken() {
-  const tenant = reqEnv('E2E_TENANT_ID');
-  const body = new URLSearchParams({
-    grant_type: 'password',
-    client_id: reqEnv('E2E_CLIENT_ID'),
-    username: reqEnv('E2E_TEST_USER'),
-    password: reqEnv('E2E_TEST_PASSWORD'),
-    scope: `openid profile ${reqEnv('E2E_SCOPE')}`,
-  });
-  const url = `https://login.microsoftonline.com/${tenant}/oauth2/v2.0/token`;
-  const res = await fetch(url, {
-    method: 'POST',
-    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
-    body,
-  });
-  if (!res.ok) {
-    const txt = await res.text();
-    throw new Error(
-      `ROPC token fetch failed (${res.status}). ` +
-      `Check: ROPC enabled on app registration, test user exists, ` +
-      `MFA excluded via Conditional Access. Response: ${txt}`
-    );
-  }
-  return res.json() as Promise<{ access_token: string; id_token: string; expires_in: number }>;
-}
-
-function reqEnv(k: string): string {
-  const v = process.env[k];
-  if (!v) throw new Error(`Missing env ${k} — run /infra to regenerate .env.test`);
-  return v;
-}
-
-async function globalSetup() {
-  fs.mkdirSync(AUTH_DIR, { recursive: true });
-  const token = await fetchRopcToken();
-  const baseURL = reqEnv('E2E_BASE_URL');
-  const browser = await chromium.launch();
-  const page = await browser.newPage();
-  await page.goto(baseURL);
-  await page.evaluate((t) => {
-    localStorage.setItem('e2e.access_token', t.access_token);
-    localStorage.setItem('e2e.id_token', t.id_token);
-  }, token);
-  await page.context().storageState({ path: STATE });
-  await browser.close();
-  console.log('E2E auth ready — real Entra token injected, MFA UI bypassed.');
-}
-
-export default globalSetup;