chore(deps-dev): Bump @types/node from 22.19.19 to 25.9.1#6
Merged
Conversation
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
5 tasks
hizrianraz
added a commit
that referenced
this pull request
May 16, 2026
…el slugs Continues the §1.2 launch-readiness pass on top of the /manwe-pool → /hermes rename. Updates the marketing surface to match what api PR #7 and specs PR #5 actually ship. Changes by area: AAMC voter pool sweep (DeepSeek + Llama 3.3 70B → Grok 4 + Mistral Large 3, per spec v1.1): - AAQualityScatter.tsx: replace the 2 retired voter rows with Grok 4 + Mistral Large 3 entries; bump header comment to v1.1 + date - ProviderRail.tsx: drop the deepseek tile; add xai + mistral as live; ungate google (now live via api#7) - LayerTower.tsx: L2 description + capabilities list reflect the 5 AAMC voters - platform/page.tsx: L2 status text "5 AAMC voters live · Anthropic + OpenAI + Google + xAI + Mistral · Together for Llama" - page.tsx (homepage): both L2 hero descriptions updated - skill.md/route.ts: L2 routing summary updated SDK API accuracy (real `ainfera` SDK calls, not invented): - content/docs.ts /docs/quickstart: rewritten to AinferaClient + client.agents.register + agent.wallet.topup + agent.inference; uses ai_live_* key format; honest wallet topup language (manual approval for launch week, automated x402 in Week 1 fast-follow) - page.tsx QS_PYTHON / QS_TS / QS_CURL homepage code blocks: same rewrite — Agent.create + agent.infer + cap_per_day replaced with the actual SDK signature - HeroFlow.tsx, TerminalBlock.tsx, SignedChain.tsx: visible agent.infer() labels updated to agent.inference() Model slug normalization (dots → dashes — code identifiers should be dashed, display names keep dots): - PrimitiveDiagram.tsx: claude-opus-4.7 + gpt-5.5 + gemini-3.1-pro → dashed variants - TerminalBlock.tsx code data: "claude-opus-4.7" → "claude-opus-4-7" in 2 places Glossary fix: - AAMC entry was wrong (said "Agent-to-Agent Model Context" — that's not what AAMC stands for). Now reads: "Adjudication and Auto- Modification Council — 5 frontier Voters × 5 Lenses, with 3-of-5 advisory, 4-of-5 binding, 5-of-5+Council self-modification quorum." Verification: - tsc green after clearing stale .next/types - No more DeepSeek or Llama 3.3 70B references in source (only an intentional CHANGELOG-reference comment in AAQualityScatter) - All `agent.infer*` user-visible labels now agent.inference - All dotted model slugs gone; display names preserved Companion to: AAMC spec v1.1 (specs#5), api adapter wiring (api#7), verify trust-note (verify#6), mcp-server quickstart refresh (#6). Linear: AIN-95 (parent AIN-93 §1.2 subsections A, B, C, H, I) Co-Authored-By: Claude <noreply@anthropic.com>
hizrianraz
added a commit
that referenced
this pull request
May 16, 2026
#13) * feat(mint): display AgentCard JWS + explicit save-confirm checkbox The signup endpoint returns agent_card_jws but the modal was discarding it — only the api_key was displayed. AgentCard JWS is the verifiable provenance artifact: customers need to pin or publish it to prove the agent is theirs. Two changes: - Render the JWS in a readonly textarea with a CopyPill, alongside the existing API key field. - Replace the unconditional "I've saved it" button with a confirmation checkbox + disabled-until-checked "Continue" button. Mirrors the Bug #6 pattern from the Sun dashboard audit: keys that cannot be recovered should require an explicit acknowledgement before close, not just a click-through. The scrim/Escape close path is already blocked during the minted step, so the only exit is via the checkbox-gated Continue button. Co-Authored-By: Claude <noreply@anthropic.com> * feat(agents): wire authoritative provenance fields on agent detail Previously Canonical/did:web/Registered were derived from audit events alone — they showed "—" whenever the agent.registered event had fallen out of the latest 500-event window, or before the first event existed at all. Prefer the authoritative AgentDetailResponse (already fetched server- side via proxyGet) for canonical_uri + did_web. Fall back to the audit-derived snapshot, then to a constructed default. The fields now always render a real value once the agent exists, instead of misleading em-dashes. Also surface framework + installed_via from privateDetail — installed_via ("via SDK install" / "via GitHub OAuth") tells the auto-register story on the page that customers actually look at after running ainfera. Drops the local layerOf in favor of the shared lib/audit-layers helper introduced in 9e389ae — keeps L1-L5 mapping consistent across views. Co-Authored-By: Claude <noreply@anthropic.com> * feat(overview): "recently added" surface sells the auto-register loop Add a section above the stat grid that lists agent.registered events from the last 24h, dedup'd by agent_name. Each row links to the agent detail page with the canonical URI and a relative timestamp. The loop the surface explains: pip install ainfera -> ainfera init -> agent appears here within seconds -> ainfera.* events flow through the audit chain The data was already arriving — Phase 1's CORS fix makes the events visible — but Overview had no surface that singled out registrations from inferences. Tulkas auto-registered "sacrificial-001" on 2026-05-16 03:58 UTC via SDK install; that fact now visibly renders. Section is conditional (only shows when registrations exist in the window) so it doesn't add an empty placeholder for fresh tenants. Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com>
hizrianraz
added a commit
that referenced
this pull request
May 16, 2026
…+ CDP rail + ai_infera_ (#15) * feat(marketing): rename /manwe-pool → /hermes (customer-facing brand fix) The /manwe-pool route was the customer landing page for hermes-agent builders, but "Manwe" is the founder's private agent Aratar codename (see project-ainfera-topology memory). Using it externally conflated the cap-table-separate founder asset with a customer cohort label. Renames the route and brand to "Hermes Pool" — parallel to "OpenClaw Pool", named for the framework the cohort uses. The Pool 1 · hermes- agent eyebrow text is unchanged. Changes: - git mv apps/marketing/app/manwe-pool → app/hermes - All Manwe Pool / /manwe-pool references in page.tsx, /openclaw, and /platform updated to Hermes Pool / /hermes - sitemap.ts, lib/og.tsx OG map, og/[slug]/route.tsx slug list - Duplicated public/og/manwe-pool.png → hermes.png (old asset retained for any cached crawlers; safe to delete after 308 settles) - next.config.mjs: added 308 (permanent: false) redirect /manwe-pool → /hermes so backlinks keep working Vocabulary lock check: "Hermes" is banned as an agent codename per web/.claude/CLAUDE.md. "Hermes Pool" is a customer cohort marketing label (parallel to "OpenClaw Pool"), same as the framework name — not an agent codename. The actual hermes-agent framework name is used lowercase throughout, which the CLAUDE.md explicitly allows. tsc green after clearing stale .next/types build artifacts. Linear: AIN-95 (parent AIN-93 § §1.2-D + §1.2-C cards) Co-Authored-By: Claude <noreply@anthropic.com> * feat(marketing): launch-readiness sweep — AAMC lineup + SDK API + model slugs Continues the §1.2 launch-readiness pass on top of the /manwe-pool → /hermes rename. Updates the marketing surface to match what api PR #7 and specs PR #5 actually ship. Changes by area: AAMC voter pool sweep (DeepSeek + Llama 3.3 70B → Grok 4 + Mistral Large 3, per spec v1.1): - AAQualityScatter.tsx: replace the 2 retired voter rows with Grok 4 + Mistral Large 3 entries; bump header comment to v1.1 + date - ProviderRail.tsx: drop the deepseek tile; add xai + mistral as live; ungate google (now live via api#7) - LayerTower.tsx: L2 description + capabilities list reflect the 5 AAMC voters - platform/page.tsx: L2 status text "5 AAMC voters live · Anthropic + OpenAI + Google + xAI + Mistral · Together for Llama" - page.tsx (homepage): both L2 hero descriptions updated - skill.md/route.ts: L2 routing summary updated SDK API accuracy (real `ainfera` SDK calls, not invented): - content/docs.ts /docs/quickstart: rewritten to AinferaClient + client.agents.register + agent.wallet.topup + agent.inference; uses ai_live_* key format; honest wallet topup language (manual approval for launch week, automated x402 in Week 1 fast-follow) - page.tsx QS_PYTHON / QS_TS / QS_CURL homepage code blocks: same rewrite — Agent.create + agent.infer + cap_per_day replaced with the actual SDK signature - HeroFlow.tsx, TerminalBlock.tsx, SignedChain.tsx: visible agent.infer() labels updated to agent.inference() Model slug normalization (dots → dashes — code identifiers should be dashed, display names keep dots): - PrimitiveDiagram.tsx: claude-opus-4.7 + gpt-5.5 + gemini-3.1-pro → dashed variants - TerminalBlock.tsx code data: "claude-opus-4.7" → "claude-opus-4-7" in 2 places Glossary fix: - AAMC entry was wrong (said "Agent-to-Agent Model Context" — that's not what AAMC stands for). Now reads: "Adjudication and Auto- Modification Council — 5 frontier Voters × 5 Lenses, with 3-of-5 advisory, 4-of-5 binding, 5-of-5+Council self-modification quorum." Verification: - tsc green after clearing stale .next/types - No more DeepSeek or Llama 3.3 70B references in source (only an intentional CHANGELOG-reference comment in AAQualityScatter) - All `agent.infer*` user-visible labels now agent.inference - All dotted model slugs gone; display names preserved Companion to: AAMC spec v1.1 (specs#5), api adapter wiring (api#7), verify trust-note (verify#6), mcp-server quickstart refresh (#6). Linear: AIN-95 (parent AIN-93 §1.2 subsections A, B, C, H, I) Co-Authored-By: Claude <noreply@anthropic.com> * feat(launch-readiness): swap dashboard rail Stripe→CDP wallet + ai_infera_ key prefix in marketing snippets Dashboard: - settings: rail label "Stripe Customer Balance" → "CDP Smart-Wallet · x402"; USDC simplified; toast/button copy aligned to CDP funding flow - wallet: drop "Top up via Stripe" ghost button (rail no longer Stripe) Marketing snippets — uniform ai_infera_ key prefix: - /build quickstart response, / page Python+TS snippets, /skill.md quickstart, /docs quickstart No behavior change to API or SDK. Copy + prefix only. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com>
hizrianraz
added a commit
that referenced
this pull request
May 16, 2026
/skill.md is the AI-native discovery document — agents reading it learn
which model values to pass in the `model` field of /v1/inference. Prior
text used human prose ("Claude Opus 4.7", "GPT-5.5") which doesn't help
an LLM generate the canonical slug string.
After api PR #13 (canonical slug→upstream adapter translation) shipped,
all 5 AAMC v1.0 canonical slugs route correctly:
claude-opus-4-7, gpt-5-5, gemini-3-1-pro, grok-4, mistral-large-3
This adds the canonical slugs inline + a paragraph explaining the
provider-drift firewall (e.g. gpt-5-5 → upstream gpt-5.5-pro). Caught
by E2E v3 cross-cutting check C10.
Memory #6 + feedback-aamc-active-lock + feedback-slug-adapter-coupling.
Co-authored-by: Claude <noreply@anthropic.com>
hizrianraz
added a commit
that referenced
this pull request
May 16, 2026
…vendors (#26) The hero provider strip mixed unrelated brands: AI providers (anthropic, openai, google, xai, mistral), infrastructure (modal, cloudflare, supabase), settlement (base, coinbase, stripe), measurement (artificial analysis), and three SOON badges. The eye couldn't parse a coherent story and the SOON×3 leaked a "not ready yet" signal during the launch window. Replace with 16 items that map cleanly to the product story (Memory #6 two-tier narrative + Memory #8 10 live providers): AAMC Council anthropic · openai · google · xai · mistral Routing catalog together · groq · deepinfra · fireworks · novita Standards x402 · usdc · base · sigstore · mcp · a2a Drops: - modal, cloudflare, supabase — internal infra, not a customer signal - artificial analysis — already cited in /aamc chart footnote - SOON×3 (meta / coinbase cdp / stripe) — pre-launch noise Updates the rail eyebrow to "AAMC Council · Routing catalog · Open standards" so the section's intent is legible at a glance, and removes the now-unused `soon` field from the Provider type. Standards without brand logos use a unified outlined-square mark so the eye reads them as a class rather than mismatched brand fragments. Co-authored-by: Claude <noreply@anthropic.com>
This was referenced May 16, 2026
hizrianraz
added a commit
that referenced
this pull request
May 16, 2026
Replaces the abstract [05] Five primitives L1-L5 grid on the homepage with a concrete drain-proof caps table showing the live caps on the 5 public Ainfera agents: varda AI co-founder $1.50 / $20.00 (per-call / daily) yavanna Public Voice $1.00 / $15.00 aule Code & repo $0.75 / $10.00 namo Research $0.50 / $5.00 tulkas Red team · drain probe $0.25 / $2.00 These values are sourced from /v1/users/hizrianraz/dashboard (per-agent spend_policy.per_call_cap_usd / daily_cap_usd). AIN-133 tracks wiring this to live wallet data Week 1; for launch they're hardcoded — sync if any cap rotates between now and Mon 09:00 SGT. The L1-L5 platform breakdown is removed from the homepage. The /platform route is left intact per anti-pattern #6 (don't break deep-links); just no longer referenced from the homepage nav flow. Manwe is noted in a small footer line as "founder dogfood, separately owned" per Memory #4 — caps mentioned but not in the public fleet table, matching the /agents-page omission. Removes now-unused imports: HoverCard, PrimitiveDiagram. Removes the PRIMITIVES const + Primitive type that drove the old grid. Co-authored-by: Claude <noreply@anthropic.com>
This was referenced May 16, 2026
hizrianraz
added a commit
that referenced
this pull request
May 18, 2026
…ws scaffold (#39) Additive scaffold path per founder direction — adds new pages without touching the 10+ existing marketing pages (which would require per-page auth per v6.1 Discipline #6 corollary). ## Marketing additions (additive, no removals) - `/routing` — 4 sections: hero, scoring formula (Q 0.40 / L 0.30 / C 0.30 defaults from AIN-154 Phase 0 lock), fallback chains table, audit-verifiable routing.decided event surfacing - `/audit` — hash-chained per-agent event log + 5 event-type table + live curl examples for /v1/audit/public + /v1/audit/<id> + /verify + Annex IV bundle export (Studio/Scale tier reference) - `/models` — AAMC v1.0 voters table (5 frontier providers) + ATS scoring dimensions (5 axes, FWGM aggregate, Compliance veto, insufficient-data floor per AIN-161 Phase 0 lock) + CC-BY 4.0 public dataset disclosure Existing `/pricing` page untouched (Memory #8 — no bundling fixes with in-flight content). ## Dashboard additions - `(tenant)/workflows/page.tsx` + `WorkflowsPageClient.tsx` — list view with status badges + sortable table; empty-state surfaces API docs - `(tenant)/workflows/[workflow_id]/page.tsx` + `WorkflowDetailClient.tsx` — detail view with breadcrumb + workflow meta header + ordered tasks table ## Data-shim deferred to Phase B2 Backend `/v1/workflows*` endpoints (shipped api#33) use bearer-token tenant auth via `CurrentTenant` dep. The dashboard's existing `proxyGet` helper uses internal-key + X-Ainfera-On-Behalf-Of shape that workflows router doesn't accept yet. For this PR: pages render empty-state + status messaging that explicitly references AIN-153 Phase B2 as the data-shim work. When the shim lands (user-scoped /v1/users/{handle}/workflows OR proxyGet support for absolute paths with internal-key auth), the page swaps to `proxyGet<WorkflowsListResponse>(...)`. Empty-state copy is honest about what's not wired yet — no fake loading spinners or simulated data. ## Brand v1.3 compliance All 3 marketing pages + 2 dashboard pages use existing tokens from `apps/marketing/components/v13/` (ScrollFade, SectionMarker) + dashboard tailwind classes (dash-head, dash-h1, dash-sub, bg-bg-elev, border-hairline-strong, etc.). No new design primitives; zero brand drift. ## Test plan - [x] `pnpm typecheck` passes for both marketing + dashboard - [x] Visual review: layout matches existing pages (no design drift) - [ ] Vercel preview deployment renders all 5 new pages - [ ] Founder UX walkthrough on Mac Studio + iPhone (Brand v1.3 lock) - [ ] Phase B2 follow-up: dashboard data shim wires /v1/workflows* ## Cross-refs - AIN-158 (marketing parent · D14 5-page lock) - AIN-153 (dashboard workflow trace view parent) - AIN-153 Phase A migration (PR api#26 · schema 0012) - AIN-153 Phase B endpoints (PR api#33 · 5 /v1/workflows* routes) - AIN-161 Phase 1 (PR api#29 · model_leaderboard view referenced on /models page footer) - AIN-154 Phase 0 prep (D-154-1 weights referenced on /routing page) - v6.1 Discipline #6 corollary (PR ainfera-os#36 · why additive scaffold vs destructive refactor) Co-authored-by: Claude <noreply@anthropic.com>
hizrianraz
added a commit
that referenced
this pull request
May 19, 2026
The May 2026 ".gitignore .claude/* contents" pass added `.claude/*` to .gitignore but explicitly whitelisted `!.claude/CLAUDE.md` (+ SKILL.md and AGENTS.md), keeping the file tracked on `main`. Result: founder Workspace email + internal agent fleet topology was publicly exposed. Per AIN-183 audit P0-1 finding. Fix: - Drop `!.claude/CLAUDE.md` (+ SKILL.md + AGENTS.md) whitelist lines. None of the three were ever needed tracked in a public repo; the whitelist was defense-in-the-wrong-direction. - `git rm --cached .claude/CLAUDE.md` removes from HEAD index. The file stays on disk so local Claude sessions in this checkout continue to load it as session memory. Scope: this commit removes from HEAD only. The file remains in git history; a history rewrite (`git filter-repo` + force push) is a separate decision (Discipline #6 corollary auth required). Co-Authored-By: Claude <noreply@anthropic.com>
Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 22.19.19 to 25.9.1. - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) --- updated-dependencies: - dependency-name: "@types/node" dependency-version: 25.7.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/types/node-25.7.0
branch
from
720b0b5 to
5d880b8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps @types/node from 22.19.19 to 25.9.1.
Commits