feat(sight): add component-owned raw packaging - #2550
Draft
ikunkun-sys wants to merge 1 commit into
Draft
Conversation
Move AgentSight raw archive assembly into the component for immutable release artifacts. Use separate Linux and macOS contracts because their payloads and lifecycle requirements differ. Linux ships the enforcer and services; macOS intentionally ships only the AgentSight binary. Assisted-by: Codex:0.147.0 Signed-off-by: 爱鲲 <jiawa.syx@alibaba-inc.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
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.
Why
AgentSight needs a component-owned raw packaging interface so release tooling can consume immutable artifacts without duplicating Linux and macOS payload assembly. The contracts follow the actual build boundary: Linux ships full tracing and enforcement, while macOS ships trajectory and viewer functionality only.
What changed
stageandpackageentrypoints for AgentSight raw archives.agentsight-enforcer, launch script, and services only in the Linux payload.Related issue
Related: #2547 documents the CLI dry-run sidecar metadata limitation. This packaging PR follows that target-specific metadata direction but intentionally does not close the CLI issue.
User / Agent impact
Release tooling can invoke
make package-rawormake stage-rawfor:agentsight-0.10.1-linux-x86_64.tar.gzagentsight-0.10.1-macos-aarch64.tar.gzLinux packages contain AgentSight, the enforcer, launch script, and service units. macOS packages contain only the AgentSight binary and contract; enforcement remains unsupported there. Cross-target packaging requires
agentsight-build.tomlwith the target identity and binary SHA-256 values.Risk and compatibility
The Linux contract declares the existing optional eBPF capabilities and system services. The macOS contract has no capabilities, services, or enforcer. Existing source and RPM installation paths are unchanged, and release-pipeline integration remains outside this PR.
Validation
Passed:
bash src/agentsight/scripts/test-package-raw.shpython3 scripts/check-component-versions.pyshellcheck src/agentsight/packaging/raw/package.sh src/agentsight/scripts/test-package-raw.shcargo fmt --all -- --checkcargo test --quiet --workspace --tests -- --skip test_try_match_process_currentgit diff --check origin/main...HEADagentsightand the real ActPlaneagentsight-enforcerwere packaged.Known baseline failures outside this diff:
cargo clippy --workspace --all-targets -- -D warningson Rust 1.97 reportsclippy::question_markinsrc/analyzer/message/openai.rs:99.cargo test --workspacereports the existingtest_try_match_process_currentfailure and a malformed rustdoc fence insrc/genai/helpers.rs:504. All non-doctest workspace tests pass when the process-discovery test is skipped.Documentation and rollback
No documentation changed. Revert commit
4eb25aa6to remove the component-owned raw packaging interface and contracts.