Skip to content

Publish sanitized v0.4.1 public core - #8

Draft
alisanmtd-oss wants to merge 1 commit into
mainfrom
agent/publish-sanitized-v0.4.1
Draft

Publish sanitized v0.4.1 public core#8
alisanmtd-oss wants to merge 1 commit into
mainfrom
agent/publish-sanitized-v0.4.1

Conversation

@alisanmtd-oss

Copy link
Copy Markdown
Owner

What changed

  • publishes the sanitized T One v0.4.1 public core
  • adds 17 non-TikTok-Shop public knowledge-pack families and their machine-readable manifests
  • improves model/provider routing, chat-first demo behavior, workspace schema, and public capability registration
  • removes internal release-readiness and private-material provenance notes from the public tree
  • adds a hard public-tree guard against config/private_project_facts.json

Why

The previous public branch still exposed internal process/provenance documentation and did not include the completed sanitized knowledge packs. This change makes the repository's public boundary explicit and machine-verifiable without publishing store, account, browser-profile, customer, or private project facts.

Impact

Users receive the expanded public knowledge packs and safer generic runtime examples. Private project configuration remains local-only and is not part of this PR. No OAuth, store write, advertising, outreach, payment, shipment, or Amazon operation was performed.

Checks

  • python scripts/verify_public_tree.py — PASS
  • python -m unittest discover -s tests -p 'test_*.py' — 44 tests, OK
  • git diff --check — PASS
  • known private project identifiers scan — no findings in the public tree

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants