@gavin-hu/my-pi-agent 0.17.0 → 0.19.0

package/extensions/plan/config.ts

@@ -1,27 +0,0 @@
-/**
- * Config-file support for plan mode.
- *
- * The `plan` section of the shared `bytefly.json` (global then project, project
- * wins). Only the approval offer is configurable; plan mode itself never depends
- * on it.
- */
-
-import { loadConfigSection } from "../../lib/config.ts";
-
-export interface PlanConfig {
-	/** Ask before recording an approved plan's objective as the session goal. */
-	goalPrompt: boolean;
-}
-
-export const DEFAULT_CONFIG: PlanConfig = { goalPrompt: true };
-
-/** Normalize one merged config object over the running base. */
-export function normalizeConfig(raw: Record<string, unknown> | undefined, base: PlanConfig): PlanConfig {
-	if (!raw) return base;
-	return { goalPrompt: typeof raw.goalPrompt === "boolean" ? raw.goalPrompt : base.goalPrompt };
-}
-
-/** Effective plan config from the shared `plan` section (defaults, global, project). */
-export function loadConfig(cwd: string): PlanConfig {
-	return loadConfigSection(cwd, "plan", DEFAULT_CONFIG, normalizeConfig);
-}

package/extensions/wechat/outbound.ts

@@ -1,100 +0,0 @@
-/**
- * Outbound file sending: encrypt a local file and deliver it as one Weixin file
- * message.
- *
- * The flow mirrors the reference client: read the plaintext, compute its size and
- * MD5, generate a 16-byte AES key and a file key, request the CDN upload target,
- * upload the AES-128-ECB ciphertext, then send a `type: 4` file item whose media
- * reference carries the returned download parameter.
- *
- * Everything is injected, so it is tested with a fake client and a temp file.
- */
-
-import { createHash, randomBytes } from "node:crypto";
-import { readFileSync } from "node:fs";
-import { basename } from "node:path";
-import { rejectionOf, type WechatClient } from "./client.ts";
-import { aesEcbPaddedSize, encryptEcb, sanitizeFileName, uploadUrlOf } from "./media.ts";
-import type { BotCredentials, CDNMedia } from "./types.ts";
-
-/** `UploadMediaType.FILE` from the protocol. */
-export const UPLOAD_MEDIA_TYPE_FILE = 3;
-
-export interface SendLocalFileArgs {
-	client: WechatClient;
-	account: BotCredentials;
-	cdnBaseUrl: string;
-	/** Files larger than this are refused. */
-	maxBytes: number;
-	to: string;
-	contextToken?: string;
-	filePath: string;
-	/** Display name; defaults to the file's base name, sanitized. */
-	fileName?: string;
-	signal?: AbortSignal;
-	/** Random bytes for the AES key and file key; defaults to `crypto.randomBytes`. */
-	random?: (size: number) => Buffer;
-}
-
-/**
- * Upload and send a local file. Returns true when the message was accepted.
- * Any failure (unreadable file, size cap, upload rejection) returns false rather
- * than throwing, so the caller can fall back.
- */
-export async function sendLocalFile(args: SendLocalFileArgs): Promise<boolean> {
-	try {
-		const plain = readFileSync(args.filePath);
-		if (plain.length === 0 || plain.length > args.maxBytes) return false;
-
-		const random = args.random ?? randomBytes;
-		const aesKey = random(16);
-		const filekey = random(16).toString("hex");
-		const rawsize = plain.length;
-		const rawfilemd5 = createHash("md5").update(plain).digest("hex");
-		const filesize = aesEcbPaddedSize(rawsize);
-
-		const upload = await args.client.getUploadUrl(
-			args.account,
-			{
-				filekey,
-				mediaType: UPLOAD_MEDIA_TYPE_FILE,
-				toUserId: args.to,
-				rawsize,
-				rawfilemd5,
-				filesize,
-				aeskey: aesKey.toString("hex"),
-			},
-			args.signal,
-		);
-
-		const downloadParam = await args.client.uploadCdn(
-			uploadUrlOf(upload, args.cdnBaseUrl, filekey),
-			encryptEcb(plain, aesKey),
-			args.signal,
-		);
-
-		// The reference encodes the hex key string as base64 (not the raw 16 bytes);
-		// the download decoder accepts either.
-		const media: CDNMedia = {
-			encrypt_query_param: downloadParam,
-			aes_key: Buffer.from(aesKey.toString("hex")).toString("base64"),
-			encrypt_type: 1,
-		};
-
-		const response = await args.client.sendFileMessage(
-			args.account,
-			{
-				to: args.to,
-				fileName: sanitizeFileName(args.fileName ?? basename(args.filePath)),
-				len: String(rawsize),
-				media,
-				contextToken: args.contextToken,
-			},
-			args.signal,
-		);
-
-		return rejectionOf(response) === undefined;
-	} catch {
-		return false;
-	}
-}

package/extensions/wechat/qrcode.ts

@@ -1,46 +0,0 @@
-/**
- * Rendering a QR string as terminal lines.
- *
- * Uses the `qrcode` package only for the module matrix, then draws Unicode
- * half-blocks so two matrix rows share one terminal line. The package loads on
- * the first QR, not when the extension registers: a session that never logs in
- * pays nothing for it. No ANSI is emitted; the login screen decides colours, and
- * the width is the matrix width plus a quiet zone.
- */
-
-interface QrMatrix {
-	size: number;
-	get(row: number, col: number): boolean;
-}
-
-/** Build the module matrix for `text`, loading `qrcode` on first use. */
-export async function qrMatrix(text: string): Promise<QrMatrix> {
-	const { default: QRCode } = await import("qrcode");
-	const qr = QRCode.create(text, { errorCorrectionLevel: "M" });
-	return qr.modules as unknown as QrMatrix;
-}
-
-/**
- * The QR as terminal lines. Each string is exactly `matrix.size + 2 * quiet`
- * columns wide (half-block characters are single width), so a caller can test
- * `qrLines(text)[0].length` against the terminal width.
- */
-export async function qrLines(text: string, options: { quiet?: number } = {}): Promise<string[]> {
-	const quiet = Math.max(0, options.quiet ?? 2);
-	const matrix = await qrMatrix(text);
-	const size = matrix.size;
-	const isDark = (row: number, col: number): boolean =>
-		row >= 0 && col >= 0 && row < size && col < size && matrix.get(row, col);
-
-	const lines: string[] = [];
-	for (let y = -quiet; y < size + quiet; y += 2) {
-		let line = "";
-		for (let x = -quiet; x < size + quiet; x += 1) {
-			const top = isDark(y, x);
-			const bottom = isDark(y + 1, x);
-			line += top && bottom ? "█" : top ? "▀" : bottom ? "▄" : " ";
-		}
-		lines.push(line);
-	}
-	return lines;
-}

package/skills/changelog/SKILL.md

@@ -1,148 +0,0 @@
----
-name: changelog
-description: "Maintain a Keep a Changelog file: record one user-visible bullet in the same commit, audit commits since the last tag for missing or weak entries, and curate a release section from the project's own rules. Use when writing, auditing, or releasing a changelog, not for ordinary code edits."
----
-
-# Maintain the changelog
-
-This is a procedure, not a second policy. Read the project's instructions first;
-where they disagree with this skill, the project wins. There are three modes:
-**record** (the default), **audit**, and **release**. `/skill:changelog` records;
-`... audit` and `... release` name the others.
-
-## 1. Read the project profile
-
-In this package the profile is written down; read it rather than rediscover it:
-
-- [`../../CHANGELOG.md`](../../CHANGELOG.md) — the preamble, the scope prefixes,
-  and the bullet shape in use;
-- [`../../AGENTS.md`](../../AGENTS.md) — the entry lands in the same commit as the
-  change, and a behavior change also updates the two entry READMEs and `docs/`;
-- [`../../docs/development.md#release`](../../docs/development.md#release) — the
-  normative release procedure: version bump, link refs, tag and push order;
-- [`../../test/release.test.ts`](../../test/release.test.ts) — the guard on
-  subsection names, order, emptiness, and the version pin.
-
-Everywhere else, find the same six things: the changelog and its preamble, the
-category spelling and order, the scope prefix and one-bullet-per-unit rule,
-whether the entry ships with the change, the release document with its bump and
-push order, and the check command with any release-consistency test.
-
-State the profile in one short paragraph. Do not invent a rule the project never
-stated; ask instead.
-
-## 2. Classify the change
-
-It qualifies when a user can observe it: behavior, a CLI/tool/command surface, a
-config default, packaging, security, or a documented promise that is now true or
-false.
-
-It does not qualify when only the implementation changed: an internal refactor, a
-rename, a test, formatting, a comment, or a dependency bump with no behavior
-change.
-
-One bullet per user-visible outcome. A feature and its bug fix before release can
-be one bullet if users see one outcome; two observable changes are two bullets.
-Ask when the outcome is unclear. Never invent an entry to make an audit look
-complete.
-
-## 3. Record
-
-- Write the entry in the same commit as the change. If the change is already
-  pushed without one, add a follow-up commit rather than rewriting history.
-- Put it under `[Unreleased]` in `Added`, `Changed`, `Deprecated`, `Removed`,
-  `Fixed`, or `Security`.
-- Lead with what the user can now do or what changed; use the project's scope
-  prefix; name a migration or required action explicitly.
-- Exclude file names, internal helpers, test counts, commit hashes, and vague
-  words such as "various" or "improvements".
-- Match the file's voice and tense. Do not add marketing.
-- A behavior change also updates its row in the catalog tables of
-  [`../../README.md`](../../README.md) and
-  [`../../README.zh-CN.md`](../../README.zh-CN.md) plus the `docs/` guide it
-  belongs to; the changelog is this skill's subject, not its only file. A skill's
-  change updates its `SKILL.md` and its README row together.
-- Re-read immediately before editing, append within the category, and preserve
-  other bullets and concurrent edits. Never create a second category heading.
-
-Shape: one blank-line-separated bullet per outcome, wrapped near 80 columns, the
-scope in backticks followed by a colon. The scope is the extension or module name,
-spelled as this package spells it — `bytefly`, `plan`, `wechat`, `todo` — or
-`lib`, `docs`, `test`, `ci`, `skills`. A bullet with no scope, or with a name the
-package does not use, is a defect. A bullet may run several sentences — say what
-the user sees, what it replaced, and any required action. Brevity is not the
-goal; vagueness is the defect.
-
-Good:
-
-```text
-- `config`: the report now says what its percentages are shares of. A
-  `Composition · 11k estimate` header sits above the rows, and a disabled
-  compaction no longer prints a headroom figure for a threshold that will never
-  fire.
-- `cli`: `oldKey` is no longer read; run `bun run config:migrate`.
-```
-
-Bad:
-
-```text
-- `config`: refactored invoice rendering and added tests.
-- `misc`: improvements.
-```
-
-## 4. Audit (read-only)
-
-1. Find the last tag: `git describe --tags --abbrev=0`, or the project's
-   equivalent.
-2. List the commits since it: `git log --oneline --no-merges <tag>..HEAD`. Read
-   each diff with `git show`; a subject line is not enough.
-3. For each commit, answer: is it user-visible? Which existing bullet covers it?
-   Is the scope right? Is the outcome accurate?
-4. Report a table:
-
-   | Commit | User-visible | Evidence | Existing entry | Action |
-   |---|---|---|---|---|
-
-   `Action` is add, update, leave, or ask. "No entry found" is a valid result.
-
-Also report duplicate `###` headings, empty categories, entries already shipped
-under a released heading, and a missing or empty `[Unreleased]` when the commits
-since the tag contain user-visible changes.
-
-Do not edit during the audit unless the user asks. If they do, return to
-**Record** and make only the entries the evidence supports.
-
-## 5. Release (only when asked)
-
-The project's release document is normative — in this package
-[`../../docs/development.md#release`](../../docs/development.md#release), guarded
-by [`../../test/release.test.ts`](../../test/release.test.ts). This is a
-checklist, not a replacement:
-
-- Confirm the version and the SemVer reason with the user.
-- Move every `[Unreleased]` entry under `## [X.Y.Z] - YYYY-MM-DD`; leave an empty
-  `[Unreleased]` heading.
-- Bump every manifest and update the compare and release link refs, in the same
-  commit as the movable part; the version in the manifest and the newest dated
-  heading must agree or the release test fails.
-- Run the project's release checks, then `bun test test/release.test.ts` for the
-  version and subsection rules.
-- Tag, push, and publish only with explicit approval, in the project's order. The
-  order matters: push the tag with `main`, never after it.
-- Keep the release commit mechanical: no behavior, code, or unrelated docs.
-- Use that section as the release body (`bun run release:notes X.Y.Z` prints it);
-  do not add extra prose.
-
-## 6. Quality gate
-
-- One bullet per user-visible change; every bullet starts with a scope and a user
-  outcome, and may take several sentences to state it.
-- No internal-only or duplicate entries, and no empty category headings.
-- No entry for a change that shipped before its heading.
-- Links and versions agree; the project check passes.
-
-## 7. Report and stop
-
-Say what was recorded, what the audit found, or what the release moved. List what
-was deliberately left out and why. When nothing qualifies, say so. Stop before
-editing if the project rules are missing or contradictory; ask instead.