@redaksjon/protokoll 0.4.3 → 1.0.1

package/docs/mcp-tools/get-version.md

@@ -0,0 +1,57 @@
+# protokoll_get_version
+
+Get the current version of Protokoll including git information and system details.
+
+## Purpose
+
+This tool is useful for diagnosing if you are using the latest version of Protokoll. It returns detailed version information including:
+- Package version
+- Git branch and commit
+- Git commit date
+- System platform, architecture, and Node.js version
+
+## Parameters
+
+None required.
+
+## Returns
+
+```typescript
+{
+  version: string;        // Full version string with git and system info
+  programName: string;    // "protokoll"
+  fullVersion: string;    // "protokoll <version>"
+}
+```
+
+## Example Output
+
+```json
+{
+  "version": "1.0.1-dev.0 (working/de9eb6d  2026-01-27 10:55:39 -0800) darwin arm64 v24.8.0",
+  "programName": "protokoll",
+  "fullVersion": "protokoll 1.0.1-dev.0 (working/de9eb6d  2026-01-27 10:55:39 -0800) darwin arm64 v24.8.0"
+}
+```
+
+## Usage
+
+Call this tool whenever you need to verify which version of Protokoll is running, especially when:
+- Troubleshooting issues
+- Verifying you have the latest changes
+- Reporting bugs
+- Checking if a feature is available in your version
+
+## Version String Format
+
+The version string follows this format:
+```
+<package-version> (<git-branch>/<git-commit> <commit-date>) <platform> <arch> <node-version>
+```
+
+Example breakdown:
+- `1.0.1-dev.0` - Package version from package.json
+- `working/de9eb6d` - Git branch and short commit hash
+- `2026-01-27 10:55:39 -0800` - Commit timestamp with timezone
+- `darwin arm64` - Operating system and architecture
+- `v24.8.0` - Node.js version

package/guide/index.md

@@ -190,6 +190,12 @@ export OPENAI_API_KEY="sk-..."
 export ANTHROPIC_API_KEY="sk-ant-..."
 ```
 
+### System Requirements
+
+- **Node.js 18+** and **npm 9+**
+- **ffmpeg** for audio format conversion (install with `brew install ffmpeg`, `apt-get install ffmpeg`, or from [ffmpeg.org](https://ffmpeg.org))
+- **OpenAI API key** (required for transcription)
+
 ## For AI Assistants
 
 If you're an AI helping someone use Protokoll:

package/guide/quickstart.md

@@ -6,10 +6,26 @@ Get Protokoll working in 5 minutes.
 
 - Node.js 18+
 - npm 9+
+- ffmpeg (for audio format conversion)
 - OpenAI API key
 
 ## Installation
 
+### 1. Install ffmpeg
+
+```bash
+# macOS
+brew install ffmpeg
+
+# Ubuntu/Debian
+sudo apt-get install ffmpeg
+
+# Windows
+# Download from https://ffmpeg.org/download.html
+```
+
+### 2. Install Protokoll
+
 ```bash
 npm install -g @redaksjon/protokoll
 ```
@@ -34,7 +50,16 @@ export OPENAI_API_KEY='sk-...'
 export ANTHROPIC_API_KEY='sk-ant-...'
 ```
 
-### 2. Create Config (optional)
+### 2. Verify ffmpeg Installation
+
+```bash
+ffmpeg -version
+# Should show version info
+```
+
+If you see "command not found", make sure ffmpeg is installed and in your PATH.
+
+### 3. Create Config (optional)
 
 ```bash
 mkdir -p ~/.protokoll

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@redaksjon/protokoll",
-  "version": "0.4.3",
+  "version": "1.0.1",
   "description": "Focused audio transcription with intelligent context integration",
   "main": "dist/main.js",
   "type": "module",
@@ -22,7 +22,7 @@
     "lint": "eslint . --ext .ts",
     "lint:fix": "eslint . --ext .ts --fix",
     "clean": "rm -rf dist",
-    "precommit": "npm run lint && npm run test && npm run mcp:test",
+    "precommit": "npm run lint && npm run build && npm run test && npm run mcp:test",
     "prepublishOnly": "npm run clean && npm run build",
     "mcp:build": "npm run build && echo 'MCP server built'",
     "mcp:inspect": "npm run build && npx @modelcontextprotocol/inspector dist/mcp/server.js",
@@ -45,9 +45,11 @@
     "@anthropic-ai/sdk": "^0.71.2",
     "@google/generative-ai": "^0.24.1",
     "@modelcontextprotocol/sdk": "^1.25.2",
+    "@redaksjon/context": "^0.0.3",
     "@riotprompt/riotprompt": "^0.0.21",
     "@theunwalked/cardigantime": "^0.0.22",
     "@theunwalked/dreadcabinet": "^0.0.15",
+    "@theunwalked/overcontext": "^0.0.3",
     "@types/fluent-ffmpeg": "^2.1.28",
     "cli-table3": "^0.6.5",
     "commander": "^14.0.2",

package/summary/2026/4/completion.json

@@ -0,0 +1,16 @@
+{
+  "choices": [
+    {
+      "message": {
+        "content": "**Weekly Summary: Week 4, 2026**\n\n**Overview:**  \nThis week focused on resolving technical issues within the project, particularly related to model configurations and documentation updates. Significant progress was made in bug fixes and enhancing the build process.\n\n**Key Accomplishments:**  \n- Resolved a critical bug concerning the model default configuration in the kronologi system.\n- Ensured built files have the correct executable permissions.\n- Updated and clarified documentation regarding the configuration hierarchy, improving overall project clarity.\n\n**Progress:**  \n- Initiated testing of the newly implemented weekly summary functionality, with early results showing promise.\n- Made advancements in verifying improvements to the build process, contributing to more efficient workflows.\n\n**Decisions:**  \n- It was decided to prioritize the testing of the weekly summary feature to ensure its reliability before further rollout.\n\n**Challenges:**  \n- No significant blockers were reported this week; however, ongoing testing may reveal unforeseen issues that will need to be addressed.\n\n**Next Steps:**  \n- Complete testing of the weekly summary functionality and gather feedback for any necessary adjustments.\n- Finalize verification of the build process improvements and implement any outstanding changes identified during testing.\n- Continue monitoring for potential issues during the implementation of updates. \n\nThis summary encapsulates the key activities and progress made during the week and sets the stage for continued advancements in the upcoming week."
+      },
+      "finish_reason": "stop"
+    }
+  ],
+  "usage": {
+    "prompt_tokens": 331,
+    "completion_tokens": 269,
+    "total_tokens": 600
+  },
+  "model": "gpt-4o-mini"
+}

package/summary/2026/4/inputs.json

@@ -0,0 +1,60 @@
+{
+  "config": {
+    "model": "gpt-4o-mini",
+    "temperature": 0.7,
+    "maxCompletionTokens": 4000,
+    "parameters": {
+      "year": {
+        "type": "number",
+        "description": "Year for the summary",
+        "required": true
+      },
+      "month": {
+        "type": "number",
+        "description": "Month number (1-12) - used as week identifier for weekly summaries",
+        "required": true
+      }
+    },
+    "context": {},
+    "content": {
+      "activity": {
+        "type": "activity",
+        "name": "Weekly Activity",
+        "directory": "",
+        "pattern": "*.md"
+      }
+    },
+    "output": {
+      "summary": {
+        "type": "summary",
+        "format": "markdown",
+        "name": "Weekly Summary",
+        "pattern": "summary.md"
+      },
+      "completion": {
+        "type": "metadata",
+        "format": "json",
+        "pattern": "completion.json"
+      },
+      "inputs": {
+        "type": "metadata",
+        "format": "json",
+        "pattern": "inputs.json"
+      }
+    },
+    "name": "weekly-summary"
+  },
+  "request": {
+    "model": "gpt-4o-mini",
+    "messages": [
+      {
+        "role": "system",
+        "content": "<Weekly Summary Persona>\nYou are a professional technical writer who creates concise, informative weekly summaries.\n\nYour summaries:\n\n- Highlight key accomplishments and progress\n- Identify important decisions and changes\n- Note blockers or challenges\n- Are written in clear, professional language\n- Focus on what matters most to stakeholders\n</Weekly Summary Persona>"
+      },
+      {
+        "role": "user",
+        "content": "<Context>\n\n</Context>\n\n<Weekly Summary Instructions>\nCreate a comprehensive weekly summary based on the provided activity files.\n\n<Structure>\n- **Overview**: Brief summary of the week's focus and major themes\n- **Key Accomplishments**: What was completed or achieved\n- **Progress**: Work that advanced significantly\n- **Decisions**: Important decisions made\n- **Challenges**: Blockers or issues encountered\n- **Next Steps**: Planned work for the coming week\n</Structure>\n\n<Guidelines>\n- Be concise but informative\n- Use bullet points for easy scanning\n- Highlight the most important items\n- Include relevant context for decisions\n- Note any risks or concerns\n- Keep the tone professional and factual\n</Guidelines>\n</Weekly Summary Instructions>\n\n<Content>\n<Weekly Activity Content>\n<activity/2026/4/test-activity.md>\n# Test Activity for Week 4, 2026\n\n## Completed Tasks\n- Fixed model default configuration bug in kronologi\n- Added executable permissions to built files\n- Updated documentation for configuration hierarchy\n\n## In Progress\n- Testing weekly summary functionality\n- Verifying build process improvements\n\n</activity/2026/4/test-activity.md>\n</Weekly Activity Content>\n</Content>"
+      }
+    ]
+  }
+}

package/summary/2026/4/summary.md

@@ -0,0 +1,26 @@
+**Weekly Summary: Week 4, 2026**
+
+**Overview:**  
+This week focused on resolving technical issues within the project, particularly related to model configurations and documentation updates. Significant progress was made in bug fixes and enhancing the build process.
+
+**Key Accomplishments:**  
+- Resolved a critical bug concerning the model default configuration in the kronologi system.
+- Ensured built files have the correct executable permissions.
+- Updated and clarified documentation regarding the configuration hierarchy, improving overall project clarity.
+
+**Progress:**  
+- Initiated testing of the newly implemented weekly summary functionality, with early results showing promise.
+- Made advancements in verifying improvements to the build process, contributing to more efficient workflows.
+
+**Decisions:**  
+- It was decided to prioritize the testing of the weekly summary feature to ensure its reliability before further rollout.
+
+**Challenges:**  
+- No significant blockers were reported this week; however, ongoing testing may reveal unforeseen issues that will need to be addressed.
+
+**Next Steps:**  
+- Complete testing of the weekly summary functionality and gather feedback for any necessary adjustments.
+- Finalize verification of the build process improvements and implement any outstanding changes identified during testing.
+- Continue monitoring for potential issues during the implementation of updates. 
+
+This summary encapsulates the key activities and progress made during the week and sets the stage for continued advancements in the upcoming week.