npm - ultimate-pi - Versions diffs - 0.1.7 → 0.2.2 - Mend

ultimate-pi 0.1.7 → 0.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (524) hide show

package/.agents/skills/wiki/references/modes.md DELETED Viewed

@@ -1,259 +0,0 @@
-# Wiki Modes
-Six modes cover the most common use cases. Pick the one that fits, or combine them.
----
-## Mode A: Website / Sitemap
-Use when: "build a sitemap wiki for my website", "map content gaps", "SEO audit wiki"
-```
-vault/
-├── .raw/              # crawl exports, analytics, scraped pages, GSC data
-├── wiki/
-│   ├── pages/         # one note per URL: status, meta, content summary
-│   ├── structure/     # site architecture, nav hierarchy, internal link map
-│   ├── audits/        # content gaps, redirect needs, thin content flags
-│   ├── keywords/      # keyword clusters, target page assignments
-│   └── entities/      # brand, authors, topic hubs
-├── _meta/
-│   ├── index.md
-│   └── log.md
-└── WIKI.md
-```
-Frontmatter for `wiki/pages/` notes:
-```yaml
----
-type: page
-url: "https://example.com/page-slug"
-status: live          # live | redirect | 404 | stub | no-index
-title: ""
-h1: ""
-meta_description: ""
-word_count: 0
-has_schema: false
-indexed: true
-canonical: ""
-internal_links_in: 0
-internal_links_out: 0
-last_crawled: YYYY-MM-DD
-tags: [page]
-created: YYYY-MM-DD
-updated: YYYY-MM-DD
----
-```
-Key wiki pages to create: `[[Site Overview]]`, `[[Navigation Structure]]`, `[[Content Gaps]]`, `[[Redirect Map]]`, `[[Keyword Clusters]]`
----
-## Mode B: GitHub / Repository
-Use when: "map my codebase", "architecture wiki for my repo", "understand this project"
-```
-vault/
-├── .raw/              # README, git log exports, code dumps, issue exports
-├── wiki/
-│   ├── modules/       # one note per major module / package / service
-│   ├── components/    # reusable UI or functional components
-│   ├── decisions/     # Architecture Decision Records (ADRs)
-│   ├── dependencies/  # external deps, versions, risk assessment
-│   └── flows/         # data flows, request paths, auth flows
-├── _meta/
-│   ├── index.md
-│   └── log.md
-└── WIKI.md
-```
-Frontmatter for `wiki/modules/` notes:
-```yaml
----
-type: module           # module | component | decision | dependency | flow
-path: "src/auth/"
-status: active         # active | deprecated | experimental | planned
-language: typescript
-purpose: ""
-maintainer: ""
-last_updated: YYYY-MM-DD
-linked_issues: []
-depends_on: []
-used_by: []
-tags: [module]
-created: YYYY-MM-DD
-updated: YYYY-MM-DD
----
-```
-Key wiki pages to create: `[[Architecture Overview]]`, `[[Data Flow]]`, `[[Tech Stack]]`, `[[Dependency Graph]]`, `[[Key Decisions]]`
----
-## Mode C: Business / Project
-Use when: "project wiki", "competitive intelligence", "team knowledge base", "meeting notes"
-```
-vault/
-├── .raw/              # meeting transcripts, Slack exports, docs, emails
-├── wiki/
-│   ├── stakeholders/  # people, companies, decision-makers
-│   ├── decisions/     # key decisions with rationale and date
-│   ├── deliverables/  # milestones, outputs, status tracking
-│   ├── intel/         # competitor analysis, market research
-│   └── comms/         # synthesized meeting notes, key threads
-├── _meta/
-│   ├── index.md
-│   └── log.md
-└── WIKI.md
-```
-Frontmatter for `wiki/decisions/` notes:
-```yaml
----
-type: decision         # stakeholder | decision | deliverable | intel | meeting | competitor
-status: active         # active | pending | done | blocked | superseded
-priority: 3            # 1 (highest) to 5 (lowest)
-date: YYYY-MM-DD
-owner: ""
-due_date: ""
-context: ""
-tags: [decision]
-created: YYYY-MM-DD
-updated: YYYY-MM-DD
----
-```
-Key wiki pages to create: `[[Project Overview]]`, `[[Stakeholder Map]]`, `[[Decision Log]]`, `[[Competitor Landscape]]`
----
-## Mode D: Personal / Second Brain
-Use when: "personal second brain", "track my goals", "journal synthesis", "life wiki"
-```
-vault/
-├── .raw/              # journal entries, articles, podcast notes, voice transcripts
-├── wiki/
-│   ├── goals/         # personal and professional goals with progress tracking
-│   ├── learning/      # concepts being mastered, skill development
-│   ├── people/        # relationships, shared context, follow-ups
-│   ├── areas/         # life areas: health, finances, career, creative
-│   └── resources/     # books, courses, tools worth referencing
-├── _meta/
-│   ├── index.md
-│   ├── log.md
-│   └── hot-cache.md   # ~500-word summary of most active context
-└── WIKI.md
-```
-Frontmatter for `wiki/goals/` notes:
-```yaml
----
-type: goal             # goal | concept | person | area | resource | reflection
-status: active         # active | paused | completed | abandoned
-area: career           # health | career | finance | creative | relationships | growth
-priority: 1
-target_date: YYYY-MM-DD
-progress: 0            # 0-100 percent
-tags: [goal]
-created: YYYY-MM-DD
-updated: YYYY-MM-DD
----
-```
-Hot cache note: `_meta/hot-cache.md` is a ~500-word file pi updates at the end of each session. It captures current focus areas, recent wins, and open threads. This prevents pi from having to crawl the whole wiki to answer "where were we?".
-Key wiki pages to create: `[[North Star]]`, `[[Weekly Review Template]]`, `[[Annual Goals]]`
----
-## Mode E: Research
-Use when: "research wiki on [topic]", "track papers I'm reading", "build a thesis"
-```
-vault/
-├── .raw/              # PDFs, web clips, data files, raw notes
-├── wiki/
-│   ├── papers/        # paper summaries with key claims and methodology
-│   ├── concepts/      # extracted concepts, models, frameworks
-│   ├── entities/      # people, organizations, methods, datasets
-│   ├── thesis/        # evolving synthesis: the "state of the field" pages
-│   └── gaps/          # open questions, contradictions, research needed
-├── _meta/
-│   ├── index.md
-│   └── log.md
-└── WIKI.md
-```
-Frontmatter for `wiki/papers/` notes:
-```yaml
----
-type: paper            # paper | concept | entity | thesis | gap
-status: summarized     # raw | summarized | synthesized | superseded
-year: 2024
-authors: []
-venue: ""
-key_claim: ""
-methodology: ""
-contradicts: []
-supports: []
-tags: [paper]
-created: YYYY-MM-DD
-updated: YYYY-MM-DD
----
-```
-Key wiki pages to create: `[[Research Overview]]`, `[[Key Claims Map]]`, `[[Open Questions]]`, `[[Methodology Comparison]]`
----
-## Mode F: Book / Course
-Use when: "companion wiki for a book", "course notes wiki", "as I read [title]"
-```
-vault/
-├── .raw/              # chapter notes, highlights, exercises
-├── wiki/
-│   ├── characters/    # characters, personas, agents, experts (adapt to content)
-│   ├── themes/        # major themes with supporting evidence
-│   ├── concepts/      # domain-specific terms and frameworks
-│   ├── timeline/      # plot structure, curriculum sequence, chapter map
-│   └── synthesis/     # your own takeaways, questions, applications
-├── _meta/
-│   ├── index.md
-│   └── log.md
-└── WIKI.md
-```
-Frontmatter for `wiki/concepts/` notes:
-```yaml
----
-type: concept          # concept | character | theme | chapter | synthesis
-status: developing     # stub | developing | mature
-source_chapters: []
-first_appearance: ""
-tags: [concept]
-created: YYYY-MM-DD
-updated: YYYY-MM-DD
----
-```
-Key wiki pages to create: `[[Book Overview]]`, `[[Theme Map]]`, `[[Character / Expert Index]]`, `[[My Takeaways]]`
----
-## Combining Modes
-You can combine modes. Examples:
-- "GitHub repo + research on the AI approach used" -> Mode B folders + Mode E papers/ folder
-- "My SaaS business + second brain" -> Mode C intel/ + Mode D goals/
-- "YouTube channel" -> Mode F (content as "book") + Mode E (research on topics covered)
-When combining, keep folder names distinct. Don't merge `decisions/` from Mode B and Mode C into one folder.

package/.agents/skills/wiki/references/plugins.md DELETED Viewed

@@ -1,96 +0,0 @@
-# Obsidian Setup
----
-## Install Obsidian
-### Linux (Flatpak: recommended)
-Check if installed:
-```bash
-flatpak list 2>/dev/null | grep -i obsidian && echo "FOUND via flatpak" || \
-which obsidian 2>/dev/null && echo "FOUND in PATH" || echo "NOT FOUND"
-```
-Install if not found:
-```bash
-flatpak install flathub md.obsidian.Obsidian
-```
-### macOS
-```bash
-ls /Applications/Obsidian.app 2>/dev/null && echo "FOUND" || brew install --cask obsidian
-```
-### Windows
-```powershell
-Test-Path "$env:LOCALAPPDATA\Obsidian" && echo "FOUND" || winget install Obsidian.Obsidian
-```
-### All platforms: direct download
-https://obsidian.md/download
----
-## Open the Vault
-After installing: Obsidian > Manage Vaults > Open Folder as Vault > select your vault directory.
----
-## Core Plugins (Built-in: No Install Required)
-These ship with Obsidian. Enable them in Settings > Core Plugins:
-| Plugin | Purpose |
-|--------|---------|
-| **Bases** | Native database-like views for `.base` files. Powers `wiki/meta/dashboard.base`. Available since Obsidian v1.9.10 (August 2025). **Replaces Dataview for most wiki use cases.** |
-| **Properties** | Visual frontmatter editor. Always enabled. |
-| **Backlinks** | Outgoing/incoming links pane. |
-| **Outline** | Document heading navigation. |
-## Recommended Community Plugins
-Install via Settings > Community Plugins > Turn off Restricted Mode > Browse.
-| Plugin | Purpose |
-|--------|---------|
-| **Templater** | Auto-populate frontmatter on note creation from `_templates/`. |
-| **Obsidian Git** | Auto-commit every 15 minutes. Protects against bad writes. |
-| **Calendar** | Right-sidebar calendar with word count, task, and link indicators. Pre-installed in this vault via `.obsidian/plugins/calendar/`. |
-| **Thino** | Quick memo capture panel in right sidebar. Pre-installed via `.obsidian/plugins/thino/`. |
-| **Iconize** | Visual folder icons for navigation. |
-| **Minimal Theme** | Best dark theme for dense information display. |
-| **Dataview** *(optional/legacy)* | Only needed if you're on Obsidian < 1.9.10 or want to use the legacy `dashboard.md` queries. The primary dashboard now uses Bases. |
-**Calendar and Thino are pre-installed**. They ship with this vault. Enable them in Settings → Community Plugins → toggle on. No download needed.
-If installing in a different vault: download `main.js` + `manifest.json` from their GitHub releases into `.obsidian/plugins/calendar/` and `.obsidian/plugins/thino/` respectively.
-Optional additions:
-- **Smart Connections**: semantic search across all notes
-- **QuickAdd**: macros for fast note creation
-- **Folder Notes**: click a folder to open an overview note
----
-## Web Clipper
-The Obsidian Web Clipper browser extension converts web articles to markdown and sends them to `.raw/` in one click.
-Install for Chrome, Firefox, or Safari from the Obsidian website.
-Set the default folder to `.raw/` in the extension settings.
----
-## After Installing Plugins
-1. Enable Bases: Settings > Core Plugins > toggle on (already on by default in Obsidian v1.9.10+)
-2. Enable Templater: Settings > Templater > set template folder to `_templates`
-3. Enable Obsidian Git: Settings > Obsidian Git > Auto backup interval: 15 minutes
-4. Enable the CSS snippet: Settings > Appearance > CSS Snippets > toggle on `vault-colors`
-5. *(Optional)* Enable Dataview only if you want the legacy `wiki/meta/dashboard.md` queries to work alongside the primary `dashboard.base`

package/.agents/skills/wiki/references/rest-api.md DELETED Viewed

@@ -1,124 +0,0 @@
-# REST API Quick Reference
-Use these commands when MCP tools are not available. Requires the Local REST API plugin running in Obsidian (port 27124).
-Set your key before running any command:
-```bash
-API="https://127.0.0.1:27124"
-KEY="your-api-key-here"
-```
----
-## Read a file
-```bash
-curl -sk \
-  -H "Authorization: Bearer $KEY" \
-  "$API/vault/wiki/index.md"
-```
----
-## Create or replace a file
-```bash
-curl -sk -X PUT \
-  -H "Authorization: Bearer $KEY" \
-  -H "Content-Type: text/markdown" \
-  --data-binary @local-file.md \
-  "$API/vault/wiki/entities/Name.md"
-```
-Or with inline content:
-```bash
-curl -sk -X PUT \
-  -H "Authorization: Bearer $KEY" \
-  -H "Content-Type: text/markdown" \
-  --data "# Page Title
-Content here." \
-  "$API/vault/wiki/concepts/Name.md"
-```
----
-## Append to a file
-```bash
-curl -sk -X POST \
-  -H "Authorization: Bearer $KEY" \
-  -H "Content-Type: text/markdown" \
-  --data "- New log entry" \
-  "$API/vault/wiki/log.md"
-```
----
-## Patch a frontmatter field
-```bash
-curl -sk -X PATCH \
-  -H "Authorization: Bearer $KEY" \
-  -H "Operation: replace" \
-  -H "Target-Type: frontmatter" \
-  -H "Target: status" \
-  -H "Content-Type: application/json" \
-  --data '"mature"' \
-  "$API/vault/wiki/concepts/Name.md"
-```
----
-## Append content under a heading
-```bash
-curl -sk -X PATCH \
-  -H "Authorization: Bearer $KEY" \
-  -H "Operation: append" \
-  -H "Target-Type: heading" \
-  -H "Target: Connections" \
-  -H "Content-Type: text/markdown" \
-  --data "- [[New Page]]" \
-  "$API/vault/wiki/entities/Name.md"
-```
----
-## Search
-Simple keyword search:
-```bash
-curl -sk -X POST \
-  -H "Authorization: Bearer $KEY" \
-  "$API/search/simple/?query=machine+learning"
-```
-Dataview query:
-```bash
-curl -sk -X POST \
-  -H "Authorization: Bearer $KEY" \
-  -H "Content-Type: application/vnd.olrapi.dataview.dql+txt" \
-  --data 'TABLE status FROM "wiki" WHERE status = "seed"' \
-  "$API/search/"
-```
----
-## List all tags
-```bash
-curl -sk \
-  -H "Authorization: Bearer $KEY" \
-  "$API/tags/"
-```
----
-## List files in a folder
-```bash
-curl -sk \
-  -H "Authorization: Bearer $KEY" \
-  "$API/vault/wiki/entities/"
-```

package/.agents/skills/wiki-fold/SKILL.md DELETED Viewed

@@ -1,204 +0,0 @@
----
-name: wiki-fold
-description: "Rollup of wiki log entries into meta-pages. Reads the last 2^k entries from wiki/log.md, writes a structurally-idempotent fold page to wiki/folds/ that links back to children. Extractive summarization (no invention). Dry-run by default, stdout-only; commit mode writes and accepts that the PostToolUse hook auto-commits. Triggers on: fold the log, run a fold, run wiki-fold, log rollup, roll up log entries."
----
-# wiki-fold: Extractive Log Rollup
-Implements a bounded subset of Mechanism 1 from [[DragonScale Memory]]: flat fold over raw `wiki/log.md` entries. Fold-of-folds (hierarchical level-stacking) is **out of scope for this skill**; see "Scope boundary" below.
-A fold is **additive**: child log entries and their referenced pages are never modified, moved, or deleted. A fold is **extractive**: every outcome and theme in the output must be traceable to a specific child log entry. No invented facts, no synthesis beyond what the child entries support.
----
-## Wiki Path Resolution
-All `wiki/` paths in this skill are relative to the wiki directory inside the Obsidian vault. Resolve before any file operation:
-```bash
-WIKI_PATH="${VAULT_WIKI_PATH:-vault/wiki}"
-```
-Use `$WIKI_PATH/` as the prefix for all `wiki/...` file paths. Example: `wiki/log.md` → `$WIKI_PATH/log.md` (default: `vault/wiki/log.md`).
----
-## Scope boundary (explicit)
-This skill does **not** implement:
-- Fold-of-folds / hierarchical level stacking (DragonScale spec calls for it; deferred to a future skill).
-- Automatic triggering (folds are always human-invoked in Phase 1).
-- Semantic-tiling dedup (Mechanism 3; separate skill).
-It **does** implement:
-- Flat fold over raw log.md entries at a chosen batch exponent `k`.
-- Structural idempotency via a deterministic fold ID.
-- Extractive summarization with count-checking.
-When referring to level in frontmatter, use `batch_exponent: k` (not `level: k`), because this skill does not produce hierarchical levels.
----
-## Modes
-| Mode | Writes? | Invocation |
-|---|---|---|
-| **dry-run (default)** | **No Write tool calls.** Emit fold content via Bash `cat`/`heredoc` to stdout only. | `fold the log, dry-run k=3` |
-| **commit** | Uses Write/Edit tools. Each Write fires the repo PostToolUse hook which auto-commits wiki changes. Accept this. Compose full content first, then sequence writes. | `fold the log, commit k=3` (only after a clean dry-run) |
-**Why stdout-only in dry-run**: the repo's `hooks/hooks.json` PostToolUse hook fires on any `Write|Edit` and runs `git add wiki/ .raw/`. Writing to `/tmp` does not stage /tmp, but it still triggers the hook, which will commit *any pending wiki changes* under a generic message. Dry-run must leave zero residue. Bash stdout does not fire the hook.
----
-## Deterministic fold ID
-Every fold has an ID derived from its inputs:
-```
-fold-k{K}-from-{EARLIEST-DATE}-to-{LATEST-DATE}-n{COUNT}
-```
-Example: `fold-k3-from-2026-04-10-to-2026-04-23-n8`.
-The filename in commit mode is `$WIKI_PATH/folds/{FOLD-ID}.md`. No date-of-creation in the filename. No timestamp in the title.
-**Duplicate detection (required)**: before emitting any output, check if `$WIKI_PATH/folds/{FOLD-ID}.md` already exists. If so, report "Fold already exists at $WIKI_PATH/folds/{FOLD-ID}.md. Use --force to overwrite, or pick a different range." and stop. This is the no-op idempotency guarantee; byte-identical content is NOT guaranteed (LLM prose varies) but the filename and scope are.
----
-## Parameters
-- `k` (default 4): batch exponent. Batch size = `2^k`. Typical values: k=3 (8), k=4 (16), k=5 (32).
-- `range` (optional): explicit entry range `entries 1-16`. Overrides k.
-- `--force`: overwrite an existing fold with the same ID. Default no.
-- `--commit`: write to wiki/. Without it, dry-run stdout-only.
-If fewer than `2^k` log entries exist, report the shortfall and stop. Do not silently fold a partial batch.
----
-## Procedure
-### 1. Parse log entries
-```
-grep -n "^## \[" "$WIKI_PATH/log.md" | head -{2^k}
-```
-Record for each entry: line number, date, operation, title, and the following bullet lines until the next `## [` or end-of-section.
-### 2. Extract child page identifiers
-From each entry's bullet list, extract:
-- `Location: wiki/path/to/page.md` (the primary page)
-- `[[Wikilinks]]` inline
-- `Pages created:` and `Pages updated:` lists
-Build a structured children list:
-```yaml
-children:
-  - date: "2026-04-23"
-    op: "wiki-save"
-    title: "DragonScale Memory v0.2 — post-adversarial-review"
-    page: "[[DragonScale Memory]]"
-  - ...
-```
-One record per log entry. Do not dedupe by page: if two entries both point to `[[DragonScale Memory]]`, both records appear, distinguishable by date and title.
-### 3. Read referenced pages (bounded)
-Read only the pages that are not already captured fully in the log entry's bullets. Budget: 0-10 page reads. Hard ceiling: 15. If an entry's referenced page is missing, record `page_missing: true` and proceed.
-### 4. Extractive summarization with count checks
-Write the fold body per `references/fold-template.md`. **Rules**:
-- **Extractive only.** Every outcome bullet and theme bullet must cite a specific child entry (e.g., `(from 2026-04-14 session)`) or a quoted line from that entry. Do not introduce events, counts, or interpretations not present in a child entry.
-- **Log entry is the primary source.** If the log entry's bullets and the referenced meta-page disagree on a fact (e.g., a count), prefer the log-entry bullets and flag the mismatch as "source mismatch: log says X, meta says Y."
-- **Count checks.** If you write "N concept pages" or "M repos updated," grep the source entries for the number and verify. Numeric mismatches are dry-run blockers.
-- **No merging across entries without naming them.** A theme that spans multiple entries must name each contributing entry inline.
-- **Uncertainty is a feature.** If an entry is ambiguous, say "ambiguous in source: [[Entry]]" rather than picking one interpretation.
-### 5. Self-check before emitting
-Before printing output, verify:
-- Every child in `children:` frontmatter appears exactly once in the Child Entries table.
-- Every entry in the table appears in the `children:` frontmatter.
-- Every numeric claim in Key Outcomes is grep-verifiable against a child entry.
-- The fold ID is deterministic and the file does not already exist (or `--force` is set).
-If any check fails, abort and report the specific failure.
-### 6. Emit
-**Dry-run**: use Bash `cat <<'EOF' ... EOF` to stdout. Do not use Write. Print the fold ID and a one-line summary of what the commit step would do.
-**Commit** (only after user says "commit the fold"):
-1. `Write` the fold page to `$WIKI_PATH/folds/{FOLD-ID}.md`. (PostToolUse hook will auto-commit this.)
-2. `Edit` `$WIKI_PATH/index.md` to add the fold link under a `## Folds` section (create section if missing). (Hook auto-commits.)
-3. `Edit` `$WIKI_PATH/log.md` to prepend one entry:
-   ```
-   ## [YYYY-MM-DD] fold | batch-exponent-k{K} rollup of N entries
-   - Location: $WIKI_PATH/folds/{FOLD-ID}.md
-   - Range: {EARLIEST-DATE} to {LATEST-DATE}
-   - Children: N log entries
-   ```
-   (Hook auto-commits.)
-Three auto-commits result. The user sees three separate `wiki: auto-commit` entries in git log. This is expected; do not attempt to suppress the hook.
----
-## Output schema
-See `references/fold-template.md` for the canonical frontmatter and body layout.
----
-## Invariants
-1. **Structural idempotency**: same range + same k → same fold ID → duplicate detection prevents double-writes. LLM prose may vary across runs; the *location and scope* are fixed.
-2. **Additive**: children are never modified.
-3. **Bounded reads**: 0-15 child-page reads per fold.
-4. **Extractive**: zero invented facts. Count checks enforced.
-5. **No chaining**: wiki-fold does not invoke wiki-lint, wiki-ingest, wiki-autoresearch, or wiki-save.
----
-## What NOT to do
-- Do not use Write/Edit during dry-run. Bash stdout only.
-- Do not include the current date in the fold filename or title. Use the child entry range.
-- Do not silently dedupe children by page title. One record per log entry.
-- Do not write "emergent themes" that span entries without naming which entries contribute.
-- Do not claim byte-identical idempotency. Structural idempotency is the actual guarantee.
-- Do not suppress or bypass the PostToolUse auto-commit hook.
-- Do not update `$WIKI_PATH/hot.md`. Ownership stays with wiki-save/ingest skills.
----
-## Reversal
-Committed fold reversal (three commits, land in this order):
-1. Remove the log.md fold entry.
-2. Remove the index.md entry.
-3. Delete the fold page file.
-Or: `git revert` the three auto-commits. Child pages are untouched in either path.
----
-## Example dry-run sequence
-User: "fold the log, dry-run k=3"
-1. Parse `$WIKI_PATH/log.md` top 8 entries.
-2. Build structured children list (8 records).
-3. Read 0-10 referenced pages as needed.
-4. Produce fold ID: `fold-k3-from-2026-04-10-to-2026-04-23-n8`.
-5. Check `$WIKI_PATH/folds/fold-k3-from-2026-04-10-to-2026-04-23-n8.md` does not exist.
-6. Write fold body following the template.
-7. Run self-check (frontmatter/table consistency, count verification).
-8. Emit via `cat <<'EOF' ... EOF` to stdout.
-9. Report: "Dry-run complete. Fold ID: {FOLD-ID}. To commit: 'commit the fold'."