pi-harness-runtime 1.1.184 → 1.1.186

package/CHANGELOG.md

@@ -2,6 +2,13 @@
 
 All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
 
+### [1.1.140](https://github.com/ManotLuijiu/pi-harness-runtime/compare/v1.1.184...v1.1.140) (2026-10-10)
+
+
+### Bug Fixes
+
+* **honcho:** implement proper MCP registration and truthful status ([844182d](https://github.com/ManotLuijiu/pi-harness-runtime/commit/844182df4822185204e6a43e94702afcf9fb1f5f)), closes [#1-10](https://github.com/ManotLuijiu/pi-harness-runtime/issues/1-10) [#12-14](https://github.com/ManotLuijiu/pi-harness-runtime/issues/12-14)
+
 ### [1.1.139](https://github.com/ManotLuijiu/pi-harness-runtime/compare/v1.1.150...v1.1.139) (2026-10-05)
 
 

package/RULES.md

@@ -0,0 +1,54 @@
+# Development Rules
+
+## Version Management
+
+### NPM Publishing via GitHub Actions + OIDC
+
+**GitHub Actions automatically publishes to npm when you push to `develop` branch.**
+
+- Uses **OpenID Connect (OIDC)** for secure npm authentication
+- No npm token stored in GitHub secrets
+- Each package is configured at: npmjs.com → Package → Settings → Trusted Publisher
+
+After every `git push` to `develop`:
+1. GitHub Actions detects the push
+2. Authenticates to npm via OIDC
+3. Runs build and tests
+4. Publishes to npm automatically
+
+You do NOT need to manually run `npm publish` or manage tokens.
+
+### Version Bump Process
+
+**Before pushing a version bump, check npm to use the correct next version:**
+
+```bash
+# 1. Check current npm version
+npm view pi-harness-runtime version
+# Example output: 1.1.184
+
+# 2. Update package.json to next version (npm + 1)
+sed -i 's/"version": "1.1.184"/"version": "1.1.185"/' package.json
+
+# 3. Commit and tag with SAME version
+git add -A && git commit -m "bump: version to 1.1.185"
+git tag v1.1.185
+git push origin develop --tags
+```
+
+**Important:**
+- Never reuse a version number already on npm
+- Use patch-level only (`1.1.x`) until production-ready
+- GitHub Actions reads the `tag` event to trigger npm publish
+
+### Why This Matters
+
+- If the tag already exists on npm, publish fails with: `You cannot publish over the previously published versions`
+- Using a new unique version ensures clean publish
+
+## Commit Messages
+
+Follow conventional commits:
+- `fix:` for bug fixes
+- `feat:` for new features
+- `chore:` for maintenance tasks

package/harness/glm-quota-countdown.ts

@@ -524,11 +524,19 @@ export class GLMQuotaCountdown {
 					: "1 minute";
 
 		try {
-			await this.notificationCenter.notify("QuotaPaused", {
+			const results = await this.notificationCenter.notify("QuotaPaused", {
 				jobId: this.jobContext?.jobId ?? jobId,
 				requirement: this.jobContext?.requirement ?? "GLM Quota",
 				error: `GLM quota reset in ${label} (${formatCountdown(remainingSeconds)}). Auto-resume pending.`,
 			});
+			// Log notification results for observability
+			for (const result of results) {
+				if (result.success) {
+					console.debug(`[notification] Sent ${result.channel} notification`);
+				} else {
+					console.warn(`[notification] Failed ${result.channel}: ${result.error}`);
+				}
+			}
 			logNotificationSent(jobId, remainingSeconds);
 		} catch (error) {
 			logNotificationFailed(jobId, String(error));