mirror of
https://github.com/alkimake/paperclip.git
synced 2026-06-14 18:10:39 +09:00
## Thinking Path > - Paperclip orchestrates AI agents for zero-human companies. > - The plugin system is the extension surface for optional product capabilities without baking every workflow into core. > - The LLM Wiki plugin package was reviewed in stacked PR #5592, which targeted `pap-9173-llm-wiki-rest`. > - The stack base PR #5597 merged to `master` before #5592 was merged into that branch, so the plugin package never reached `master`. > - A direct PR from `pap-9173-llm-wiki-rest` back to `master` would be noisy because that branch has diverged from current `master`. > - This pull request reapplies the reviewed `packages/plugins/plugin-llm-wiki/` package onto current `master` and updates Docker deps-stage manifest coverage. > - The branch intentionally no longer changes `pnpm-workspace.yaml` after maintainer feedback; because the new package is now a root workspace importer, the remaining integration question is how maintainers want the root lockfile handled under the current PR policy. ## What Changed - Added the LLM Wiki plugin package under `packages/plugins/plugin-llm-wiki/` from the merged PR #5592 head. - Preserved the post-review cleanup from #5592: generated design/screenshot artifacts are not committed, and `src/ui/index.tsx` / `src/wiki.ts` are small public entrypoints. - Added the new plugin package manifest to the Docker deps stage so policy can validate package manifest coverage. - Removed the earlier `pnpm-workspace.yaml` exclusion per maintainer request, so the plugin is included by the existing `packages/plugins/*` workspace glob. ## Verification Current head: - PGlite migration harness: ran migrations 001-003, verified old non-space distillation unique constraints were removed, inserted duplicate cursor and work-item keys in a second space, then reran migration 003 successfully - `node ./scripts/check-docker-deps-stage.mjs` - `git diff --check` Known current-head install result after removing the workspace exclusion: - `pnpm install --frozen-lockfile` fails because `pnpm-lock.yaml` has no importer for `packages/plugins/plugin-llm-wiki/package.json`. Previously verified on the same plugin source before the workspace-exclusion removal: - `pnpm --filter @paperclipai/plugin-sdk build` - `cd packages/plugins/plugin-llm-wiki && pnpm install --lockfile=false && pnpm test` ## Risks - The branch now includes `packages/plugins/plugin-llm-wiki` in the root workspace but does not update `pnpm-lock.yaml`. Root frozen install will fail until maintainers choose a lockfile path that fits repo policy. - Committing `pnpm-lock.yaml` directly on this PR conflicts with the current PR policy check, while excluding the package from `pnpm-workspace.yaml` was rejected in maintainer feedback. - The package includes UI code already reviewed in #5592; generated screenshot/design artifacts were intentionally removed per maintainer request, so visual review should regenerate screenshots locally if needed. - The package depends on plugin host support from #5597, which is already merged to `master`. > For core feature work, check [`ROADMAP.md`](ROADMAP.md) first and discuss it in `#dev` before opening the PR. Feature PRs that overlap with planned core work may need to be redirected — check the roadmap first. See `CONTRIBUTING.md`. ## Model Used - OpenAI GPT-5 Codex via Codex CLI, tool use and local code execution enabled; context window not exposed. ## Checklist - [x] I have included a thinking path that traces from project context to this change - [x] I have specified the model used (with version and capability details) - [x] I have checked ROADMAP.md and confirmed this PR does not duplicate planned core work - [x] I have run the targeted checks listed above - [x] I have added or updated tests where applicable - [ ] If this change affects the UI, I have included before/after screenshots - [x] I have updated relevant documentation to reflect my changes - [x] I have considered and documented any risks above - [x] I will address all Greptile and reviewer comments before requesting merge Stack context: #5592 was merged into `pap-9173-llm-wiki-rest` after #5597 had already merged that branch to `master`, so this follow-up PR is needed to carry the plugin package itself into `master`. Co-authored-by: Paperclip <noreply@paperclip.ing>
49 lines
1.6 KiB
TypeScript
49 lines
1.6 KiB
TypeScript
type FetchLike = (input: string, init: RequestInit) => Promise<Response>;
|
|
|
|
export type IngestSourceActionResult = {
|
|
operation?: {
|
|
issue?: {
|
|
id?: unknown;
|
|
} | null;
|
|
} | null;
|
|
};
|
|
|
|
export function readIngestOperationIssueId(result: unknown): string {
|
|
const issueId = (result as IngestSourceActionResult | null)?.operation?.issue?.id;
|
|
if (typeof issueId === "string" && issueId.trim()) return issueId;
|
|
throw new Error("Ingest operation did not return an issue id; the dropped file could not be attached.");
|
|
}
|
|
|
|
async function readUploadError(response: Response): Promise<string> {
|
|
const body = await response.json().catch(() => null);
|
|
if (body && typeof body === "object") {
|
|
const error = (body as { error?: unknown; message?: unknown }).error;
|
|
if (typeof error === "string" && error.trim()) return error;
|
|
const message = (body as { error?: unknown; message?: unknown }).message;
|
|
if (typeof message === "string" && message.trim()) return message;
|
|
}
|
|
return `Attachment upload failed with HTTP ${response.status}.`;
|
|
}
|
|
|
|
export async function uploadIssueAttachmentFile(input: {
|
|
companyId: string;
|
|
issueId: string;
|
|
file: File;
|
|
fetchImpl?: FetchLike;
|
|
}): Promise<unknown> {
|
|
const fetchImpl = input.fetchImpl ?? fetch;
|
|
const form = new FormData();
|
|
form.append("file", input.file);
|
|
const response = await fetchImpl(
|
|
`/api/companies/${encodeURIComponent(input.companyId)}/issues/${encodeURIComponent(input.issueId)}/attachments`,
|
|
{
|
|
method: "POST",
|
|
credentials: "include",
|
|
body: form,
|
|
},
|
|
);
|
|
if (!response.ok) {
|
|
throw new Error(await readUploadError(response));
|
|
}
|
|
return response.json();
|
|
}
|