Commit Graph

24 Commits

Author SHA1 Message Date
saravanakumardb1
c9a7f905af feat(ai-ui): Wave 2 MVP @bytelyst/ai-ui@0.1.0 2026-05-27 12:07:23 -07:00
saravanakumardb1
ed5fb707ad ci(packages): close ROADMAP TODOs #5, #6 + draft RFC for #4
═══════════════════════════════════════════════════════════════════════
TODO #6 — size-limit budgets in CI
═══════════════════════════════════════════════════════════════════════
Adds .size-limit.cjs with budgets for 6 pilot @bytelyst/* packages,
plus a Gitea Actions workflow (.gitea/workflows/size-limit.yml) that
fails the build on any regression.

Current measurements vs budget (all comfortably under):
  @bytelyst/api-client       793 B  / 8 KB
  @bytelyst/auth-client     1.97 KB / 8 KB
  @bytelyst/celebrations     236 B  / 6 KB
  @bytelyst/quick-actions    122 B  / 6 KB
  @bytelyst/react-auth      2.71 KB / 10 KB
  @bytelyst/dashboard-shell 3.96 KB / 30 KB

Scripts:
  pnpm size       — measure + assert against budgets
  pnpm size:why   — explain top contributors

Deps: size-limit@^12.1.0, @size-limit/preset-small-lib@^12.1.0.

Pilot scope (this commit): 6 packages. Full @bytelyst/* rollout is
incremental — each entry added separately.

═══════════════════════════════════════════════════════════════════════
TODO #5 — Storybook canonical pattern
═══════════════════════════════════════════════════════════════════════
Discovery: @bytelyst/ui already has Storybook 8 with the @bytelyst/
addon-a11y addon configured and 5 .stories.tsx files.

This commit:
  - Documents that setup as the canonical template
    (docs/STORYBOOK_TEMPLATE.md) including the .storybook/main.ts,
    preview.ts, package.json scripts, and an example story.
  - Catalogs which of the 8 visual @bytelyst/* packages need Storybook
    added (1/8 done — @bytelyst/ui).
  - Per docs/ROADMAP_2026_DECISIONS.md §9, hosting target is
    self-hosted Gitea Pages (no Chromatic).

Full rollout to the other 7 packages stays open as incremental work.

═══════════════════════════════════════════════════════════════════════
TODO #4 — DTCG v3 token migration RFC
═══════════════════════════════════════════════════════════════════════
This is too large to land in a single commit. Drafted RFC instead:
  docs/rfc/0001-dtcg-v3-token-migration.md

The RFC proposes a 4-PR sequence:
  PR 1 — Add converter + dual-emit (byte-identical assertion)
  PR 2 — Flip source of truth to DTCG JSON
  PR 3 — Introduce the component tier
  PR 4 — Multi-theme via DTCG token sets

Estimate: 2 person-weeks total. Backward compatibility: --ml-* and
--bl-* names preserved through all 4 PRs. Status: Draft, awaiting
reviewers.

Refs: learning_ai_uxui_web/docs/ROADMAP_2026.md §10 TODOs #4, #5, #6
2026-05-27 11:49:21 -07:00
saravanakumardb1
d1d88db4dd chore(gitea): rename npm package owner ByteLyst -> learning_ai_user 2026-05-26 18:38:57 -07:00
root
9e8d0bd048 ci: add Gitea-compatible package publish modes
All checks were successful
CI — Common Platform / Build, Test & Typecheck (push) Successful in 5m28s
Publish @bytelyst/* packages / publish (push) Successful in 5m54s
2026-05-25 07:25:52 +00:00
root
442ad629c2 ci: harden Gitea package publish workflow
All checks were successful
CI — Common Platform / Build, Test & Typecheck (push) Successful in 2m53s
2026-05-25 07:18:30 +00:00
root
e3b20446ec ci: fix consumer verification path
All checks were successful
CI — Common Platform / Build, Test & Typecheck (push) Successful in 3m53s
Publish @bytelyst/* packages / publish (push) Successful in 4m14s
2026-05-25 06:27:55 +00:00
root
daabd37c78 ci: verify published packages as consumers
All checks were successful
CI — Common Platform / Build, Test & Typecheck (push) Successful in 3m33s
Publish @bytelyst/* packages / publish (push) Successful in 2m27s
2026-05-25 06:20:30 +00:00
root
c7f6b981f1 ci: use mounted npmrc for pnpm publish
All checks were successful
CI — Common Platform / Build, Test & Typecheck (push) Successful in 2m9s
Publish @bytelyst/* packages / publish (push) Successful in 2m39s
2026-05-25 06:14:34 +00:00
root
b46d4ba0b6 ci: run Gitea publish workflow with bash
Some checks failed
CI — Common Platform / Build, Test & Typecheck (push) Successful in 3m45s
Publish @bytelyst/* packages / publish (push) Failing after 4m6s
2026-05-25 06:09:29 +00:00
root
079e46b74d ci: simplify Gitea publish workflow trigger
Some checks failed
Publish @bytelyst/* packages / publish (push) Failing after 1m38s
CI — Common Platform / Build, Test & Typecheck (push) Successful in 1m55s
2026-05-25 06:04:52 +00:00
root
9b884d6e85 ci: fix Hostinger Gitea workflows
All checks were successful
CI — Common Platform / Build, Test & Typecheck (push) Successful in 1m29s
2026-05-25 06:02:05 +00:00
root
7d8aebd5d4 ci: add Gitea package publish workflow
Some checks failed
CI — Common Platform / Build, Test & Typecheck (push) Failing after 3s
CI — Common Platform / Publish @bytelyst/* to Gitea npm registry (push) Has been skipped
2026-05-25 05:57:38 +00:00
saravanakumardb1
539e64e5d6 ci: include eslint.config.js + workflow files in path triggers
Three consecutive commits to eslint.config.js (9be49acb, 1035b730,
7ae60852) failed to trigger any new common-plat CI runs even after
`git push origin main && git push gitea main`. Root cause: the
workflow had a 'paths:' filter that only matched packages/**,
services/**, dashboards/**, lockfiles, and a few specific
root manifests — `eslint.config.js` and the workflows themselves
were NOT in the list, so Gitea silently skipped every push that
only touched those files.

Added the two missing globs:

  - 'eslint.config.js'
  - '.gitea/workflows/**'

Both are demonstrably CI-relevant — eslint.config.js drives the
lint step that's currently failing, and workflow edits obviously
need to trigger a fresh run.

This commit edits a workflow file, so it is itself covered by the
new path glob and should trigger a run on push.
2026-05-23 16:51:38 -07:00
saravanakumardb1
5da706ead1 ci: correct on-disk path in CI workflows (/opt/bytelyst → /Users/sd9235/code/mygh)
The 'Build, Test & Typecheck' job was failing immediately at its
first 'Pull latest' step with:

  /opt/bytelyst/learning_ai_common_plat: No such file or directory
  exit status 1

The act_runner on this host has the monorepo at
/Users/sd9235/code/mygh/learning_ai_common_plat (same pattern as
the consumer repos that switched to the on-disk workflow earlier
today). The legacy /opt/bytelyst/* path predates the migration and
never existed on this host.

Replaced all 10 occurrences across both CI workflow files
(.gitea/workflows/ci.yml and publish.yml) with sed. No script
content changed, only the cd target.
2026-05-23 15:34:42 -07:00
root
8b04ff806c ci: fix workflow for Linux host runner, auto-publish on push
Generated with [Devin](https://cli.devin.ai/docs)

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
2026-05-10 01:59:46 +00:00
saravanakumardb1
deff216c7e refactor(gitea): robust manifest-based publish pipeline
publish-outdated-packages.sh rewritten:
- Manifest-based change detection (no registry tarball downloads)
- Single pack per package (not double-pack for check+publish)
- Deterministic content hash: normalizes version, publishConfig,
  and @bytelyst/* dep versions (workspace:* resolution noise)
- Single metadata fetch per package (cached in-process)
- Fixed .npmrc overwrite bug that broke auth during publish phase
- npm_clean() helper strips all proxy env vars uniformly

release-packages.sh fixed:
- .npmrc now includes scoped registry + proxy=false for corp
- Unified corp/home publish path (no duplicated code)
- version_on_registry() uses proxy-stripped env
- Registry credential check uses proxy-stripped env

CI workflow: switched to publish-outdated-packages.sh --skip-build
2026-04-13 01:47:03 -07:00
saravanakumardb1
54a06e227a refactor(scripts): move 5 Gitea scripts into scripts/gitea/ subdirectory
Moved:
  publish-local-gitea-packages.sh  → gitea/publish-local-packages.sh
  publish-outdated-gitea-packages.sh → gitea/publish-outdated-packages.sh
  release-gitea-packages.sh        → gitea/release-packages.sh
  run-registry-tests.sh            → gitea/run-registry-tests.sh
  harden-publish-config.sh         → gitea/harden-publish-config.sh

Dropped -gitea- infix (redundant with folder name).

Fixed in every moved script:
- REPO_ROOT: ../ → ../../ (one level deeper)
- Internal cross-reference comments

Updated all 10 referencing files:
- package.json (release script path)
- .gitea/workflows/ci.yml (publish step)
- 3 workflow .md files (publish-outdated usage)
- 3 devops docs (publish-local + registry-tests refs)
- 2 internal comment cross-references
2026-04-13 00:02:55 -07:00
saravanakumardb1
9e53a5cefa ci: add lint step to build-and-test job 2026-03-29 11:08:11 -07:00
saravanakumardb1
57fc783451 fix(ci): remove secrets.GITEA_NPM_TOKEN override + add git reset for dirty workdir
- Publish job was overriding runner env with empty string via secrets ref
- Build job could fail on dirty workdir from previous failed run
- Runner env already provides GITEA_NPM_TOKEN — no secrets store needed
2026-03-27 23:06:45 -07:00
saravanakumardb1
7f257df0f5 feat(ci): add token drift detection job to CI pipeline 2026-03-27 16:39:10 -07:00
saravanakumardb1
aa139d5021 feat(ci): add auto-publish job for @bytelyst/* packages + update migration doc
- Add publish-packages job to CI workflow (runs after build-and-test)
- Publish 13 remaining packages to Gitea (56 total, up from 43)
- Update act_runner token to read+write scope
- Fix package counts throughout migration doc (43 → 56)
- Update CI status: all 10/10 repos now have CI workflows
- Add package inventory section (§15.1)
2026-03-26 23:18:05 -07:00
saravanakumardb1
0ffbdce0ef fix(ci): fix admin-web test mocks + workflow build command
- Add getCurrentUserFromRequest + requireAdmin to all 8 auth-server test mocks
- Fixes Vitest 4.x strict mock requiring all accessed exports
- Skip pnpm install in CI workflow (deps already installed locally)
2026-03-22 21:11:24 -07:00
saravanakumardb1
017eb4278b fix(ci): use local paths for host-mode Gitea runner
- Replace actions/checkout with git pull + local working-directory
- Fixes corp proxy blocking GitHub action downloads
2026-03-22 20:23:01 -07:00
saravanakumardb1
6d4579da37 chore(ci): migrate to Gitea local CI, disable GitHub Actions
- Add .gitea/workflows/ci.yml for Gitea Actions
- Disable GitHub Actions: ci-extraction-service, ci-mcp-server, reusable-pnpm-workspace
- Add docs/devops/GITEA_LOCAL_CI.md setup guide
2026-03-22 20:13:02 -07:00