Skip to content

feat(classify): add review-only suggestions with cached evidence - #11

Open
Railly wants to merge 10 commits into
mainfrom
railly/classify-performance-latest
Open

Railly wants to merge 10 commits into
mainfrom
railly/classify-performance-latest

Conversation

@Railly

@Railly Railly commented Sep 22, 2026

Copy link
Copy Markdown
Member
  • Add review-only Jev classification with explicit taxonomies and durable receipts.
  • Batch GitHub reads and reuse version-checked evidence, including an offline cached view.
  • Add bounded concurrency, 429 backoff, safe diagnostics, and regression coverage.

@vercel

vercel Bot commented Sep 23, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
issue-graph Ready Ready Preview, v0 Nov 14, 2026 10:48pm UTC

Comment thread src/semantic-evidence-store.ts Resolved
Comment thread src/semantic-evidence-store.ts Resolved
# Conflicts:
#	README.md
#	apps/docs/tests/content.test.ts
#	scripts/verify-package.ts
#	skill-data/core/SKILL.md
#	skill-data/core/references/workflows.md
#	src/cli.ts
#	src/index.ts
#	src/schema.ts
`ISSUE_GRAPH_HOME` is shared with graph, reconcile and status runs, which
create it with the default umask (0755). The evidence, receipt and cache
stores required the root itself to be 0700, so `classify` failed with
`evidence-invalid` after any earlier run.

The root now only has to be an owned directory without group or world
write bits; everything under `classify/` keeps the 0700/0600 checks. The
error hints name the permission requirements.
…tial

The evidence store validated every title, body and comment against a
token pattern. Public issues routinely quote `sk-` or `ghp_` examples and
pasted logs, so one match failed the evidence write and stopped the whole
`classify` run with `evidence-invalid`.

Captures only hold public issue and comment text, never the CLI's own
GitHub or Gateway credentials, so the pattern guarded nothing. It is
removed from both write and read validation.
Comment thread src/cli.ts Resolved
…ateway

The classify transport ran `gh api` with no host, so an ambient `GH_HOST` or
gh's own config could select a network-private Enterprise server. That server
reports its own repositories as `PUBLIC`, which passed the visibility check,
and issue text could then reach the external Gateway during inference.

`shellTransport` now accepts a hostname and sets `GH_HOST` for every gh child;
classify pins `github.com`. Capture also requires the repository `url` returned
by GraphQL to be the github.com URL, so a response from another host fails
identity verification even through a caller-supplied transport.
`classify` shipped without a documentation page or navigation entry, so the
command, safety, cache, and billing guidance existed only in the README and the
bundled skill. Add `docs/classify` with preview and run modes, flags, what
leaves the machine, cache and receipt layout, billing limits, and output codes,
register the slug in the docs navigation, and point the README commands table
at the page.
# Conflicts:
#	skill-data/core/references/workflows.md

This branch was successfully deployed

1 active deployment
Preview — fce02a74 Deployed Nov 14, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants