gitea-admin/CASAN
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
212 Commits 1 Branch 0 Tags
main
Commit Graph
7 Commits
Author SHA1 Message Date
thanhnv 06c404084d feat(casan): add native plugin facade
CASAN Supply Chain and Provenance / verify-scan-attest (push) Canceled after 0s
Details
CASAN CI Gate / Frontend Tests (H3 gate) (push) Canceled after 0s
Details
CASAN CI Gate / CASAN Security Gate + Vault KMS (H4/H5) (push) Canceled after 0s
Details
CASAN CI Gate / Build & Deploy OKR → /opt/webapps/okr (push) Canceled after 0s
Details
CASAN Harness CI / harness (push) Canceled after 0s
Details
2026-08-18 16:26:27 +07:00
thanhnv 9c9efb1043 feat: ship production local assurance viewer in core 2026-07-28 23:09:22 +07:00
thanhnv cce3cbfd42 feat: add production assurance dashboard flow 2026-07-28 21:49:15 +07:00
thanhnv 114340c719 feat: harden CASAN production install lifecycle 2026-07-24 11:11:44 +07:00
thanhnv 881ee01691 feat: prepare CASAN paid PoC release package 2026-07-18 00:07:04 +07:00
thanhnv 3be9970c15 feat: add control panel 2026-07-08 19:07:35 +09:00
thanhnvandClaude Opus 4.8 8c20cfde9f feat(packaging): level-based source hub — Core + DevKit packaging, Platform/Enterprise scaffold 
Organize CASAN as a reusable source hub with SPLIT releases so downstream adopts only the
level it needs (packaging/levels.json is the single source of truth).

Implemented now:
- Level 1 Core: bin/casan CLI (run/gate/test/verify/reuse/dashboard) + VERSION.
- Level 2 DevKit: packages/casan-devkit (install.sh, Dockerfile.harness, templates:
  project scaffold, domain-pack, gitea-workflow).
- scripts/package-release.sh core|devkit|platform|all-in-one-demo — builds split bundles
  into dist/ (BUNDLE-MANIFEST + SHA256SUMS); platform is stamped PREVIEW/INCOMPLETE;
  enterprise (future) is REFUSED (exit 3, no fake-complete package). Bundles verified:
  extract → bin/casan works, deterministic + domain suites pass, casan reuse VALID.
- docs/packaging: CASAN_PACKAGING_PLAN + ADOPTION + CI + DOMAIN_PACK + GITEA_PACKAGE + DOCKER.

Structure + docs only:
- Level 3 packages/casan-platform (dashboard exists; control-panel/viewers pending).
- Level 4 packages/casan-enterprise (RBAC/tenant/KMS/WORM/approval exist in core; governed
  console pending). No Chat Console/RBAC-console/tenant-console/model-mgmt built in this task.

Harness change (enables extracted bundles to self-resolve): casan-paths.sh + the Python
project_root() walk-ups now accept a second root marker `packages/casan-harness` in addition
to `.specify`, so a freshly-unpacked core/devkit/demo bundle (no `.specify` yet) roots
correctly and creates state on first run. In an adopted repo `.specify` still matches first.
policy-bundle.yaml paths corrected to packages/casan-harness (re-signed). Full gate 64/0/3.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-07-08 15:55:37 +09:00