Publish Customer Management v0.2.0: selected-sources-only agent template - #96
Merged
Merged
Conversation
Syncs the bundle with firstlanding #10014 (merged 2026-08-13): the per-customer agent's knowledge_search moves from scope ["agent", "org"] to scope [] with an explicit customer-public-docs source_ref, backed by a new web/site installation carrying that install_key. Each stamped customer gets its own selected source copy and no broad corpus grant. Publish gate: production was promoted 2026-08-14T00:23Z with the platform code that accepts this shape (pre-#10014 code rejects scope []), so this is safe to release now. Acceptance: one fresh catalog install must provision an agent whose knowledge tool is scope [] + a per-customer source (firstlanding #10000, R2). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
All three CI failures shared this root cause: sample.yaml is the release version the automation cuts tarballs from, and it must match solution.yaml's solution_version. samples.json is generated (archastro create solutionmanifest) and now verifies drift-clean against the bumped source. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Review on ArchCode
Problem and author intent
This is R2 of the #9448 PR-1 rollout (tracked on firstlanding ArchAstro/firstlanding#10000): the prod catalog's Customer Management bundle predates firstlanding ArchAstro/firstlanding#10014, so every fresh catalog install still provisions per-customer agents with the broad
scope: ["agent", "org"]knowledge grant. This republish makes new installs provision selected-sources-only agents.What changed
solutions/customer-management/agents/customer-management.yaml— synced byte-for-byte with the firstlanding sample as merged in ArchAstro/firstlanding#10014:knowledge_searchbecomesscope: []+source_refs: [customer-public-docs], and aweb/siteinstallation withinstall_key: customer-public-docs(docs.archagents.com, max 100 pages) backs that ref. Each stamped customer gets its own copy of the source and no broad corpus.solution.yaml—solution_versionv0.1.0 → v0.2.0.samples.json—current_versionv0.1.0 → v0.2.0 (this line is what the release pipeline keys on).Nothing else in the bundle differs from what is already published.
Publish gate (why this is safe to merge now)
Pre-#10014 platform code rejects
scope: []at provisioning. Production was promoted 2026-08-14T00:23Z with the accepting code (image20260813T224131Z-gb27701836d7a, contains ArchAstro/firstlanding#10014 and ArchAstro/firstlanding#10066), so the gate is satisfied — merging this now cannot produce failed installs.Scope / risk
Catalog-content only; no code. Low risk, new installs only — existing installs and already-stamped customer agents are untouched (the existing live install is the separate R3, firstlanding ArchAstro/firstlanding#10053).
Acceptance test (R2's verification, after the pipeline publishes)
One fresh install of the Customer Management solution from the prod catalog, then inspect the provisioned agent: its
knowledge_searchtool must bescope: []with a per-customersource_idsentry resolving to that install's owncustomer-public-docssource — not["agent", "org"]. This mirrors the canonical proof in firstlanding (customer_management_solution_install_test.exs), now against the real published artifact.🤖 Generated with Claude Code