* fix(stardust): fix opening prototyped pages from browser plugin
Use `open <vfs-path>`, not `playwright-cli open`, for prototype
previews.
VFS-backed prototype files must be opened with the `open` shell
command so the preview service worker resolves the path.
`playwright-cli open` bypasses the worker and yields FILE NOT
FOUND. Update prototype and uplift SKILL.md to spell this out.
* chore: remove multiple files detail
Closes three low-risk Tessl skill-review orphan warnings.
- distill/SKILL.md: added a `## References` section listing the two
reference files (samples-brief-format.md, trait-matrix-schema.md).
distill was the only skill without a References section.
- prototype/SKILL.md References: added the four cinematic motion docs
(motion-registers.md, motion-stack.md, motion-attributes.md,
motion-runtime.md) alongside motion-validation.md.
- prototype/SKILL.md References: switched 7 cross-skill paths from
`skills/stardust/reference/X.md` (absolute-style, unresolvable by
Tessl) to `../stardust/reference/X.md` (the convention already
used by stardust/SKILL.md and uplift/SKILL.md).
No behavior changes — additive + path-correctness fixes.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Stacks three minor versions on the `redesign-adobecom` branch.
## 0.8.0 — Original `redesign-adobecom` changes
- NEW skill: `distill` — analyze HTML mockups + website URLs and produce a structured style guide; anchors `direct` under Mode B.
- Motion validation gate (Phase 2.8 on `prototype`) — clipped-container reveal timing, animation-range vs reading position, anim-enter trigger reachability, reduced-motion override completeness, no-JS fallback, multi-viewport scroll-driven checks.
- Surface forks formalized as parent-direction tuning under reimagined mode.
- Journal rule + recursive validate-and-fix loop promoted to master skill.
- HTTP/2 / Akamai bypass: route-fulfiller pattern in playwright-recipe.
## 0.9.0 — Cinematic motion feature
- `prototype --cinematic` (and `--cinematic=<register>`) — layers a brand-faithful motion register on the static prototype. Output is `<slug>-cinematic.html` alongside the static `<slug>-proposed.html`.
- Five motion registers as a closed catalog (`arrival`, `kinetic-display`, `live-systems`, `editorial`, `kinetic-grid`).
- Lenis bundled at `skills/prototype/assets/motion/` (MIT, ~17 KB). No GSAP / Framer / Theatre.js.
- Motion `data-*` vocabulary: `[data-anim]`, `[data-tile-anim]`, `[data-countup]`, `[data-flip]`, `[data-fill]`, `[data-split]`, `[data-parallax]`.
- Canonical inline runtime at `prototype/reference/motion-runtime.md`.
- Six cinematic-mode validation gates (Pass 6): Lenis bootstrap, reduced-motion fallback, scroll-jack check, three-position screenshot pass, register-match audit, motion C-cliff detector.
- `direct` writes `extensions.motion.register` from PRODUCT.md Brand Personality. For multi-variant runs the register lives in per-variant `DESIGN-<id>.json`.
## 0.10.0 — `/stardust:uplift <URL>` one-shot presales orchestrator
- NEW skill: `uplift` — produces three differentiated variants (A faithful + improvements, B "what if we amplified `<captured trait>`?", C "what if motion was part of the identity?" — fully cinematic) without further user coordination.
- Closed catalog of 8 "what if…" captured-trait amplification candidates with disqualification clauses.
- Load-bearing artifacts: `uplift-improvements.md` (5 specific weaknesses) and `uplift-questions.md` (catalog walk + picks + disqualifications).
- Delegates to extract → direct → prototype with no new flags on the underlying skills.
## Plugin metadata
- `tile.json` bumped 0.8.0 → 0.10.0; registers `uplift` + `prepare-migration` (the latter a pre-existing gap closed).
- `.claude-plugin/plugin.json` bumped 0.9.0 → 0.10.0.
## Backward compatibility
All existing sub-commands unchanged. Motion is opt-in via `--cinematic`. `uplift` is a new entry point with no parallel render path — it delegates to existing skills. Existing project trees gain new artifacts only when the new flags / skills are engaged.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The semantic-release/github success step posts a 'released in version'
comment on the merged PR. With only contents+issues write, GitHub denied
that write (see run 26256538929: 'Not allowed to add a comment to the
issue/PR #144'). Per @semantic-release/github docs, pull-requests: write
is required for the success comment.
PR #139 wrapped commit-analyzer with path filtering but tried to fix
release-notes-generator with gitRawCommitsOpts: { path: '.' } -- a
no-op because the plugin reads context.commits from semantic-release,
never gitRawCommitsOpts. Result: every skill release body and CHANGELOG
included commits from the entire repo (see slicc-handoff-v1.0.0).
- Add scripts/path-filtered-notes-generator.cjs mirroring the analyzer
wrapper -- filters context.commits via git log -- . before delegating
to the real plugin.
- Wire it into release.config.cjs in place of the bare plugin entry;
drop the dead gitRawCommitsOpts config.
- Regenerate plugins/aem/edge-delivery-services/skills/slicc-handoff/
CHANGELOG.md (skipped by PR #140 because the tag did not exist yet).
Per review feedback: defer SLICC protocol detail to the maintainer-curated
https://www.sliccy.ai/llms.txt index rather than restating it in the
skill. Adds a pointer near the top of SKILL.md and trims "How It Works"
to a one-paragraph summary that links to llms.txt for the full rel URIs,
payload shape, and public API catalog. Activation guidance, verb-prefix
rules, and example commands are kept inline so the skill stays useful
without a network fetch.
Co-authored-by: Cursor <cursoragent@cursor.com>
Per review feedback: let semantic-release manage the changelog content.
Reverts the descriptive notes added in 6c75163.
Co-authored-by: Cursor <cursoragent@cursor.com>
Replaces the placeholder with an Initial Version entry that explains what
the skill is for, what's included (SKILL.md, the Node helper, package and
release config), the handoff/upskill verb prefixes, the SLICC_PORT env
var, and security notes about treating the instruction string as
untrusted input. Future semantic-release entries will be prepended above
this section.
Co-authored-by: Cursor <cursoragent@cursor.com>
Adds a new skill that lets an external coding agent hand off the current
task to the SLICC browser agent, or trigger installation of a skill into
SLICC from a GitHub repo. The skill ships a small Node helper that posts
to a local SLICC node-server on localhost and (optionally) opens the
sliccy.ai handoff URL so the SLICC extension can pick it up via its
RFC 8288 Link header observer. Either path results in a yes/no approval
card in the SLICC cone keyed by verb prefix (handoff: / upskill:).
Registers the skill in plugins/aem/edge-delivery-services/tile.json.
Co-authored-by: Cursor <cursoragent@cursor.com>
Hey @trieloff 👋
I ran your skills through `tessl skill review` at work and found some targeted improvements for the Cloud Service replication skill. Here's the before/after:
| Skill | Before | After | Change |
|-------|--------|-------|--------|
| replication (cloud-service) | 52% | 87% | +35% |
I picked this skill because it had the most room to grow across the repo — the baseline was 52%, lowest alongside `replication-orchestrator` (6.5 LTS). Since Cloud Service is the forward-looking runtime, it felt like the highest-signal place to contribute.
<details>
<summary>Changes made</summary>
**Description improvements (biggest impact — 40% → 100%):**
- Rewrote frontmatter description from a generic 2-line summary to a specific, action-oriented description listing concrete capabilities (publish, deactivate, delete, bulk activation, preview-tier targeting, sync/async, status checks, permissions, workflow steps, event handling)
- Added explicit "Use when..." clause with seven trigger scenarios covering natural language terms users would say ("publish pages", "activate content", "check replication status")
- Switched description from YAML block scalar to quoted string format
- Added metadata.category field
**Content improvements (42% → 73%):**
- Removed "Architecture: How Replication Works in Cloud Service" section — Claude already understands AEM's Sling Content Distribution pipeline
- Removed ReplicationActionType values table — these are self-evident from the linked Javadoc and the code examples
- Moved Common Patterns (auto-publish on Content Fragment save, external cache purge after publication) to references/patterns.md for progressive disclosure, reducing the main SKILL.md by ~100 lines
- Added a Service User setup pattern to the reference file for completeness
- Condensed Best Practices section — removed verbose exception handling example, consolidated service user guidance into a concise paragraph with a link to the reference file
- Net result: SKILL.md dropped from 744 to 592 lines with better structure
**Unchanged skills:**
- All other 88 skills left untouched — many are already scoring well (replicate-content at 100%, workflow-development at 99%, best-practices at 94%)
</details>
I also stress-tested your replication skill against a few real-world task evals and it held up really well on bulk content activation with automatic transactional bucketing above the 100-path threshold. Kudos for that.
Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch — just saw room for improvement and wanted to contribute.
Want to self-improve your skills? Just point your agent (Claude Code, Codex, etc.) at this Tessl guide (https://docs.tessl.io/evaluate/optimize-a-skill-using-best-practices) and ask it to optimize your skill. Ping me — @yogesh-tessl (https://github.com/yogesh-tessl) — if you hit any snags.
Thanks in advance 🙏
Co-authored-by: Yogesh Rao <yogesh-tessl@users.noreply.github.com>
* fix(aem-workflow): correct cq.workflow.job.max.procs parallelism myth in workflow-debugging (AEM 6.5 LTS)
The skill instructed customers to increase cq.workflow.job.max.procs
for workflow throughput. While that property is shown in Felix Console
(its display name and description are defined in the WorkflowSession
Factory metatype), it has no effect at runtime — no code path reads
the value. Real workflow parallelism is controlled by queue.maxparallel
on the "Granite Workflow Queue" (an Apache Sling Job Queue
Configuration instance). The skill's own thread-pool section at
SKILL.md:105 already mentions Max Parallel correctly; the four
cq.workflow.job.max.procs references contradicted that and were
misleading customers.
- SKILL.md: 4 references to cq.workflow.job.max.procs replaced with
queue.maxparallel on the Granite Workflow Queue
- reference.md: parallelism row updated to point to the correct OSGi
config (Apache Sling Job Queue Configuration)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(aem-workflow): correct JMX MBean ObjectName for retry/queue-info ops in workflow-debugging (AEM 6.5 LTS)
The skill cited com.adobe.granite.workflow:type=Repository as the
MBean hosting retryFailedWorkItems, returnSystemJobInfo, and
returnWorkflowQueueInfo. That ObjectName does not exist on AEM 6.5 LTS
— a JMX lookup returns 404. All three operations actually live on
com.adobe.granite.workflow:type=Maintenance, the same MBean the skill
already used correctly for purgeCompleted/countStaleWorkflows/
restartStaleWorkflows. The real second workflow MBean is
:type=Statistics, which exposes time-series execution metrics.
Updates Step 7 (Key JMX MBeans) to:
- Consolidate every workflow maintenance operation under the
Maintenance MBean (matches what AEM actually exposes via JMX)
- Add Statistics MBean as a separate row with its read/write
accessors for DataLifeTime / DataFidelityTime / DataProcessRate /
DataRate plus getResults / clearRecords
- Add operation parameter signatures (model, days, dryRun) where
applicable
Verified on AEM 6.5 LTS localhost:4505:
- :type=Maintenance → HTTP 200
- :type=Statistics → HTTP 200
- :type=Repository → HTTP 404 (does not exist)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(aem-workflow): replace stale Config Status ZIP file refs with live Felix Console URLs in workflow-debugging (AEM 6.5 LTS)
The skill instructed customers to "check in 039_Sling_Thread_Pools.txt"
and similar numbered files from the Configuration Status ZIP for
thread pools, threads, Sling Jobs, and Sling Scheduler data. The
Config Status ZIP produced by AEM 6.5 LTS (/system/console/
status-Configurations.zip) does not contain those numbered files —
only 000_Configurations.txt and index.json. A customer following the
skill would search for files that do not exist on their AEM.
Updates all 9 references to point to the live Felix Console pages
that are the actual sources of this data:
- 039_Sling_Thread_Pools.txt -> /system/console/status-slingthreadpools
- 042_Threads.txt -> /system/console/status-Threads
- 043_Threads__via_JStack_.txt -> /system/console/status-jstack-threaddump
- 027_Sling_Jobs.txt -> /system/console/slingevent
- 034_Sling_Scheduler.txt -> /system/console/status-slingscheduler
- 003_Configurations.txt -> /system/console/configMgr
Each URL verified to return HTTP 200 on AEM 6.5 LTS localhost:4505.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(aem-workflow): correct Granite Workflow Queue Max Parallel default value in workflow-debugging (AEM 6.5 LTS)
The skill stated that the Granite Workflow Queue ships with
queue.maxparallel = 1. The actual OOTB value on AEM 6.5 LTS is 0.5,
which the Sling Job Queue interprets as "50% of available CPU cores"
(fractional values in 0..1 are CPU-relative; integers >= 1 are
absolute worker counts). A customer following the previous skill
would plan throughput tuning against the wrong starting point.
Updated in two places:
- Step 3c Granite Workflow Queue config bullet list
- Step 5 Configuration checklist table row
Both now cite the OOTB 0.5 value with a pointer to verify the running
value via the OSGi config endpoint at
/system/console/configMgr/org.apache.sling.event.jobs.QueueConfiguration~workflow.
Verified on AEM 6.5 LTS localhost:4505: queue.maxparallel = 0.5.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
All existing CHANGELOG.md files contained commits from the entire repo
since the skill's last tag, making release notes meaningless. This
regenerates each one from scratch using git log filtered to the skill's
own directory, following up on #139 which fixed the root cause for
future releases.
Empty release sections (e.g. 1.0.0) indicate versions bumped solely by
docs/refactor commits, which is correct — the angular preset omits those
types from the CHANGELOG body.
Also adds scripts/regenerate-changelogs.cjs in case a manual re-run is
ever needed.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Use execFileSync with argument array instead of execSync with
interpolated string to avoid shell injection risk
- Log a warning via context.logger when the git fallback is triggered
so failures are diagnosable rather than silently swallowed
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Each skill was including all repo commits in its CHANGELOG and GitHub
release body, and unrelated breaking changes were triggering spurious
major bumps. Fix by path-filtering at both the commit-analysis and
note-generation stages.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Create .cursor-plugin/marketplace.json for an "adobe-skills" marketplace (version 1.0.0) that includes an "app-builder" plugin entry. Also update .github/CODEOWNERS to add ownership for /.cursor-plugin/ to @shsteimer and @trieloff so plugin config changes are properly reviewed.
* fix(aem-workflow): update workflow-launchers content for AEM 6.5 LTS
Updates the workflow-launchers skill for AEM 6.5 LTS with validated
content covering launcher configuration, condition patterns, and
JCR-event-driven workflow triggering. SKILL.md now references the
canonical foundation refs hosted under workflow-orchestrator instead
of local duplicates.
- SKILL.md: expanded launcher configuration guidance; loop-prevention
guardrail clarified (WorkflowSession vs JCR Session disambiguation);
IDE-LLM consumability improvements; foundation ref links re-pointed
to workflow-orchestrator canonical copies
- condition-patterns.md: ECMAScript (Rhino) terminology corrected;
pattern coverage tightened
- launcher-config-reference.md: cq:WorkflowLauncher property
reference expanded; consumability improvements
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* chore(aem-workflow): remove duplicated foundation refs from workflow-launchers (AEM 6.5 LTS)
The 6 foundation reference files under workflow-launchers/references/
workflow-foundation/ duplicated the canonical copies hosted in
workflow-orchestrator/references/workflow-foundation/. SKILL.md links
were re-pointed to the canonical copies in the previous commit, so
the local duplicates are now orphaned.
Deletes:
- 65-lts-guardrails.md
- README.md
- api-reference.md
- architecture-overview.md
- jcr-paths-reference.md
- quick-start-guide.md
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(aem-workflow): correct loop-prevention setUserData value in workflow-launchers (AEM 6.5 LTS)
The skill instructed setUserData("workflowmanager") for loop prevention.
AEM's WorkflowLauncherListener does not recognize that string. The
correct value is "changedByWorkflowProcess", which matches
HandlerBase.WORKFLOW_SESSION_USERDATA in
com.adobe.granite.workflow.core and is the default member of the OSGi
config property granite.workflow.launcher.globally.exluded.event.user.data
that the launcher reads at startup.
- SKILL.md: setUserData("workflowmanager") -> "changedByWorkflowProcess"
in the loop-prevention guardrail (2 occurrences in same line)
- condition-patterns.md: setUserData("workflowmanager") ->
"changedByWorkflowProcess" in the Java snippet; rewrote the comment
to correctly distinguish the OSGi config-property name from the
userData value
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(aem-workflow): correct OOTB launcher names, excludeList format, and condition shorthand in workflow-launchers (AEM 6.5 LTS)
Audit findings verified against AEM 6.5 LTS localhost:4505 OOTB
launchers under /libs/settings/workflow/launcher/config/:
- SKILL.md "Common OOTB Launchers" table: dam_update_asset_create
does not exist (actual: update_asset_create); dam_update_asset_modify
does not exist (actual: update_asset_mod); dam_xmp_writeback trigger
description corrected to PROPERTY_CHANGED (eventType=16) on
nt:unstructured at /jcr:content/metadata; update_page_version_*
removed (not present in /libs, /conf, or /apps on a baseline 6.5 LTS
install). Table expanded with eventType, nodetype, glob, and
workflow columns
- SKILL.md and launcher-config-reference.md: excludeList type
corrected from String[] to String (single comma-separated value);
description expanded to document the two entry formats — bare JCR
property names and the event-user-data:<value> prefix that excludes
events tagged with a specific JCR observation userData
- launcher-config-reference.md: document the singular `condition`
shorthand alongside the plural `conditions` array; both forms are
accepted at startup
- condition-patterns.md: loop-prevention comment rewritten to explain
the changedByWorkflowProcess value via the customer-visible OSGi
config property granite.workflow.launcher.globally.exluded.event.
user.data (visible in Felix Console)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Add a human-friendly displayName ("Adobe App Builder") and a local "skills" path to plugins/app-builder/.cursor-plugin/plugin.json. Update README install instructions to create the local plugin directory and copy the plugin contents (mkdir -p + cp -R), and add a note to verify the plugin loaded in Cursor settings. These changes clarify local installation and expose the plugin's skills directory for Cursor distribution.
Add Cursor-native plugin manifest at plugins/app-builder/.cursor-plugin/plugin.json,
mirroring the existing .claude-plugin/plugin.json (name: app-builder, version: 1.0.0).
Documents the Cursor distribution channel in README under Installation, marking
app-builder as the pilot plugin. Other plugins will gain Cursor support once
the pattern is validated.
* fix(stardust): make migrate output genuinely zip-and-deploy portable
The 0.7.0 contract claimed "self-contained, zip-and-deploy" but
emitted root-absolute paths (/assets/..., /beers/) plus
directory-only nav links. Those work on a webserver at the host
root only — they 404 on file:// and at any subpath. This PR
delivers what the claim promised:
- Output path is URL-literal: /beers/ -> beers/index.html,
/about-us/history.html -> about-us/history.html. No more
synthesizing /about/index.html from a slug.
- Page map (state.json.migrate.pageMap[]) built once per run;
per-page rendering and internal-link rewriting both consume it.
- Reference shape is depth-aware relative: prefix is ./ for
depth-0 pages, ../ * depth otherwise. Works on file://, at
host root, and at any subpath without rewriting.
- Phase 3 broadens the self-containment check into a full
portability audit: refuses absolute internal refs, refuses
directory-only nav, runs the new pageMap + file:// fixtures.
- New fixtures: file-protocol-audit.mjs (Playwright file://
round-trip) and pagemap-audit.mjs (static pageMap consistency).
- asset-bundling.md and migrate-output-format.md aligned to the
new depth-aware-relative shape; state.json contract gains
pageMap[].
Plugin bumped 0.7.0 -> 0.7.1.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* review: fix four flagged correctness issues
- Directory-only-nav regex now catches `./beers/` (the cited example).
Old pattern required a-z as first char; `./beers/` starts with `.`
and would have slipped through. New pattern accepts ./, ../, /, or a
bare segment, and excludes scheme-bearing URLs (no false positive
on https://google.com/).
- Add a second grep for absolute url() references inside inline style
attrs and <style> blocks (and CSS files); the original href/src grep
missed these.
- SKILL.md Outputs row no longer claims the sidecar lives at
<source-url-path>/_meta.json (nonsense for .html-leaf pages).
Replaced with a row that points at the canonical sidecar rule.
- migration-procedure.md § Page map now explicitly says same-origin
absolute URLs are stripped to their path portion before pageMap
lookup (per content-preservation.md § Internal link rewriting),
closing the loophole that would let <a href="https://origin/foo/">
pass through verbatim.
Regex patterns verified against a test fixture before commit.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* review: update migrate-self-contained-bundle eval to 0.7.1 contract
The eval was pinned to 0.7.0's root-relative /assets/<subpath>
shape. This PR's contract change to depth-aware relative paths
would have made the eval fail against correct 0.7.1 output.
- detection_src_href criterion now asserts <prefix>assets/<subpath>
(not /assets/<subpath>).
- Renamed prefix_resolution_root_relative -> prefix_normalises_authoring;
description flipped from "reference is left as-is" to "authoring
is normalised to the depth-aware emit form".
- Added 4 new criteria: depth_aware_paths (6pts),
pagemap_constructed (6pts), internal_links_via_pagemap (5pts),
portability_audit_passes (13pts).
- Setup uses real source URLs that exercise the URL-literal rule:
/, /beers/, /about/history.html (preserve .html leaf),
/docs/api/ (depth-2 nested).
- Prototype HTML now carries internal nav in three authoring styles
(root-absolute, same-origin absolute, directory-only) plus a
broken-link case, exercising the page map rewrite.
- Run 1 expected behavior rewritten to expect depth-aware emission
('./assets/...'), pageMap built before render, broken-link
flagging, and the 6-step portability audit passing.
- Run 4 (cross-page dedup) updated so the second page emits its
shared asset with its own '../' prefix while the underlying file
on disk is a single copy.
- Weights re-balanced to sum to 100; portability_audit_passes gets
the largest weight (13pts) since it backs the contract claim.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
* feat(stardust): migrate produces self-contained zip-and-deploy bundle
Bundles every referenced asset into stardust/migrated/assets/ and
rewrites HTML/CSS references to root-relative /assets/<subpath> so
the migrated tree is fully self-contained. Adds asset-bundling
reference (six detection shapes, nine edge cases), output-format
contract with state.json.migrate block (selfContained: true),
--clean and --pin-timestamp flags, and an eval covering the six
acceptance criteria.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* review: fix count, --clean correctness, document asset-missing rename
- Bump totalAssetsBundled 6 → 7 in eval task.md (matched bundledAssets[] length).
- --clean now implies --force so the bundledAssets Set is the complete
union across every page; idempotent-skipped pages' assets are no
longer at risk of being deleted as stale. Updated SKILL.md flag
description, asset-bundling.md § Stale asset cleanup, the
Idempotent-skip interaction note, and the eval's run-3 expected
behaviour + criterion.
- Document the contentDeviations / migrationDecisions kind rename
from "media-missing" to "asset-missing" in
migrate-output-format.md § Backwards compatibility — consumers
should accept either string until they migrate.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* chore(stardust): bump plugin version 0.6.0 → 0.7.0
Self-contained zip-and-deploy bundle is a minor-version addition:
new --clean and --pin-timestamp flags, new state.json migrate
block (forward-compat), new asset-bundling reference contract,
provenance kind rename (media-missing → asset-missing).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* chore(stardust): bump palette library version v0.6.0 → v0.7.0
Keep the palette library version aligned with the plugin version.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
Coordinated three-part change: Part I adds a strategic ia-fidelity
axis pinned at direct time (verbatim → A1/A2/A3 surface forks vs
reimagined → A+B+C role-differentiated). Part II adds 10 disciplines
at three phase boundaries (brief-time 1-5, craft-time 6-8, quality
gates 9 + convergence detector 10) with the four wasatch dry-run
friction carve-outs folded in. Part III lands Phase 5 approval
fold-back (site-wide / page-local / don't-fold) with verbatim no-op
gating. Also sweeps remaining Phase 5.5 → 2.7 references across the
plugin docs.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* fix(aem-workflow): correct workflow-model-design XML format for /conf design-time (AEMaaCS)
The cloud-service workflow-model-design skill incorrectly showed
cq:WorkflowModel / cq:WorkflowNode / cq:WorkflowTransition (runtime
/var format) under the /conf design-time path. The Workflow Model
Editor expects cq:Page + jcr:content/flow/<step-component> with
nt:unstructured step nodes and sling:resourceType identifiers.
A developer following the previous content would deploy a model the
editor cannot open and Sync cannot process.
Verified against AEM Cloud Service SDK localhost:4517 OOTB models at
/libs/settings/workflow/models/ and source at com.adobe.granite.workflow
on master branch.
- model-xml-reference.md: full rewrite to cq:Page + flow/parsys
format; design-time vs runtime table; cq:template fix to
/libs/cq/workflow/templates/model; rewritten pitfalls section;
runtime /var shape documented for reference
- step-types-catalog.md: every step snippet converted to
nt:unstructured + sling:resourceType; sling:resourceType reference
table added; initiatorparticipant documented; transition XML
removed (Sync derives transitions from step order)
- model-design-patterns.md: Pattern 5 Task Manager XML corrected to
flow-layer format; Pattern 6 variables annotated as runtime-only
- SKILL.md: Sync verification added to checklist; /conf-only on
AEMaaCS distinction (no /etc legacy auto-deploy); filter.xml
guidance updated
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(aem-workflow): correct AND_SPLIT/AND_JOIN/END resourceTypes in workflow-model-design (AEMaaCS)
The cloud-service step-types-catalog listed sling:resourceType values
for AND_SPLIT, AND_JOIN, and END that do not exist as design-time
components on AEM Cloud Service. Verified against
/libs/cq/workflow/components/model/ on localhost:4517.
- sling:resourceType table: AND_split -> and (actual OOTB component
is named `and`, not `AND_split`); AND_join and end rows removed
(no such components exist)
- AND_SPLIT example: corrected sling:resourceType to
cq/workflow/components/model/and; AND_JOIN inline example removed
- AND_JOIN section: replaced manual <synchronize> example with note
that AEM Sync derives AND_JOIN nodes automatically at /var
- END Node section: replaced manual <workflowend> example with note
that Sync derives both START and END automatically
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Align with the updated MCP server which split fetch-cam-bpa-findings
into two purpose-specific tools:
- fetch-cam-bpa-findings-by-pattern: code-transformer pattern flows
(scheduler, assetApi, eventListener, resourceChangeListener, eventHandler)
- fetch-cam-bpa-findings-by-importance: returns authoritative _COUNT_
rollup rows at one importance level (CRITICAL/MAJOR/ADVISORY/INFO),
sorted by descending count — for open-ended "what are the critical
findings?" requests
Changes:
- cam-mcp.md: rename all references; add full Tool section for
fetch-cam-bpa-findings-by-importance (request, response shape,
backend endpoint, error response note)
- SKILL.md: update CAM via MCP summary and batching section to name
both tools with their respective use cases
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The MCP cam-bpa-fetcher now returns success:true with an empty targets
array and a message field when a specific pattern has no findings in the
latest BPA report, instead of success:false with a misleading "upload
BPA report" suggestion.
Align the skills layer:
- BpaResult gains a message field (unified-collection-reader.js)
- bpa-findings-helper caches and propagates mcp.message so callers see
"No 'scheduler' findings in the latest BPA report for project X"
rather than the generic cache message when targets are empty
- cam-mcp.md documents the new message field on the success response
and splits the empty-targets behavior table row into the two distinct
cases (success:true specific-pattern vs success:false all-pattern)
- New test verifies message propagation, cache write, and no re-fetch
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Fork pull requests receive a read-only GITHUB_TOKEN regardless of the
permissions block, so the gh api POST/PATCH to create or update the
sticky tessl-lint comment always returns HTTP 403. This caused the job
to exit 1 even when all tiles passed lint.
Make both comment API calls non-fatal with || echo warning so the job
result reflects the actual lint outcome rather than a GitHub API
permission restriction.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* feat(stardust)!: sweep — drop doctor.md, F-NNN fossils, opt-out flags, live integration
Four related cleanups bundled. Each independently small; together
they shrink the docs by ~600 lines and remove three doc-rot
patterns at once.
1. Delete doctor.md (493-line spec for an unimplemented script).
The Festool-incident concerns it was scoped to are now handled
by concrete write-time contracts (validateProvenance, content-
sourcing hierarchy, anti-toolbox audit). No external references.
2. Drop F-NNN feedback fossils + version-changelog paragraphs.
STARDUST-FEEDBACK.md doesn't exist in the plugin; the F-001 /
F-002 / F-009 / F-015 / F-016 / F-018 citations were opaque
tribal vocabulary. Kept the rules they cited; dropped the
IDs. divergence-toolkit.md changelog paragraphs (v0.1 → v0.2,
v0.4 → v0.5, v0.5 → v0.5.1) collapsed.
3. Slim flag surfaces. Every --no-* / --skip-* / --allow-* /
--refresh-stale flag dropped from prototype and migrate; the
underlying quality gates are now mandatory. Manual chat
overrides ("ship as-is", "accept the P1 findings") remain
available and are recorded in _provenance verbatim.
prototype flags: 10 → 5 (<slug>, --all, --prep, --canon-from,
--publish-sample).
migrate flags: 8 → 5 (<slug>, --all, --force, --require-approved,
--strict-canon).
4. Drop the impeccable:live integration. Live was documented as
the "default" iteration path but wasn't used — chat-driven
command invocation is the actual default. Phase 4 collapses
from 6 steps to 3 (open file → mark prototyped → report).
Iteration paths drop from 3 to 2 (chat-driven, direct
invocation). Live remains usable as an external tool the user
invokes directly against the proposed file; stardust no
longer pretends to drive its poll loop.
BREAKING CHANGE: prototype no longer accepts --no-iterate,
--no-critique, --skip-adapt-audit, --adapt-variant, --no-hamburger,
--refresh-stale, or --no-impeccable. migrate no longer accepts
--refresh-stale, --allow-placeholder, or --skip-adapt-audit.
The mobile-adapt audit, content-sourcing scan, placeholder gate,
and critique + audit pass are now mandatory; manual chat overrides
replace the flag-based bypasses.
The live driver loop (Phase 4 steps 4-6: config.json setup, event
streaming, carbonize cleanup, iteratedVia: impeccable:live
provenance) is gone. The proposed file's iteratedVia provenance
now records the named impeccable commands run against the file,
not a live sessionId.
stardust bumped to 0.6.0.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* chore(stardust): sync tile.json version to plugin.json (0.6.0)
The tile manifest's version was stuck at 0.1.0 while the plugin
moved to 0.6.0. Keep them in sync so tessl-side catalog metadata
matches the marketplace.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
* stardust: mobile-nav collapse pattern + drop before/after viewer
Two related changes to stardust:prototype landing together.
Mobile-nav collapse (additive):
- New stock CSS-only hamburger pattern auto-applied by Phase 5.5
when the Mobile-adapt audit refuses at 360px (overflow,
sub-11px nav font, or sub-10px nav gap).
- New audit conditions documented in skills/prototype/SKILL.md
§ Mobile-adapt audit; checked at runtime via the Playwright
snippet at skills/prototype/fixtures/mobile-nav-audit.mjs.
- Stock pattern doc at skills/prototype/reference/mobile-nav-collapse.md
carries the copy-pasteable HTML+CSS+JS, the ARIA checklist,
the post-injection source-order check, --no-hamburger opt-out,
and the alternative-pattern vocabulary.
- New data-nav-collapse="hamburger" attribute (v2.2 additive) on
<header> when the pattern is applied.
- Positive + negative fixtures verify the audit end-to-end.
Drop the per-page before/after viewer:
- Phase 3 (Compose the viewer) removed; the proposed file is
opened directly in the browser.
- Approval is now chat-only: "approve <slug>" or "approve".
- skills/prototype/reference/before-after-shell.md renamed to
proposed-file-shell.md and stripped to the proposed-file
contract only (viewer half, iframe resolution chain, action
buttons, and stash mechanic all dropped).
- state-machine.md prototypePath repointed at -proposed.html;
doctor.md D-104 pairs -proposed.html with -shape.md;
artifact-map.md drops the <slug>.html row; publish-sample.md
simplifies variant discovery (no more "is not the viewer"
disambiguation); evals/prototype-before-after rewritten to
expect a single proposed file.
BREAKING CHANGE: stardust:prototype no longer composes the
before/after viewer at stardust/prototypes/<slug>.html.
Anyone scripting on top of that file existing on disk should
switch to stardust/prototypes/<slug>-proposed.html (the
prototypePath in state.json now points there directly). The
approval gesture moves from the viewer's Approve button to a
chat-only "approve <slug>" / "approve".
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* stardust: bump version to 0.5.0
Minor bump for the breaking change in 370a208 (drop before/after
viewer; chat-only approval). Pre-1.0 semver: minor bump signals
a breaking change without claiming API stability.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
The `marketplace` field in plugin dependencies and the
`allowCrossMarketplaceDependenciesOn` allowlist must use the
marketplace's `name` (`impeccable`), not its GitHub repo path
(`pbakaus/impeccable`). The mismatch caused Claude Code to flag
the stardust plugin manifest as invalid on install.
Bumped to 0.4.1.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Abhishek Garg