feat(heicode): SK workflow UI, Agnet contract docs, usage-log schema

Manager web: Git sources workflow steps and copy; typecheck fixes for auth
and home sections; UsageLog type in usage-log-schema.ts (outside ignored data/).

docs: Agnet platform contract adds runtime_execution and sk_access_policy,
orchestration-plan and acceptance matrix aligned.

Made-with: Cursor
This commit is contained in:
Ubuntu
2026-05-01 07:38:17 +00:00
parent a8f64bce68
commit b42e5b2dd0
25 changed files with 171 additions and 71 deletions
+14 -1
View File
@@ -620,7 +620,7 @@ export function AgnetAuditPage() {
}
// =============================================================================
// Git sources — SK 正文以 Git 为准;此处为绑定说明 + 运行时解析锚点列表
// Git sources — 绑定代码/SK 仓库与云上权限 → 部署 → 展示各部署的快照锚点(SK 正文仍以 Git 为准)
// =============================================================================
export function AgnetSKSourcesPage() {
@@ -672,6 +672,19 @@ export function AgnetSKSourcesPage() {
<p className='mt-2'>{t('Git sources binding explainer')}</p>
</div>
<div className='mt-4 rounded-xl border border-[color-mix(in_oklch,var(--primary)_18%,var(--border))] bg-[color-mix(in_oklch,var(--card)_50%,transparent)] p-4 text-sm leading-relaxed text-muted-foreground'>
<p className='font-medium text-foreground'>
{t('Git sources workflow title')}
</p>
<ol className='mt-3 list-decimal space-y-2 ps-5 marker:text-muted-foreground'>
<li>{t('Git sources workflow step 1')}</li>
<li>{t('Git sources workflow step 2')}</li>
<li>{t('Git sources workflow step 3')}</li>
<li>{t('Git sources workflow step 4')}</li>
<li>{t('Git sources workflow step 5')}</li>
</ol>
</div>
{!effectiveDeployment ? (
<EmptySurface
title={t('No deployment for Git sources')}
+1 -2
View File
@@ -7,7 +7,6 @@ import {
} from '@/features/auth/errors'
import type {
LoginPayload,
LoginResponse,
Login2FAResponse,
TwoFAPayload,
RegisterPayload,
@@ -131,7 +130,7 @@ async function callHeicodeAuth<T>(
`Auth request failed (${res.status})`
throw new Error(message)
}
return data
return data as T
}
// ============================================================================
@@ -35,7 +35,7 @@ const MODELS: ModelConfig[] = [
id: 'gemini-pro',
name: 'gemini-2.5-pro',
response:
'Heicode Manager binds Git-backed SK sources and rolls Agnet runs, events, resolved anchors, and audit into one tenant-scoped control plane.',
'Bind Git code and SK tool repos, allocate cloud permissions for sub-agents, then deploy—runs inherit SK allow/deny policy with hashed anchors, events, and audit on one tenant-scoped control plane.',
tokens: 29,
latency: 156,
badgeClass:
@@ -1,6 +1,5 @@
import { Link } from '@tanstack/react-router'
import { ArrowRight } from 'lucide-react'
import { useTranslation } from 'react-i18next'
import { Button } from '@/components/ui/button'
import { AnimateInView } from '@/components/animate-in-view'
@@ -10,8 +9,6 @@ interface CTAProps {
}
export function CTA(props: CTAProps) {
const { t } = useTranslation()
if (props.isAuthenticated) {
return null
}
@@ -8,7 +8,6 @@ import {
Users,
HeartHandshake,
} from 'lucide-react'
import { useTranslation } from 'react-i18next'
import { AnimateInView } from '@/components/animate-in-view'
interface FeaturesProps {
@@ -16,8 +15,6 @@ interface FeaturesProps {
}
export function Features(_props: FeaturesProps) {
const { t } = useTranslation()
const features = [
{
id: 'fast',
@@ -1,10 +1,7 @@
import { Settings, Zap, BarChart3 } from 'lucide-react'
import { useTranslation } from 'react-i18next'
import { AnimateInView } from '@/components/animate-in-view'
export function HowItWorks() {
const { t } = useTranslation()
const steps = [
{
num: '1',
@@ -1,5 +1,4 @@
import { useRef, useEffect, useCallback } from 'react'
import { useTranslation } from 'react-i18next'
interface CounterProps {
end: number
@@ -70,8 +69,6 @@ interface StatsProps {
}
export function Stats(_props: StatsProps) {
const { t } = useTranslation()
const stats = [
{ end: 100, suffix: 'K+', label: '已编排任务' },
{ end: 50, suffix: '+', label: '接入租户' },
@@ -21,7 +21,7 @@ import {
StatusBadge,
type StatusBadgeProps,
} from '@/components/status-badge'
import type { UsageLog } from '../../data/schema'
import type { UsageLog } from '../../usage-log-schema'
import {
formatModelName,
getFirstResponseTimeColor,
@@ -29,7 +29,7 @@ import { Label } from '@/components/ui/label'
import { ScrollArea } from '@/components/ui/scroll-area'
import { StatusBadge, type StatusBadgeProps } from '@/components/status-badge'
import { DynamicPricingBreakdown } from '@/features/pricing/components/dynamic-pricing-breakdown'
import type { UsageLog } from '../../data/schema'
import type { UsageLog } from '../../usage-log-schema'
import {
parseLogOther,
getParamOverrideActionLabel,
@@ -132,7 +132,7 @@ export function UsageLogsTable({ logCategory }: UsageLogsTableProps) {
const isLoadingData = isLoading || (isFetching && !data)
const table = useReactTable({
data: logs as Record<string, unknown>[],
data: logs as unknown as Record<string, unknown>[],
columns: columns as ColumnDef<Record<string, unknown>>[],
state: {
columnFilters,
+1 -1
View File
@@ -4,7 +4,7 @@ import {
parseTiersFromExpr,
type ParsedTier,
} from '@/features/pricing/lib/billing-expr'
import type { UsageLog } from '../data/schema'
import type { UsageLog } from '../usage-log-schema'
import type { LogOtherData } from '../types'
const PARAM_OVERRIDE_ACTION_MAP: Record<string, string> = {
+1 -1
View File
@@ -1,7 +1,7 @@
/**
* Type definitions for usage logs
*/
import type { UsageLog } from './data/schema'
import type { UsageLog } from './usage-log-schema'
// ============================================================================
// Log Category Types
@@ -0,0 +1,24 @@
/**
* API row shape for common (chat/relay) usage logs from the Manager backend.
* Kept permissive: optional fields mirror partial responses and legacy rows.
*/
export interface UsageLog {
id?: number
user_id: number
username?: string
type: number
channel: number
channel_name?: string
token_name?: string
model_name: string
group?: string
other: string
quota: number
use_time: number
prompt_tokens: number
completion_tokens: number
is_stream: boolean
request_id?: string
content?: string
ip?: string
}
+1 -1
View File
@@ -21,7 +21,7 @@ import { type SidebarData } from '@/components/layout/types'
* - 平台是管理后台:登录后默认仅展示 Code delivery cockpit + 个人入口;
* - 不再向普通用户暴露 Playground / API Keys / Models 等开发者控制台条目;
* - Usage logs 作为交付链路的一环,归并进 Code delivery 分组;
* - Git sources:SK 正文以 Git 为准;此处仅登记连接与展示运行时解析锚点(commit / 制品),不提供正文编辑;
* - Git sources:先绑定代码与 SK 工具仓库并分配子 Agent 云上权限,部署后在此查看快照锚点;SK 正文仍以 Git 为准,不提供 Markdown 编辑;
* - 所有 admin/root 管理类入口(Channels/Models/Tenants/Redemption/...)
* 收纳进 "系统设置" workspace(点击进入 /system-settings 后才出现)。
*
+13 -7
View File
@@ -1605,10 +1605,16 @@
"Get Started": "Get Started",
"Git binding": "Git binding",
"Git sources": "Git sources",
"Git sources binding explainer": "Skill (SK) content lives in Git. Manager does not edit Markdown here—register repository connections and refs via the Heicode client or your deployment plan sk_sources. Below lists immutable snapshot anchors (Git commit / upload artifact) resolved for auditing.",
"Git sources subtitle": "Bind Git repositories for SK, then review immutable snapshot anchors tied to each deployment.",
"Git sources binding explainer": "Skill (SK) definitions live in Git. Manager does not edit Markdown here—register code repos, SK tool repos, and refs via the Heicode client or your deployment plan sk_sources. Allocate cloud permissions for sub-agents (VMs, roles, scopes) in the same plan; deploy sub-agents after bindings exist so each run inherits allow/deny SK policy. Below lists immutable snapshot anchors (Git commit / upload artifact) resolved for auditing.",
"Git sources subtitle": "Bind Git code and SK tool repositories, attach cloud permissions for sub-agents, deploy, then review snapshot anchors per deployment.",
"Git sources workflow title": "Typical setup flow",
"Git sources workflow step 1": "Bind your team’s Git repositories that hold application code and delivery context.",
"Git sources workflow step 2": "Bind SK tool repositories (skills registry) your tenant is allowed to draw from.",
"Git sources workflow step 3": "Allocate cloud capacity and permissions for sub-agents—for example dedicated VMs, roles, and API scopes.",
"Git sources workflow step 4": "Deploy sub-agents; the deployment wires bound sources and policies into that run.",
"Git sources workflow step 5": "After deployment, each sub-agent receives its effective SK allow / deny policy from the control plane.",
"Git-backed SK sources": "Git-backed SK sources",
"Git-backed SK sources description": "Immutable snapshots from bound Git refs and uploads—wired into each run for audit.",
"Git-backed SK sources description": "Bind repos and capacity first; immutable snapshots after each deployment show which SK lineage actually ran under tenant policy.",
"GitHub": "GitHub",
"Give the group a recognizable name and optional description.": "Give the group a recognizable name and optional description.",
"Give this group a recognizable name.": "Give this group a recognizable name.",
@@ -1775,7 +1781,7 @@
"Inspect": "Inspect",
"Inspect events": "Inspect events",
"Inspect Git sources": "Inspect Git sources",
"Inspect Git sources description": "Review resolved anchors (commit / artifact hash) from your bound repositories.",
"Inspect Git sources description": "Follow bind → allocate cloud permissions → deploy, then review anchors and lineage for each deployment.",
"Inspect SK lineage": "Inspect SK lineage",
"Inspect user prompts": "Inspect user prompts",
"Instance": "Instance",
@@ -2176,9 +2182,9 @@
"No deployment available for events.": "No deployment available for events.",
"No deployment available for SK snapshots.": "No deployment available for SK snapshots.",
"No deployment for Git sources": "No deployment selected yet",
"No deployment for Git sources hint": "Create a deployment whose plan includes sk_sources pointing at your Git repository—resolved anchors will appear here.",
"No deployment for Git sources hint": "Finish binding code/SK repos and sub-agent cloud permissions in your plan, then create a deployment—resolved anchors appear here.",
"No resolved snapshots yet": "No resolved snapshots yet",
"No resolved snapshots hint": "Resolve snapshots from the control plane after Git-backed sk_sources are configured.",
"No resolved snapshots hint": "Once repos, cloud permissions, and deployment are in place, the control plane resolves snapshot anchors for auditing.",
"No deployments available. Create one to get started.": "No deployments available. Create one to get started.",
"No Deployments Found": "No Deployments Found",
"No deployments match the current filter": "No deployments match the current filter",
@@ -3106,7 +3112,7 @@
"Sign in": "Sign in",
"Sign In": "Sign In",
"Sign in to operate Agnet deployments, inspect events, and audit SK snapshots for every tenant under your account.": "Sign in to operate Agnet deployments, inspect events, and audit SK snapshots for every tenant under your account.",
"Sign in to operate deployments and review Git-bound snapshot anchors for tenants under your account.": "Sign in to operate deployments and review Git-bound snapshot anchors for tenants under your account.",
"Sign in to operate deployments and review Git-bound snapshot anchors for tenants under your account.": "Sign in to bind repositories and cloud permissions, deploy sub-agents, and review Git-bound snapshot anchors for tenants under your account.",
"Sign in to your workspace": "Sign in to your workspace",
"Sign in with Passkey": "Sign in with Passkey",
"Sign out": "Sign out",
+13 -7
View File
@@ -1605,10 +1605,16 @@
"Get Started": "Commencer",
"Git binding": "Git binding",
"Git sources": "Git sources",
"Git sources binding explainer": "Skill (SK) content lives in Git. Manager does not edit Markdown here—register repository connections and refs via the Heicode client or your deployment plan sk_sources. Below lists immutable snapshot anchors (Git commit / upload artifact) resolved for auditing.",
"Git sources subtitle": "Bind Git repositories for SK, then review immutable snapshot anchors tied to each deployment.",
"Git sources binding explainer": "Skill (SK) definitions live in Git. Manager does not edit Markdown here—register code repos, SK tool repos, and refs via the Heicode client or your deployment plan sk_sources. Allocate cloud permissions for sub-agents (VMs, roles, scopes) in the same plan; deploy sub-agents after bindings exist so each run inherits allow/deny SK policy. Below lists immutable snapshot anchors (Git commit / upload artifact) resolved for auditing.",
"Git sources subtitle": "Bind Git code and SK tool repositories, attach cloud permissions for sub-agents, deploy, then review snapshot anchors per deployment.",
"Git sources workflow title": "Typical setup flow",
"Git sources workflow step 1": "Bind your team’s Git repositories that hold application code and delivery context.",
"Git sources workflow step 2": "Bind SK tool repositories (skills registry) your tenant is allowed to draw from.",
"Git sources workflow step 3": "Allocate cloud capacity and permissions for sub-agents—for example dedicated VMs, roles, and API scopes.",
"Git sources workflow step 4": "Deploy sub-agents; the deployment wires bound sources and policies into that run.",
"Git sources workflow step 5": "After deployment, each sub-agent receives its effective SK allow / deny policy from the control plane.",
"Git-backed SK sources": "Git-backed SK sources",
"Git-backed SK sources description": "Immutable snapshots from bound Git refs and uploads—wired into each run for audit.",
"Git-backed SK sources description": "Bind repos and capacity first; immutable snapshots after each deployment show which SK lineage actually ran under tenant policy.",
"GitHub": "GitHub",
"Give the group a recognizable name and optional description.": "Donnez au groupe un nom reconnaissable et une description facultative.",
"Give this group a recognizable name.": "Donnez un nom reconnaissable à ce groupe.",
@@ -1775,7 +1781,7 @@
"Inspect": "Inspect",
"Inspect events": "Inspect events",
"Inspect Git sources": "Inspect Git sources",
"Inspect Git sources description": "Review resolved anchors (commit / artifact hash) from your bound repositories.",
"Inspect Git sources description": "Follow bind → allocate cloud permissions → deploy, then review anchors and lineage for each deployment.",
"Inspect SK lineage": "Inspect SK lineage",
"Inspect user prompts": "Inspecter les invites utilisateur",
"Instance": "Instance",
@@ -2176,9 +2182,9 @@
"No deployment available for events.": "No deployment available for events.",
"No deployment available for SK snapshots.": "No deployment available for SK snapshots.",
"No deployment for Git sources": "No deployment selected yet",
"No deployment for Git sources hint": "Create a deployment whose plan includes sk_sources pointing at your Git repository—resolved anchors will appear here.",
"No deployment for Git sources hint": "Finish binding code/SK repos and sub-agent cloud permissions in your plan, then create a deployment—resolved anchors appear here.",
"No resolved snapshots yet": "No resolved snapshots yet",
"No resolved snapshots hint": "Resolve snapshots from the control plane after Git-backed sk_sources are configured.",
"No resolved snapshots hint": "Once repos, cloud permissions, and deployment are in place, the control plane resolves snapshot anchors for auditing.",
"No deployments available. Create one to get started.": "Aucun déploiement disponible. Créez-en un pour commencer.",
"No Deployments Found": "Aucun déploiement trouvé",
"No deployments match the current filter": "No deployments match the current filter",
@@ -3106,7 +3112,7 @@
"Sign in": "Se connecter",
"Sign In": "Se connecter",
"Sign in to operate Agnet deployments, inspect events, and audit SK snapshots for every tenant under your account.": "Sign in to operate Agnet deployments, inspect events, and audit SK snapshots for every tenant under your account.",
"Sign in to operate deployments and review Git-bound snapshot anchors for tenants under your account.": "Sign in to operate deployments and review Git-bound snapshot anchors for tenants under your account.",
"Sign in to operate deployments and review Git-bound snapshot anchors for tenants under your account.": "Sign in to bind repositories and cloud permissions, deploy sub-agents, and review Git-bound snapshot anchors for tenants under your account.",
"Sign in to your workspace": "Sign in to your workspace",
"Sign in with Passkey": "Se connecter avec Passkey",
"Sign out": "Se déconnecter",
+13 -7
View File
@@ -1605,10 +1605,16 @@
"Get Started": "開始する",
"Git binding": "Git binding",
"Git sources": "Git sources",
"Git sources binding explainer": "Skill (SK) content lives in Git. Manager does not edit Markdown here—register repository connections and refs via the Heicode client or your deployment plan sk_sources. Below lists immutable snapshot anchors (Git commit / upload artifact) resolved for auditing.",
"Git sources subtitle": "Bind Git repositories for SK, then review immutable snapshot anchors tied to each deployment.",
"Git sources binding explainer": "Skill (SK) definitions live in Git. Manager does not edit Markdown here—register code repos, SK tool repos, and refs via the Heicode client or your deployment plan sk_sources. Allocate cloud permissions for sub-agents (VMs, roles, scopes) in the same plan; deploy sub-agents after bindings exist so each run inherits allow/deny SK policy. Below lists immutable snapshot anchors (Git commit / upload artifact) resolved for auditing.",
"Git sources subtitle": "Bind Git code and SK tool repositories, attach cloud permissions for sub-agents, deploy, then review snapshot anchors per deployment.",
"Git sources workflow title": "Typical setup flow",
"Git sources workflow step 1": "Bind your team’s Git repositories that hold application code and delivery context.",
"Git sources workflow step 2": "Bind SK tool repositories (skills registry) your tenant is allowed to draw from.",
"Git sources workflow step 3": "Allocate cloud capacity and permissions for sub-agents—for example dedicated VMs, roles, and API scopes.",
"Git sources workflow step 4": "Deploy sub-agents; the deployment wires bound sources and policies into that run.",
"Git sources workflow step 5": "After deployment, each sub-agent receives its effective SK allow / deny policy from the control plane.",
"Git-backed SK sources": "Git-backed SK sources",
"Git-backed SK sources description": "Immutable snapshots from bound Git refs and uploads—wired into each run for audit.",
"Git-backed SK sources description": "Bind repos and capacity first; immutable snapshots after each deployment show which SK lineage actually ran under tenant policy.",
"GitHub": "GitHub",
"Give the group a recognizable name and optional description.": "グループに認識しやすい名前とオプションの説明を付けます。",
"Give this group a recognizable name.": "このグループに認識しやすい名前を付けます。",
@@ -1775,7 +1781,7 @@
"Inspect": "Inspect",
"Inspect events": "Inspect events",
"Inspect Git sources": "Inspect Git sources",
"Inspect Git sources description": "Review resolved anchors (commit / artifact hash) from your bound repositories.",
"Inspect Git sources description": "Follow bind → allocate cloud permissions → deploy, then review anchors and lineage for each deployment.",
"Inspect SK lineage": "Inspect SK lineage",
"Inspect user prompts": "ユーザープロンプトの検査",
"Instance": "インスタンス",
@@ -2176,9 +2182,9 @@
"No deployment available for events.": "No deployment available for events.",
"No deployment available for SK snapshots.": "No deployment available for SK snapshots.",
"No deployment for Git sources": "No deployment selected yet",
"No deployment for Git sources hint": "Create a deployment whose plan includes sk_sources pointing at your Git repository—resolved anchors will appear here.",
"No deployment for Git sources hint": "Finish binding code/SK repos and sub-agent cloud permissions in your plan, then create a deployment—resolved anchors appear here.",
"No resolved snapshots yet": "No resolved snapshots yet",
"No resolved snapshots hint": "Resolve snapshots from the control plane after Git-backed sk_sources are configured.",
"No resolved snapshots hint": "Once repos, cloud permissions, and deployment are in place, the control plane resolves snapshot anchors for auditing.",
"No deployments available. Create one to get started.": "利用可能なデプロイメントがありません。開始するには1つ作成してください。",
"No Deployments Found": "デプロイメントが見つかりません",
"No deployments match the current filter": "No deployments match the current filter",
@@ -3106,7 +3112,7 @@
"Sign in": "ログイン",
"Sign In": "ログイン",
"Sign in to operate Agnet deployments, inspect events, and audit SK snapshots for every tenant under your account.": "Sign in to operate Agnet deployments, inspect events, and audit SK snapshots for every tenant under your account.",
"Sign in to operate deployments and review Git-bound snapshot anchors for tenants under your account.": "Sign in to operate deployments and review Git-bound snapshot anchors for tenants under your account.",
"Sign in to operate deployments and review Git-bound snapshot anchors for tenants under your account.": "Sign in to bind repositories and cloud permissions, deploy sub-agents, and review Git-bound snapshot anchors for tenants under your account.",
"Sign in to your workspace": "Sign in to your workspace",
"Sign in with Passkey": "Passkeyでログイン",
"Sign out": "ログアウト",
+13 -7
View File
@@ -1605,10 +1605,16 @@
"Get Started": "Начать",
"Git binding": "Git binding",
"Git sources": "Git sources",
"Git sources binding explainer": "Skill (SK) content lives in Git. Manager does not edit Markdown here—register repository connections and refs via the Heicode client or your deployment plan sk_sources. Below lists immutable snapshot anchors (Git commit / upload artifact) resolved for auditing.",
"Git sources subtitle": "Bind Git repositories for SK, then review immutable snapshot anchors tied to each deployment.",
"Git sources binding explainer": "Skill (SK) definitions live in Git. Manager does not edit Markdown here—register code repos, SK tool repos, and refs via the Heicode client or your deployment plan sk_sources. Allocate cloud permissions for sub-agents (VMs, roles, scopes) in the same plan; deploy sub-agents after bindings exist so each run inherits allow/deny SK policy. Below lists immutable snapshot anchors (Git commit / upload artifact) resolved for auditing.",
"Git sources subtitle": "Bind Git code and SK tool repositories, attach cloud permissions for sub-agents, deploy, then review snapshot anchors per deployment.",
"Git sources workflow title": "Typical setup flow",
"Git sources workflow step 1": "Bind your team’s Git repositories that hold application code and delivery context.",
"Git sources workflow step 2": "Bind SK tool repositories (skills registry) your tenant is allowed to draw from.",
"Git sources workflow step 3": "Allocate cloud capacity and permissions for sub-agents—for example dedicated VMs, roles, and API scopes.",
"Git sources workflow step 4": "Deploy sub-agents; the deployment wires bound sources and policies into that run.",
"Git sources workflow step 5": "After deployment, each sub-agent receives its effective SK allow / deny policy from the control plane.",
"Git-backed SK sources": "Git-backed SK sources",
"Git-backed SK sources description": "Immutable snapshots from bound Git refs and uploads—wired into each run for audit.",
"Git-backed SK sources description": "Bind repos and capacity first; immutable snapshots after each deployment show which SK lineage actually ran under tenant policy.",
"GitHub": "GitHub",
"Give the group a recognizable name and optional description.": "Дайте группе узнаваемое имя и необязательное описание.",
"Give this group a recognizable name.": "Дайте этой группе узнаваемое имя.",
@@ -1775,7 +1781,7 @@
"Inspect": "Inspect",
"Inspect events": "Inspect events",
"Inspect Git sources": "Inspect Git sources",
"Inspect Git sources description": "Review resolved anchors (commit / artifact hash) from your bound repositories.",
"Inspect Git sources description": "Follow bind → allocate cloud permissions → deploy, then review anchors and lineage for each deployment.",
"Inspect SK lineage": "Inspect SK lineage",
"Inspect user prompts": "Просмотр запросов пользователя",
"Instance": "Экземпляр",
@@ -2176,9 +2182,9 @@
"No deployment available for events.": "No deployment available for events.",
"No deployment available for SK snapshots.": "No deployment available for SK snapshots.",
"No deployment for Git sources": "No deployment selected yet",
"No deployment for Git sources hint": "Create a deployment whose plan includes sk_sources pointing at your Git repository—resolved anchors will appear here.",
"No deployment for Git sources hint": "Finish binding code/SK repos and sub-agent cloud permissions in your plan, then create a deployment—resolved anchors appear here.",
"No resolved snapshots yet": "No resolved snapshots yet",
"No resolved snapshots hint": "Resolve snapshots from the control plane after Git-backed sk_sources are configured.",
"No resolved snapshots hint": "Once repos, cloud permissions, and deployment are in place, the control plane resolves snapshot anchors for auditing.",
"No deployments available. Create one to get started.": "Нет доступных развертываний. Создайте одно, чтобы начать.",
"No Deployments Found": "Развертывания не найдены",
"No deployments match the current filter": "No deployments match the current filter",
@@ -3106,7 +3112,7 @@
"Sign in": "Войти",
"Sign In": "Войти",
"Sign in to operate Agnet deployments, inspect events, and audit SK snapshots for every tenant under your account.": "Sign in to operate Agnet deployments, inspect events, and audit SK snapshots for every tenant under your account.",
"Sign in to operate deployments and review Git-bound snapshot anchors for tenants under your account.": "Sign in to operate deployments and review Git-bound snapshot anchors for tenants under your account.",
"Sign in to operate deployments and review Git-bound snapshot anchors for tenants under your account.": "Sign in to bind repositories and cloud permissions, deploy sub-agents, and review Git-bound snapshot anchors for tenants under your account.",
"Sign in to your workspace": "Sign in to your workspace",
"Sign in with Passkey": "Войти с Passkey",
"Sign out": "Выйти",
+13 -7
View File
@@ -1605,10 +1605,16 @@
"Get Started": "Bắt đầu",
"Git binding": "Git binding",
"Git sources": "Git sources",
"Git sources binding explainer": "Skill (SK) content lives in Git. Manager does not edit Markdown here—register repository connections and refs via the Heicode client or your deployment plan sk_sources. Below lists immutable snapshot anchors (Git commit / upload artifact) resolved for auditing.",
"Git sources subtitle": "Bind Git repositories for SK, then review immutable snapshot anchors tied to each deployment.",
"Git sources binding explainer": "Skill (SK) definitions live in Git. Manager does not edit Markdown here—register code repos, SK tool repos, and refs via the Heicode client or your deployment plan sk_sources. Allocate cloud permissions for sub-agents (VMs, roles, scopes) in the same plan; deploy sub-agents after bindings exist so each run inherits allow/deny SK policy. Below lists immutable snapshot anchors (Git commit / upload artifact) resolved for auditing.",
"Git sources subtitle": "Bind Git code and SK tool repositories, attach cloud permissions for sub-agents, deploy, then review snapshot anchors per deployment.",
"Git sources workflow title": "Typical setup flow",
"Git sources workflow step 1": "Bind your team’s Git repositories that hold application code and delivery context.",
"Git sources workflow step 2": "Bind SK tool repositories (skills registry) your tenant is allowed to draw from.",
"Git sources workflow step 3": "Allocate cloud capacity and permissions for sub-agents—for example dedicated VMs, roles, and API scopes.",
"Git sources workflow step 4": "Deploy sub-agents; the deployment wires bound sources and policies into that run.",
"Git sources workflow step 5": "After deployment, each sub-agent receives its effective SK allow / deny policy from the control plane.",
"Git-backed SK sources": "Git-backed SK sources",
"Git-backed SK sources description": "Immutable snapshots from bound Git refs and uploads—wired into each run for audit.",
"Git-backed SK sources description": "Bind repos and capacity first; immutable snapshots after each deployment show which SK lineage actually ran under tenant policy.",
"GitHub": "GitHub",
"Give the group a recognizable name and optional description.": "Đặt cho nhóm một cái tên dễ nhận biết và mô tả tùy chọn.",
"Give this group a recognizable name.": "Hãy đặt cho nhóm này một cái tên dễ nhận biết.",
@@ -1775,7 +1781,7 @@
"Inspect": "Inspect",
"Inspect events": "Inspect events",
"Inspect Git sources": "Inspect Git sources",
"Inspect Git sources description": "Review resolved anchors (commit / artifact hash) from your bound repositories.",
"Inspect Git sources description": "Follow bind → allocate cloud permissions → deploy, then review anchors and lineage for each deployment.",
"Inspect SK lineage": "Inspect SK lineage",
"Inspect user prompts": "Kiểm tra lời nhắc của người dùng",
"Instance": "Phiên bản",
@@ -2176,9 +2182,9 @@
"No deployment available for events.": "No deployment available for events.",
"No deployment available for SK snapshots.": "No deployment available for SK snapshots.",
"No deployment for Git sources": "No deployment selected yet",
"No deployment for Git sources hint": "Create a deployment whose plan includes sk_sources pointing at your Git repository—resolved anchors will appear here.",
"No deployment for Git sources hint": "Finish binding code/SK repos and sub-agent cloud permissions in your plan, then create a deployment—resolved anchors appear here.",
"No resolved snapshots yet": "No resolved snapshots yet",
"No resolved snapshots hint": "Resolve snapshots from the control plane after Git-backed sk_sources are configured.",
"No resolved snapshots hint": "Once repos, cloud permissions, and deployment are in place, the control plane resolves snapshot anchors for auditing.",
"No deployments available. Create one to get started.": "Không có triển khai nào khả dụng. Tạo một cái để bắt đầu.",
"No Deployments Found": "Không tìm thấy triển khai nào",
"No deployments match the current filter": "No deployments match the current filter",
@@ -3106,7 +3112,7 @@
"Sign in": "Đăng nhập",
"Sign In": "Đăng nhập",
"Sign in to operate Agnet deployments, inspect events, and audit SK snapshots for every tenant under your account.": "Sign in to operate Agnet deployments, inspect events, and audit SK snapshots for every tenant under your account.",
"Sign in to operate deployments and review Git-bound snapshot anchors for tenants under your account.": "Sign in to operate deployments and review Git-bound snapshot anchors for tenants under your account.",
"Sign in to operate deployments and review Git-bound snapshot anchors for tenants under your account.": "Sign in to bind repositories and cloud permissions, deploy sub-agents, and review Git-bound snapshot anchors for tenants under your account.",
"Sign in to your workspace": "Sign in to your workspace",
"Sign in with Passkey": "Đăng nhập bằng Passkey",
"Sign out": "Đăng xuất",
+13 -7
View File
@@ -1605,10 +1605,16 @@
"Get Started": "开始使用",
"Git binding": "Git 绑定",
"Git sources": "Git 来源",
"Git sources binding explainer": "Skill(SK)正文以 Git 仓库为唯一事实源。Manager 不在此编辑 Markdown:请在 Heicode 客户端或部署计划的 sk_sources 中登记仓库连接与引用。下列为运行时解析得到的不可变快照锚点(Git commit / 上传制品),供审计追溯。",
"Git sources subtitle": "为 SK 绑定 Git 仓库后,在此查看与各次部署关联的快照锚点。",
"Git sources binding explainer": "Skill(SK)定义以 Git 为唯一事实源。Manager 不在此编辑 Markdown:请在 Heicode 客户端或部署计划的 sk_sources 中登记代码仓库、SK 工具仓库与引用;并在同一计划中为子 Agent 分配云上权限(虚拟机、角色、API 范围等)。完成绑定后再部署子 Agent,使每次运行继承允许的 SK 与被禁止的 SK 策略。下列为运行时解析得到的不可变快照锚点(Git commit / 上传制品),供审计追溯。",
"Git sources subtitle": "绑定代码与 SK 工具仓库、为子 Agent 分配云上权限并部署后,在此按部署查看快照锚点。",
"Git sources workflow title": "典型配置顺序",
"Git sources workflow step 1": "绑定团队用于应用代码与交付上下文的 Git 仓库。",
"Git sources workflow step 2": "绑定 SK 工具仓库(技能来源),声明租户可引用的工具集。",
"Git sources workflow step 3": "为子 Agent 分配云上资源与权限(如独立虚拟机、角色与其他访问边界)。",
"Git sources workflow step 4": "部署子 Agent;部署会把已绑定的来源与策略写入该次运行。",
"Git sources workflow step 5": "部署完成后,子 Agent 从控制面获知生效的允许 SK 与禁止 SK。",
"Git-backed SK sources": "基于 Git 的 SK 来源",
"Git-backed SK sources description": "来自已绑定 Git 引用与上传制品的不可变快照,并注入每次运行以供审计。",
"Git-backed SK sources description": "先完成仓库与云上能力绑定;每次部署后的不可变快照反映在该租户策略下实际运行的 SK 血缘。",
"GitHub": "GitHub",
"Give the group a recognizable name and optional description.": "为该分组提供一个可识别的名称和可选的描述。",
"Give this group a recognizable name.": "为此分组提供一个可识别的名称。",
@@ -1775,7 +1781,7 @@
"Inspect": "查看",
"Inspect events": "查看事件",
"Inspect Git sources": "查看 Git 来源与快照",
"Inspect Git sources description": "查看已绑定仓库解析出的锚点(commit / 制品哈希)。",
"Inspect Git sources description": "按「绑定 → 分配云上权限 → 部署」完成后,在此查看各次部署的锚点与血缘。",
"Inspect SK lineage": "追溯 SK 血缘",
"Inspect user prompts": "检查用户提示",
"Instance": "实例",
@@ -2176,9 +2182,9 @@
"No deployment available for events.": "暂无可查看事件的部署。",
"No deployment available for SK snapshots.": "暂无可查看 SK 快照的部署。",
"No deployment for Git sources": "暂无可关联的部署",
"No deployment for Git sources hint": "请在编排计划的 sk_sources 中指向 Git 仓库并创建部署后,此处会显示解析锚点。",
"No deployment for Git sources hint": "在计划中完成代码/SK 仓库与子 Agent 云上权限的配置并创建部署后,此处会显示解析锚点。",
"No resolved snapshots yet": "尚无已解析的快照",
"No resolved snapshots hint": "在配置好基于 Git 的来源后,由控制面触发快照解析即可在此查看。",
"No resolved snapshots hint": "仓库、云上权限与部署就绪后,由控制面解析快照锚点即可在此审计追溯。",
"No deployments available. Create one to get started.": "没有可用的部署。创建一个开始吧。",
"No Deployments Found": "未找到部署",
"No deployments match the current filter": "没有符合当前筛选条件的部署",
@@ -3106,7 +3112,7 @@
"Sign in": "登录",
"Sign In": "登录",
"Sign in to operate Agnet deployments, inspect events, and audit SK snapshots for every tenant under your account.": "登录后即可操作 Agnet 部署、查看事件,并审计你账号下各租户的 SK 快照。",
"Sign in to operate deployments and review Git-bound snapshot anchors for tenants under your account.": "登录后即可操作部署、查看事件,并审阅你账号下各租户与 Git 绑定的快照锚点。",
"Sign in to operate deployments and review Git-bound snapshot anchors for tenants under your account.": "登录后即可绑定仓库与云上权限、部署子 Agent,并审阅你账号下各租户与 Git 绑定的快照锚点。",
"Sign in to your workspace": "登录到你的工作空间",
"Sign in with Passkey": "使用 Passkey 登录",
"Sign out": "登出",