amethyst/nappletHost/src/main/AndroidManifest.xml at cd221d5de120f8c6544d375ead4737ee2dfd0187 - amethyst - Gitea on NOSTR

laantungir/amethyst

mirror of https://github.com/vitorpamplona/amethyst.git synced 2026-08-09 16:14:40 +00:00

Files

T

Claude 4218a7c1af refactor(napplets): extract sandbox runtime into :nappletHost module

The `:napplet` sandbox runtime (NappletHostActivity, NappletContentServer,
NappletIpc, NappletKeyActions) now lives in a new :nappletHost Android library
that depends only on :commons + :quartz — NEVER :amethyst. So the sandbox code
is compile-time incapable of importing Amethyst.instance / LocalCache / Account,
turning the "two-process, no secrets in the sandbox" rule from a convention into
a build-graph guarantee.

- New module + NappletHostContract (Intent-extra keys + broker service FQN), so
  the launcher (amethyst) and activity (module) share the launch contract with no
  dependency cycle. The activity binds the broker by class name.
- Capability labels for the "what it can access" sheet are resolved by the
  launcher (which has app resources) and passed in, so the module needs no
  capability string resources. Host-only strings moved into the module.
- amethyst depends on :nappletHost; the broker-side (NappletBrokerService,
  gateways, NappletLaunchRegistry) stays in :amethyst. Manifest declares the
  activity by FQN (keeps @style/Theme.Amethyst resolvable).
- Docs updated (CLAUDE.md + security plan).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016ncMHuBBVHEf7spAoSssde

2026-06-22 20:45:19 +00:00

3 lines

111 B

XML

Raw Blame History

	`<?xml version="1.0" encoding="utf-8"?>`
	`<manifest xmlns:android="http://schemas.android.com/apk/res/android" />`