@agent-native/core 0.99.2 → 0.100.0

package/src/templates/workspace-core/.agents/skills/context-xray/SKILL.md

@@ -20,15 +20,40 @@ counts, then lets the user or agent pin, evict, or restore individual segments.
 | Action | When to use |
 | --- | --- |
 | `context-manifest-get` | Read the current manifest for a thread. Returns token totals, segment status, source, and whether changes are enforceable. |
+| `context-preview-get` | Compose the would-be system context for the current user/org/app without a live thread. Returns labeled system sections with provenance, governance tier, token counts, and bounded previews. Backs the Agent page Context tab. |
 | `context-pin` | Preserve a segment across future compaction/model calls. Use for task specs, acceptance criteria, user constraints, and other durable context. |
 | `context-evict` | Exclude a stale or irrelevant segment from future model calls. Eviction is reversible and never deletes chat history. |
 | `context-restore` | Undo a pin, evict, or summarize directive for a segment. |
 | `context-report` | External hosts can report their visible context inventory. These manifests are advisory unless Agent-Native owns the emitted content. |
 
+## System Sections
+
+Manifests now cover the system-prompt half of context, not just conversation
+segments. Each system section carries a `provenance` label (framework-core,
+actions-prompt, template, enterprise-workspace-core, sql-workspace,
+legacy-app-default, organization, personal, memory, db-schema, tools,
+model-overlay, runtime-context) and a `governance` tier:
+
+- `required` — framework/enterprise policy; can never be altered by the user.
+- `inherited` — template/org/workspace instructions; managed elsewhere,
+  visible here.
+- `user` — personal instructions and memory; editable through Files.
+
+System sections are display-only provenance: they cannot be pinned, evicted,
+or summarized. The persisted manifest stores source refs, scope, content
+hashes, token counts, and bounded previews (~200 chars) — never raw prompt
+bodies; full content stays behind the resource/access model. The in-chat
+X-Ray panel groups these under "System", and the Agent page Context tab
+renders the full breakdown (via `context-preview-get`) with a
+system-vs-conversation split meter. Manifests are the latest snapshot per
+thread; there is no per-iteration history.
+
 ## Rules
 
 - Never evict or summarize protected segments. The manifest marks active-turn
   user/tool/thinking context as `protected`.
+- System sections are never evictable; required/inherited tiers are locked by
+  design — do not present controls that imply otherwise.
 - Prefer pinning the user's task, requirements, and decisions before evicting
   large stale tool results.
 - Eviction excludes content from future model calls; it does not delete the

package/src/templates/workspace-core/.agents/skills/external-agents/SKILL.md

@@ -28,6 +28,13 @@ For a deliberately isolated app, add that app directly at
 `https://<app>.agent-native.com/mcp` or
 `https://<your-host>/mcp`.
 
+In-app, the Agent page's **Access** tab (`/agent#access`, see the
+`agent-page` skill) is the discoverable home for all of this: it shows the
+app's copyable MCP URL and A2A agent-card URL, per-client setup steps
+(Claude, ChatGPT, Cursor, Claude Code, Codex, Other), and links to the full
+`/mcp/connect` page including the static-token fallback. Point users there
+instead of dictating URLs in chat.
+
 OAuth-capable hosts should use the standard remote MCP OAuth flow. Claude
 connectors and Claude Code `/mcp` authentication discover the protected
 resource, open the Agent-Native authorization page, and store their own tokens.

package/src/templates/workspace-core/.agents/skills/recurring-jobs/SKILL.md

@@ -29,6 +29,15 @@ Recurring jobs are scheduled tasks the agent executes automatically on a cron sc
 | `manage-jobs` | `list`     | List all jobs and their status                             |
 | `manage-jobs` | `update`   | Update schedule, instructions, or toggle enabled           |
 
+## UI Surface
+
+Users can see and manage jobs without the agent on the Agent page's Jobs tab
+(`/agent#jobs`, `AgentJobsTab` in `packages/core/src/client/agent-page/`):
+recurring jobs (personal and organization scope) with pause/resume/delete and
+run status, plus automations (personal-only today). Backed by the scoped
+list/manage actions in `packages/core/src/jobs/actions/` — direct users there
+instead of describing job files when they just want to view or toggle jobs.
+
 ## Key Files
 
 | File                                  | Purpose                                                  |