web-discovery

Imported from hraness/web-discovery (AGENTS.md). Install upstream with npx skills add hraness/web-discovery. Copyright stays with the author.

Contents

• src/discovery.ts owns validated origins, paths, site and article metadata, representative images, crawler policy, sitemaps, feed enclosures, manifests, IndexNow payloads, and structured data.
• src/json-ld.tsx and src/social-image.tsx own the React and Next.js rendering boundaries.
• src/*.test.ts holds deterministic examples and property tests for public behavior.
• scripts/ contains build, package-smoke, inventory, and public-boundary checks.
• .github/workflows/ runs read-only continuous integration and publishes an immutable release only after tag verification succeeds.
• .agents/skills/ contains portable cross-repository KB and phased-execution workflows.
• kb/ contains authored repository rationale, maintained synthesis, and implementation plans.
• WRITING.md and STYLE.md define the internal and public prose contracts.

Guidelines

• Keep this package product-neutral and limited to truthful web-discovery primitives shared by concrete Next.js consumers.
• Follow WRITING.md for internal prose and STYLE.md for public prose.
• Apply unreasonably robust programming when agent work is cheap. Model invalid states out of existence, parse foreign values from unknown, and pair readable deterministic regressions with property tests for parsers, ordering, normalization, serialization, and round trips.
• Deliver changes to main through a current-head pull request. Keep the stable Required CI job green, resolve every review thread, and serialize merges. Human approval stays optional while one regular maintainer would otherwise self-review. Never force-push or bypass the gate.
• Pin Hraness dependencies to reviewed immutable releases or full commits. Never connect repositories through sibling paths, Git submodules, or coordinated main assumptions; upgrade each consumer independently.
• Extract another shared package only after two concrete consumers require the same stable, product-neutral interface. Keep product titles, descriptions, routes, update dates, crawler decisions, and visual identity in consumers.
• Freeze package interfaces before parallel lanes begin. Give exports, manifests, lockfiles, generated output, and other convergence surfaces one owner while lanes edit disjoint paths.
• Keep canonical URLs, social metadata, sitemaps, crawler policy, and structured data derived from one validated bare HTTPS origin.
• Keep representative article images consumer-owned and derive metadata, schema, feed enclosures, and image sitemap entries from one checked record. Do not move asset provenance or image rendering into this package.
• Model indexable and private surfaces explicitly. Never use robots.txt as a substitute for page-level noindex, authentication, or authorization.
• Emit only schema that represents visible page content. Do not invent ratings, reviews, prices, authorship, dates, or other unsupported facts.
• Keep social cards deterministic, readable, and free of remote assets or runtime filesystem dependencies. Load the official Nebula Sans Book and Bold payloads only through the reviewed generated Design Kit export.
• Preserve the root, ./json-ld, and ./social-image export contracts. Keep React and Next.js as peers. The only runtime dependency is the exact immutable Design Kit release that supplies the social-image font payloads; do not add product dependencies.
• Use Bun 1.3.14 for installs, builds, and tests. Verify every packed runtime export with genuine Node 24 and a real Next.js production build.
• Keep mandatory rules in the closest AGENTS.md, executable contracts in types and tests, and pull-based rationale, evidence, synthesis, and plans in kb/.
• Run bun run check before handoff. Run bun run kb:refresh, review the bounded findings, and finish with bun run kb:check after material KB edits.

• Treat the user's request to change this repository as standing authorization for routine task-owned commits, pushes, pull requests, merges, releases, deployments, and production verification after the gates applicable to that action pass. Do not ask for duplicate confirmation. Build confidence through relevant automated checks, bounded diagnostics, and independent review, not another human approval. Passing checks does not expand task scope or authority.
• Prefer agentic service provisioning for new infrastructure. Check Vercel Marketplace for a native product that can provision the required resource first; use Stripe Projects as a supported alternative when it better covers the service or the Marketplace route only connects an existing account. Verify the current catalog, account, region, plan, recurring cost and resource capabilities before selecting a route. Prefer supported provider CLIs or APIs over browser-only setup when neither catalog fits, and explain the concrete exception. Reuse existing owner-controlled resources where appropriate; this preference alone does not authorize migrations, duplicate accounts, paid upgrades or wider access. Continue setup already authorized by the task and budget without duplicate confirmation. Keep provider credentials and generated environment files private, complete required interactive authentication, and verify deployment, persistence and recovery separately from successful provisioning.
• Separate artifact admission from live qualification and operational activation. Use applicable automated source, security, package/install, and provenance evidence for artifact admission; live provider qualification is not a universal publication prerequisite. Preserve explicit live acceptance criteria and require relevant live evidence for claims that depend on it. If publication or an artifact's install, upgrade, or default-use path activates risky unqualified behavior, keep that behavior guarded or disabled, or obtain bounded relevant evidence before shipping or activation.
• Use the repository's documented delivery workflow and preserve the identity, target, capacity, migration, and recovery guards applicable to operational activation. Replace an obsolete gate through a reviewed source and policy change with corresponding tests, never an ad hoc skip. Preserve every runtime-enforced approval, access control, branch protection, environment rule, safety policy, and required final gate. Ask for user input only when delivery needs a material product decision, missing credentials or authority, unavoidable interactive authentication, an irreversibly destructive action outside task scope, or resolution of a failure that cannot be handled safely and autonomously.
• Preserve production and user data throughout delivery. Inspect the exact account, environment, deployment, and data target before writes. For data changes, inspect a dry run or equivalent migration plan and validate the recovery path before any effect that could lose or corrupt data. Prefer additive, backward-compatible migrations and bounded batches. Record mutation intent, use idempotency or conditional writes, and reconcile uncertain results before retrying. Verify deployed identity, health, and relevant data invariants after delivery. Routine delivery never authorizes resetting, truncating, dropping, or overwriting user data; stop the unsafe operation if preservation or recovery cannot be established.
• Prefer short-lived repository workload identities such as OIDC trusted publishing, GitHub Apps, and narrowly scoped machine identities. Use unattended stable publication and production promotion when supported by the provider and repository. Establish supported machine authority once and verify it with a non-publishing preflight where available; routine releases should not require recurring interactive authentication or conversational approval. Retain account two-factor authentication and provider controls, including required authentication for approval of an exact staged artifact; do not add long-lived personal tokens to eliminate an interactive prompt.
• Keep delivery gates proportional to the failure they prevent. Prefer required checks on the current integration candidate, independent agent review, and atomic or conditional integration. Add a merge queue or another approval stage only for a demonstrated coordination or safety need. Replace redundant queues, serial waits, and duplicate checks through reviewed policy changes while retaining evidence for the integrated result.
• Preserve useful reasoning fan-out, but avoid unnecessary checkout fan-out. Prefer subagents in the current task for bounded research, review, diagnosis, and focused checks when they can safely share one working tree; create a separate task or worktree only for independently deliverable divergent edits, an isolated verification tree, or a different execution environment.
• Give each expensive focused validation command and external wait one owner. The integration owner reviews that evidence and runs the repository-required aggregate or final gate once after convergence. Reuse evidence only for the exact Git tree, command, lockfiles, toolchain, relevant environment, and validity period, and never to skip a required final integration, merge, release, deployment, or production-verification gate.
• On Hraness development machines, use $oompa-local-efficiency and the installed host scheduler for heavyweight top-level commands when available. Keep ordinary work in the compute lane; give authenticated browser/dev-server/Chromium work one browser-auth owner and Mac-only validation one mac-native owner.
• When a CI or policy gate scans complete Git history, check out the exact governed SHA and fetch only the fully qualified governed refs before scanning. Preserve the complete-history gate and reject unexpected refs instead of importing unrelated concurrent heads.
• At closeout, record applicable branch, PR, check, merge, release, deployment, and production evidence. Archive only conclusively finished tasks, never from silence alone, and reclaim only freshly revalidated clean merged worktrees through the guarded exact-path flow.

ALGAL skills

• Prefer the globally installed algal-* skills for bounded git state, diffs, repository survey/search, test and release gates, CI polling, and web fetches instead of repeated raw tool output.
• At session start, if the algal skill is unavailable, install the current skill pack for Claude Code, Codex, and Devin for Terminal with bunx skills add 0thernet/algal-skills --global --agent claude-code codex devin --skill '*' --copy --yes.
• Confirm installation with bunx skills list --global. If Bun or network access is unavailable, continue with repository-native tools instead of blocking delivery.
• Treat ALGAL receipts as execution evidence, not provider attestation, and preserve the repository's normal verification and release gates.