Commit Graph
8 Commits
Author SHA1 Message Date
yeuimu d81d14bd52 docs(skill): 去除全部 localhost:3003 —— 一律使用公网地址 table.inkreach.cc
skill 面向公开分发,不应包含部署机内网地址。SKILL.md / cli-reference /
rest-api / instance-access 共 10 处替换;rest-api 双源表与 ssh 隧道
兜底整段删除(前端 rewrite 已让域名全功能可用)。
2026-09-23 05:54:15 +00:00
yeuimu 8499de27e6 docs(skill): swagger is a curated registry — audit-verified gaps both ways
Cross-diff of all @Controller routes vs docs-json (486 vs 438 after shape
normalization): real undocumented routes include the entire authority-matrix
family (live 200, 0 doc entries), select-visibility, plugin runtime/proxy,
ShareDB socket internals, oauth-server, health; ~27 doc entries belong to
the enterprise backend and 404 on this CE instance. Completeness check =
controller grep, docs-json alone is not exhaustive.
2026-09-23 05:43:13 +00:00
yeuimu 20c1e48193 docs(skill): swagger now reachable on the public domain (frontend rewrite) 2026-09-23 05:39:01 +00:00
yeuimu c5e291a7cf fix(skill): public domain 404s swagger — origin-aware base URL + discovery
Verified live: https://table.inkreach.cc/docs-json and /docs → 404
(frontend doesn't proxy swagger paths), while /api/* IS proxied
(PAT auth → 200). Guide now: two-origin table (domain for API calls,
backend origin for swagger), ssh-tunnel fallback for remote machines,
backend-controller grep as last resort; instance-access.md connection
table gains the public-domain row.
2026-09-23 05:33:35 +00:00
yeuimu 3df9225a68 docs(skill): full-route honesty — ~362 backend paths, core documented, rest via /docs-json
Audit vs live swagger: guide covers the CLI-mirrored operational core;
added verified aggregation/row-count + a full inventory section pointing
to the unauthenticated /docs-json spec for the ~35 uncovered groups
(auth/session, user, spaces, share, attachments, import/export, trash,
templates, org/oauth/admin/billing, official webhooks, plugin UI…).
2026-09-23 05:29:11 +00:00
yeuimu 2530eea8b5 feat(skill): teach direct REST API usage — api-reference/rest-api.md
Comprehensive review found the skill taught CLI-only usage (just one
script-action callback snippet); nothing on calling the API directly.

New guide (verified against the live instance):
- base URL + Bearer PAT auth, Node v24 fetch header-drop warning
- full endpoint map mirrored from the CLI's HTTP layer (records/fields/
  tables/views/presets/workflow/secrets/executions/fire/sql/PAT/signup)
- canonical curl examples incl. typecast/fieldKeyType bodies, url-encoded
  filter, convert-for-options, workflow node PUT + activate, script-action
  callback via triggerInput._apiBaseUrl
- gotchas: typecast never creates choices (silent no-op), visibilityFilter
  400, PATCH field strips options, whole-graph node replace, search[] tuple

SKILL.md: module table row + routing rule wired to the new guide.
2026-09-23 05:20:14 +00:00
yeuimu eefdceffe8 docs: npx-based install (verified) — CLI via git+https, skill via skills add
- CLI: npx git+https://... (ad-hoc) / npm i -g git+https://... (permanent)
- skill: npx -y skills add https://... -g -y --copy (installs to
  ~/.zcode/skills + ~/.claude/skills + ~/.agents/skills + ~40 agents)
- prefix trap documented: npm/npx NEED git+, skills add must NOT have it
- install.sh kept as offline/no-npm fallback
2026-09-23 04:39:15 +00:00
yeuimu 76ef02d659 refactor: move skill to skills/inkreach-teable (from .agents/skills/)
git mv rename (history preserved); install.sh + README updated.
The skill is consumed via user-level install (~/.zcode/skills), so
in-repo .agents discovery was unnecessary.
2026-09-23 04:07:39 +00:00