feat(report): host-declared surface meta in status reports - #280
Closed
ranxianglei wants to merge 1 commit into
Closed
ranxianglei wants to merge 1 commit into
ranxianglei wants to merge 1 commit into
Conversation
StatusReportOptions gains optional meta: { pack?, packVersion?, host? }. Overview and compressed drilldown render a leading 'ACTIVE SURFACE: pack=<name> <version> | host=<host>' line. No meta -> reports stay byte-identical (verified against pre-change code across all scope/view/sort combos). Which pack is active is host policy; the kernel only renders what the host declares.
📦 Built Package ArtifactBranch: Option A — Install from npm PR tag (recommended)In your adapter project: npm install acp-kernel@pr-280Each push to this PR publishes a new version under the Option B — Download artifact
tar xzf acp-kernel-pr280.tgz
npm install ./packageThis comment is automatically updated on each push. |
This was referenced Sep 13, 2026
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
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.
Closes #278.
What
StatusReportOptionsgains optionalmeta: { pack?, packVersion?, host? }. The overview and the compressed drilldown render a leading:No meta → reports stay byte-identical.
Design
SurfaceMetainterface +renderSurfaceLine()insrc/report.ts;SurfaceMetare-exported from the barrel (src/index.ts).pack=v3when only packVersion given); all-empty meta ({}) behaves exactly like absent meta.Verification
tsc --noEmitclean; full suite 731/731 pass (7 new tests intests/surface-meta.test.ts: no-meta byte-clean, empty-meta equivalence, overview leading line, compressed leading line, partial-meta variants ×3, uncompressed views never get the line).buildStatusReportvs new one over a fixture state (nested T1/T2 blocks + inactive block + tool messages) across all scope/view/sort/limit combos — all 8 outputs byte-identical without meta.npm run buildsucceeds.