Skip to content

System-Apps 03350348: AppCard on the shells' runtime (6881fb6c) - #53

Merged
ymote merged 1 commit into
mainfrom
chore/system-apps-03350348
Sep 27, 2026
Merged

ymote merged 1 commit into
mainfrom
chore/system-apps-03350348

Conversation

@ymote

@ymote ymote commented Sep 27, 2026

Copy link
Copy Markdown
Contributor

Repins OctoSense-System-Apps to 03350348 (OctoSense-System-Apps#20). That commit moves AppCard's runtime to Octoscript-Makepad 6881fb6c and makepad 6cf03859, which is what this shell uses since #51. octos stays at a6ea8505 (#52). Only native-apps.lock.json changes.

Local checks (macOS), matching the runtime workflow:

  • cargo check --locked, --features mobile-apps, and --workspace --features mobile-apps,app-appcard all pass.
  • The tree guards pass for host and aarch64-linux-android.
  • There is one octos (a6ea8505).
  • test_android_kernel passes.
  • setup-native.py --check --cargo-manifest Cargo.toml passes.

🤖 Generated with Claude Code

System-Apps now pins Octoscript-Makepad 6881fb6c / makepad 6cf03859 for
AppCard, matching this shell; octos stays a6ea8505.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@ymote
ymote merged commit 19514f1 into main Sep 27, 2026
2 checks passed
@ymote
ymote deleted the chore/system-apps-03350348 branch September 27, 2026 08:22
chrislearn pushed a commit to chrislearn/OctoSense that referenced this pull request Sep 29, 2026
…pps-03350348

System-Apps 03350348: AppCard on the shells' runtime (6881fb6c)
chrislearn pushed a commit to chrislearn/OctoSense that referenced this pull request Sep 29, 2026
makepad OctoSense-org#52 (OHOS packager honours the workspace target dir), OctoSense-org#53
(sys.dataset and sys.news_digest registered), OctoSense-org#54 (peer-link client);
Octoscript-Makepad OctoSense-org#56 (taskplan_light accents). Both runtime patches
apply unchanged; the stacked tree is now 2320c430.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
chrislearn pushed a commit to chrislearn/OctoSense that referenced this pull request Sep 29, 2026
Seven lib tests failed after the OctoScript/Octoscript-Makepad pins moved:
- l0_eval: the missing-data adapters lacked the watchlist helpers; the
  visible-error test now evaluates with no adapters (build_bare) and is
  ignored with its reason, since this evaluator is not the on-screen one.
- nav exemplar: replaced with OctoScript's current nav.card fixture; the
  nav size bound follows OctoScript's profile (< 400 lines).
- l0.md: the theme paragraph names only real themes.
- ACCENTS: taskplan_light answers every hue (Octoscript-Makepad OctoSense-org#56).
- capability_bridge scans every splash_* file that registers sys helpers
  (makepad OctoSense-org#53 wired sys.dataset and sys.news_digest).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
tyreseluo pushed a commit to tyreseluo/OctoSense that referenced this pull request Oct 4, 2026
App Hub moves from 58c3c8ae to its main 0d5b47a2:
- OctoSense-org#53: publisher keys come from the authenticated catalog.
- OctoSense-org#54: an installed release launches as itself, from verified bytes.
- OctoSense-org#63, OctoSense-org#64: the native apps OctoSense made native are reserved
  (calculator, clock, notes, reminders, weather, browser, task); its
  example app `weather` became `forecast`.
- OctoSense-org#61, OctoSense-org#67: makepad repins (this workspace's [patch] wins either way).
- Docs.

octosense-app-contract 1.1.0 (App Hub OctoSense-org#66, published to crates.io)
carries the reserved names. app-policy re-exports them, so App Hub's
admission tests at 58c3c8ae, whose fixtures still use `weather`, fail
against 1.1.0. The pin and the lock move together.

App Hub's new bundle layout (App Hub OctoSense-org#62, which OctoSense-org#301 prepares for) is
not in 0d5b47a2: installed bundles stay where the shell looks today.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.

1 participant