Repository navigation
Conversation
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.
Adds a bounded, trusted SDK hook for business activity notices. Commits an activity event with the exact business revision and routes opt-in Feishu delivery through existing employee identities. Validates tenant/company/object/revision provenance, withholds credential-like summaries, and preserves gates, UUID deduplication and bounded retries.
Adds generic conversational rendering for coordinated employee replies. The discussion topic/turn comes only from immutable pinned Run input; the card leads with the actual public output summary when content sync is enabled. Metadata remains secondary and audit-friendly. Ordinary handoffs are unchanged; started/failed events do not fabricate employee dialogue. Business notices also put public summaries before audit metadata.
Validation: 81 focused Feishu tests passed, one skipped; all required GitHub checks passed. Covers immutable provenance, invalid topic/turn fields, secrets, content opt-out and preservation of ordinary collaboration cards. No business-specific workflow, public callback, group ingress or API key added. Private extension qualification separately exercised real discussion cards and independent identity delivery; no private deployment details committed here.
Additional runtime boundaries:
company_context.memory_mode=EXPLICITkeeps scheduling bindings while disabling automatic retrieval and capture. It grants no authority to read memory; trusted extensions must validate their own frozen knowledge selection.The explicit-mode code qualification passed all required CI checks, including PostgreSQL integration, Compose E2E, unit coverage, quality and CodeQL. Model/memory setup guides now explain this mode in English and Chinese. No business-specific lyric rules or private deployment configuration added to core.